Open Stack

> On Nov 30, 2015, at 8:17 AM, Thierry Carrez <thierry at openstack.org> wrote:
> 
> AFEK, Ifat (Ifat) wrote:
>> My name is Ifat, and I am the PTL of a new project named Vitrage[1][2]. We would like Vitrage to be the Openstack RCA (Root Cause Analysis) Engine for analyzing and expanding OpenStack alarms & events, yielding insights regarding the root cause of problems and deducing the existence of problems before they are directly detected.
>> 
>> We already have this functionality working in production in Alcatel-Lucent CloudBand solution (as proprietary java code), and we started a process of porting it to python.
>> 
>> In a few months from now, once we have something ready, we will ask to become an OpenStack project under the Big Tent. Are there any specific guidelines, processes to follow, things we should consider in advance, etc.? we are trying to do everything "right" from the beginning, to make the process easier later on.
>> 
>> [1] https://wiki.openstack.org/wiki/Vitrage
>> [2] https://launchpad.net/vitrage
> 
> Hi Ifat,
> 
> You should look into the requirements for the new project teams:
> http://governance.openstack.org/reference/new-projects-requirements.html
> 
> You'll find that those are mostly community requirements. The big tent
> approach to OpenStack inclusion is that if you help achieving the
> OpenStack mission and are part of the OpenStack community (and develop
> in the OpenStack way), then you are an OpenStack project.
> 
> We further documented the OpenStack culture in the project team guide
> (still under development):
> http://docs.openstack.org/project-team-guide/
> 
> Those two reference documents should go a long way to explain what we
> expect from OpenStack project teams.

I also encourage you to not wait to start applying those principles until “a few months from now” once you "have something ready”. By far the biggest issue with new project applications has been the teams working in ways that do not meet the openness requirements, such as behind corporate firewalls or using exclusionary communication channels. Following that pattern will only delay the acceptance of Vitrage as an official project.

Set up your repository on git.openstack.org now and use it for the port. Use the openstack-dev mailing list and our IRC meeting rooms to organize that work. Demonstrate that you want to be part of the community, not just part of the brand, so that when the time comes your application will be easy to approve.

Doug