Le 18/12/2013 11:25, Thierry Carrez a écrit :
Sylvain Bauza wrote:
Well, correct me if I'm wrong, but Stackforge is already the place for
promising projects ? If so, why creating a wikipage for listing them ?
Not really. Any project can be in stackforge. It doesn't have to be
promising or to wa
Sylvain Bauza wrote:
> Well, correct me if I'm wrong, but Stackforge is already the place for
> promising projects ? If so, why creating a wikipage for listing them ?
Not really. Any project can be in stackforge. It doesn't have to be
promising or to want to ever be part of the integrated openstac
Le 17/12/2013 14:59, Thierry Carrez a écrit :
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 feedbac
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 b
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 q
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 feedba
On 17/12/13 11:54 +0100, Jaromir Coufal wrote:
On 2013/16/12 15:19, Flavio Percoco wrote:
1. Programs that are not part of OpenStack's release cycle shouldn't
be considered official nor they should have the rights that integrated
projects have.
I don't agree on this point. There might be support
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
>
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
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 deci
On Tue, 2013-12-17 at 11:25 +0100, Thierry Carrez wrote:
> Mark McLoughlin wrote:
> > I'm not totally convinced we need such formality around the TC
> > expressing its support for an early-stage program/project/effort/team.
>
> This is a difficult balance.
>
> You want to help a number of project
On 2013/16/12 15:19, Flavio Percoco wrote:
1. Programs that are not part of OpenStack's release cycle shouldn't
be considered official nor they should have the rights that integrated
projects have.
I don't agree on this point. There might be supportive teams, which are
helping OpenStack in gener
Mark McLoughlin wrote:
> I'm not totally convinced we need such formality around the TC
> expressing its support for an early-stage program/project/effort/team.
This is a difficult balance.
You want to help a number of projects attract more contributors and
reach critical mass. For that, they wan
On 16/12/13 23:49 +, Mark McLoughlin wrote:
Hi Thierry,
On Fri, 2013-12-13 at 15:53 +0100, Thierry Carrez wrote:
Hi everyone,
TL;DR:
Incubation is getting harder, why not ask efforts to apply for a new
program first to get the visibility they need to grow.
Long version:
Last cycle we int
Hi Thierry,
On Fri, 2013-12-13 at 15:53 +0100, Thierry Carrez wrote:
> Hi everyone,
>
> TL;DR:
> Incubation is getting harder, why not ask efforts to apply for a new
> program first to get the visibility they need to grow.
>
> Long version:
>
> Last cycle we introduced the concept of "Programs"
On Mon, Dec 16, 2013 at 9:49 AM, Thierry Carrez wrote:
> Flavio Percoco wrote:
> > What I'm arguing here is:
> >
> > 1. Programs that are not part of OpenStack's release cycle shouldn't
> > be considered official nor they should have the rights that integrated
> > projects have.
> >
> > 2. I think
Flavio Percoco wrote:
> What I'm arguing here is:
>
> 1. Programs that are not part of OpenStack's release cycle shouldn't
> be considered official nor they should have the rights that integrated
> projects have.
>
> 2. I think requesting Programs to exist at the early stages of the
> project is
On 13/12/13 16:37 +0100, Flavio Percoco wrote:
On 13/12/13 15:53 +0100, Thierry Carrez wrote:
Hi everyone,
TL;DR:
Incubation is getting harder, why not ask efforts to apply for a new
program first to get the visibility they need to grow.
Long version:
Last cycle we introduced the concept of "
Apologies for the miss, I just double-checked and Nova does have its own
mission statement :
http://git.openstack.org/cgit/openstack/governance/tree/reference/programs.yaml
Thanks,
-Sylvain
2013/12/13 Sylvain Bauza
> Thanks Thierry.
>
> AFAIK, Compute ("Nova") is not having yet its own mission
Thanks Thierry.
AFAIK, Compute ("Nova") is not having yet its own mission statement, so I
guess any project with different people than regular Nova ATCs should
consider an request for new Program if they feel there is difference in
terms of feature delivery ?
-Sylvain
2013/12/13 Thierry Carrez
On 13/12/13 10:44 -0500, Russell Bryant wrote:
On 12/13/2013 10:37 AM, Flavio Percoco wrote:
On 13/12/13 15:53 +0100, Thierry Carrez wrote:
Hi everyone,
TL;DR: Incubation is getting harder, why not ask efforts to apply
for a new program first to get the visibility they need to grow.
Long vers
Sylvain Bauza wrote:
> While I agree with most of what Thierry said, I need clarifications
> though, on what a Program is,
A "team" is a group of people working on a given mission. They can be
freely created. They apply to become an "OpenStack Program" if they feel
their (well-established) mission
While I agree with most of what Thierry said, I need clarifications though,
on what a Program is, and what is the key point where an idea should get
its own Program instead of being headed by an already existing Program.
For example, take Barbican which is providing extra features to Keystone,
or
On 12/13/2013 10:37 AM, Flavio Percoco wrote:
> On 13/12/13 15:53 +0100, Thierry Carrez wrote:
>> Hi everyone,
>>
>> TL;DR: Incubation is getting harder, why not ask efforts to apply
>> for a new program first to get the visibility they need to grow.
>>
>> Long version:
>>
>> Last cycle we intro
On 13/12/13 15:53 +0100, Thierry Carrez wrote:
Hi everyone,
TL;DR:
Incubation is getting harder, why not ask efforts to apply for a new
program first to get the visibility they need to grow.
Long version:
Last cycle we introduced the concept of "Programs" to replace the
concept of "Official pr
On 12/13/2013 09:53 AM, Thierry Carrez wrote:
> Hi everyone,
>
> TL;DR:
> Incubation is getting harder, why not ask efforts to apply for a new
> program first to get the visibility they need to grow.
>
> Long version:
>
> Last cycle we introduced the concept of "Programs" to replace the
> concep
26 matches
Mail list logo