Open Stack

Hi,

Murano project volunteers to be a first project applying to "Emerging
projects" program. Murano was here quite long time and it was developed
taking into account all OpenStack development processes.

I think Murano is a good candidate to be a first project in this new
program as it should be quite painless to try different OpenStack
requirements on Murano in order to specify "Emerging projects" requirements
in the future.

What kind of process should it be for "Emerging projects" program
application?

Thanks
Georgy



On Tue, Dec 17, 2013 at 6:27 AM, Flavio Percoco <flavio at redhat.com> wrote:

> On 17/12/13 14:59 +0100, Thierry Carrez wrote:
>
>> Mark McLoughlin wrote:
>>
>>> On Tue, 2013-12-17 at 13:44 +0100, Thierry Carrez wrote:
>>>
>>>> Mark McLoughlin wrote:
>>>>
>>>>> How about if we had an "emerging projects" page where the TC feedback
>>>>> on
>>>>> each project would be listed?
>>>>>
>>>>> That would give visibility to our feedback, without making it a yes/no
>>>>> blessing. Ok, whether to list any feedback about the project on the
>>>>> page
>>>>> is a yes/no decision, but at least it allows us to fully express why we
>>>>> find the project promising, what people need to help with in order for
>>>>> it to be incubated, etc.
>>>>>
>>>>> With a formal yes/no status, I think we'd struggle with projects which
>>>>> we're not quite ready to even bless with an "emerging" status but we
>>>>> still want to encourage them - this allows us to bless a project as
>>>>> "emerging" but be explicit about our level of support for it.
>>>>>
>>>>
>>>> I agree that being able to express our opinion on a project in shades of
>>>> grey is valuable... The main drawback of using a non-boolean status for
>>>> that is that you can't grant any benefit to it. So we'd not be able to
>>>> say "emerging projects get design summit space".
>>>>
>>>> They can still collaborate in unconference space or around empty tables,
>>>> but then we are back to the problem we are trying to solve: increase
>>>> visibility of promising projects pre-incubation.
>>>>
>>>
>>> Have an emerging projects track and leave it up to the track coordinator
>>> to decide prioritize the most interesting sessions and the most advanced
>>> projects (according to the TC's feedback)  ?
>>>
>>
>> I guess that /could/ work. I don't expect we'll have space for more than
>> one session per project, but that may be enough for self-organization if
>> we nail the "collaboration spaces" correctly.
>>
>> I'm fine with giving that page a try (we can always revisit if it's not
>> working any better...).
>>
>
>
> I'm not sure about the page as a medium for this but I like the idea.
> This is pretty much a way to incubate programs, which is basically
> what I proposed in my previous emails. Lets not consider Programs
> official right away, lets give them a place where they can grow a bit
> with the projects the have under their umbrella. Lets also - as Mark
> suggested - use that place to add comments and help them grow.
>
> And I'm also in favor of having a emerging projects track. +1
>
>
> Cheers,
> FF
>
>
> --
> @flaper87
> Flavio Percoco
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
Georgy Okrokvertskhov
Technical Program Manager,
Cloud and Infrastructure Services,
Mirantis
http://www.mirantis.com
Tel. +1 650 963 9828
Mob. +1 650 996 3284
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20131217/d409f7c4/attachment.html>