Open Stack

Thanks for the clarifications, Thierry!  Not being totally involved and following only parts leads to my getting some foggy results, especially trying to find wikis and other related docs through not great search tools.  Hopes this makes things clearer for the DefCore team.  It might also lead to another blog post and/or more words tiring these altogether on a wiki or doc for the various communities.  I try to keep up, but those at the center seldom realize how much context needs to be added for those only seeing the final decisions.

Again,thanks for the clarifications and corrections and hope this helps those reading Defcore ML

--Rocky

Sent from my iPad

> On Feb 12, 2015, at 01:06, Thierry Carrez <thierry at openstack.org> wrote:
> 
> See comments & corrections below.
> 
> FWIW I'm preparing a openstack.org blog post to publicize the recent
> changes.
> 
> Rochelle Grober wrote:
>> [...]
>> New project tag “Integrated-Release”:
>> 
>> http://governance.openstack.org/reference/tags/integrated-release.html
>> 
>> Note on the above, the last section lists the “integrated” projects for
>> Kilo.
> 
> This tag is more a way to seamlessly transition the previous
> categorization (being part of the integrated release or not) into the
> new world order. Kilo will still do an integrated release, so we use the
> tag to describe it.
> 
>> [...]
>> These specify the new process for a project to “join” OpenStack.  They
>> no longer will be moved to the OpenStack repositories, but can remain in
>> stackforge.
> 
> I don't know where you got that information. Obviously projects
> recognized as "produced by the OpenStack community" will live under the
> openstack/ git organization name. Stackforge is explicitly *not* OpenStack.
> 
> The spec you linked to states:
> 
> "The second part of the change is recognizing that there is more to
> “OpenStack” than a finite set of projects blessed by the Technical
> Committee. We already have plenty of projects that are developed on
> OpenStack infrastructure, follow the OpenStack way of doing things, have
> development discussions on the openstack-dev mailing-list and use
> #openstack-meeting channels for their team meetings. Those are part of
> the OpenStack community as well, and we propose that those should
> considered “OpenStack projects” (and be hosted under openstack git
> namespaces), as long as they meet an objective criteria for inclusion
> (to be developed as one of the work items below)."
> 
>> [...]
>> Along with the new project process, there is also a new testing
>> guidelines document that will be applied to all projects wanting to
>> become part of OpenStack:
>> 
>> http://governance.openstack.org/reference/project-testing-interface.html
> 
> This document is actually not new. It describes how we operated in the
> past years.
> 
> Cheers,
> 
> -- 
> Thierry Carrez (ttx)
> 
> _______________________________________________
> Defcore-committee mailing list
> Defcore-committee at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee