openstack/governance
Code Issues Proposed changes

stackforge retirement: make workflow reqs+cla clearer

Browse Source 
There has been some concern voiced over the ambiguity of the language
used in this resolution. Concerns were brought up about whether new or
existing contributors will now need to sign a CLA or alter workflow. It
is my understanding that this is not the case.

To make this clear, I propose adding this unambiguous writing to the
resolution.

Change-Id: Iac0f87678479e694350cccfb9bb87ce3bb946ff6
This commit is contained in:
Ben Kero 2015-09-29 15:55:11 -07:00 committed by Flavio Percoco
parent 8e63b0f16e
commit c6e237eaf4
1 changed files with 5 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
resolutions/20150615-stackforge-retirement.rst
View File

@ -30,6 +30,8 @@ OpenStack project infrastructure will be permitted to use the
"openstack/" namespace. "openstack/" namespace.
The "openstack/" namespace is intended to convey that projects The "openstack/" namespace is intended to convey that projects
contained within it are developed by the OpenStack community at large. contained within it are hosted on OpenStack infrastructure. Only some
Only some of the projects within will be official OpenStack projects of the projects within will be official OpenStack projects
themselves. themselves. As such, there should not be any new requirements such as
CLA signing. This resolution should not alter the workflow of any of
the projects.