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

Attachment: pgpdDFeX8C356.pgp
Description: PGP signature

_______________________________________________
OpenStack-dev mailing list
[email protected]
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to