From c6e237eaf44aa3f9b092fa111991f254b3274615 Mon Sep 17 00:00:00 2001 From: Ben Kero Date: Tue, 29 Sep 2015 15:55:11 -0700 Subject: [PATCH] stackforge retirement: make workflow reqs+cla clearer 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 --- resolutions/20150615-stackforge-retirement.rst | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/resolutions/20150615-stackforge-retirement.rst b/resolutions/20150615-stackforge-retirement.rst index 483b3adce..338bf5a3e 100644 --- a/resolutions/20150615-stackforge-retirement.rst +++ b/resolutions/20150615-stackforge-retirement.rst @@ -30,6 +30,8 @@ OpenStack project infrastructure will be permitted to use the "openstack/" namespace. The "openstack/" namespace is intended to convey that projects -contained within it are developed by the OpenStack community at large. -Only some of the projects within will be official OpenStack projects -themselves. +contained within it are hosted on OpenStack infrastructure. Only some +of the projects within will be official OpenStack projects +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.