[openstack-dev] [governance] Becoming a Program, before applying for incubation

Dina Belova dbelova at mirantis.com
Wed Dec 18 05:07:28 UTC 2013


Mark, I love that idea.

It seems to me nice to have 'projects kindergarten' were every one is
blessed because of youth and perspective from the point of OpenStack
future, but at the same time it will be some scale of being talented and
experienced for these 'children'.

It might solve problem of better visibility for new (really good
ones!) initiatives, but will make even more huge headache for TC, I
suppose... This solution requires permanent observation and going deeper in
tones of new ideas...

Thanks,
Dina

On Tuesday, December 17, 2013, 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)  ?
>
> Mark.
>
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org <javascript:;>
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>


-- 

Best regards,

Dina Belova

Software Engineer

Mirantis Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20131218/8aef104c/attachment.html>


More information about the OpenStack-dev mailing list