On Dec 18, 2013, at 4:40 AM, Thierry Carrez wrote:
> I guess there are 3 options:
>
> 1. Require diversity for incubation, but find ways to bless or recommend
> projects pre-incubation so that this diversity can actually be achieved
>
> 2. Do not require diversity for incubation, but require it
+1
-bryan
On Wed, Dec 18, 2013 at 10:22 PM, Jay Pipes wrote:
> On 12/18/2013 12:34 PM, Doug Hellmann wrote:
>
>> I have more of an issue with a project failing *after* becoming
>> integrated than during incubation. That's why we have the incubation
>> period to begin with. For the same reason,
Le 18/12/2013 16:37, Steven Dake a écrit :
In the early days of incubation requests, I got the distinct
impression managers at companies believed that actually getting a
project incubated in OpenStack was not possible, even though it was
sparsely documented as an option. Maybe things are dif
On 12/18/2013 12:34 PM, Doug Hellmann wrote:
I have more of an issue with a project failing *after* becoming
integrated than during incubation. That's why we have the incubation
period to begin with. For the same reason, I'm leaning towards allowing
projects into incubation without a very diverse
On Wed, Dec 18, 2013 at 2:40 AM, Thierry Carrez wrote:
> I guess there are 3 options:
>
> 1. Require diversity for incubation, but find ways to bless or recommend
> projects pre-incubation so that this diversity can actually be achieved
>
> 2. Do not require diversity for incubation, but require i
On 12/18/2013 07:01 AM, Dolph Mathews wrote:
> Options 2 and 3 sound identical to me, when realistically applied.
> Option 3 just makes the common sense aspect mandatory.
Indeed, Option 3 gets my vote. One aspect I'd like to mention regarding
diversity of contributors in any open source project is
On 18/12/13 12:35 -0500, Doug Hellmann wrote:
On Wed, Dec 18, 2013 at 10:58 AM, Sean Dague wrote:
On 12/18/2013 10:37 AM, Steven Dake wrote:
> But I can tell you one thing for certain, an actual incubation
> commitment from the OpenStack Technical Committee has a huge impact - it
>
On Wed, Dec 18, 2013 at 10:20 AM, Jarret Raim wrote:
> > It is a difficult thing to measure, and I don't think the intent is to
> set
> a hard %
> > for contributions. I think the numbers for Barbican were just
> illustrating
> the
> > fact that the concrete contributions are very coming very heav
On Wed, Dec 18, 2013 at 10:58 AM, Sean Dague wrote:
> On 12/18/2013 10:37 AM, Steven Dake wrote:
> > On 12/18/2013 03:40 AM, Thierry Carrez wrote:
> >> Hi everyone,
> >>
> >> The TC meeting yesterday uncovered an interesting question which, so
> >> far, divided TC members.
> >>
> >> We require th
On 18/12/13 11:40 +0100, Thierry Carrez wrote:
Hi everyone,
The TC meeting yesterday uncovered an interesting question which, so
far, divided TC members.
We require that projects have a number of different developers involved
before they apply for incubation, mostly to raise the bus factor. But
On Wed, Dec 18 2013, Thierry Carrez wrote:
> 1. Require diversity for incubation, but find ways to bless or recommend
> projects pre-incubation so that this diversity can actually be achieved
>
> 2. Do not require diversity for incubation, but require it for
> graduation, and remove projects from
On 12/18/2013 10:37 AM, Steven Dake wrote:
> On 12/18/2013 03:40 AM, Thierry Carrez wrote:
>> Hi everyone,
>>
>> The TC meeting yesterday uncovered an interesting question which, so
>> far, divided TC members.
>>
>> We require that projects have a number of different developers involved
>> before t
On 12/18/2013 03:40 AM, Thierry Carrez wrote:
Hi everyone,
The TC meeting yesterday uncovered an interesting question which, so
far, divided TC members.
We require that projects have a number of different developers involved
before they apply for incubation, mostly to raise the bus factor. But
> It is a difficult thing to measure, and I don't think the intent is to set
a hard %
> for contributions. I think the numbers for Barbican were just illustrating
the
> fact that the concrete contributions are very coming very heavily from one
> source. That's only one data point, though, and as
On Wed, Dec 18, 2013 at 5:18 AM, Daniel P. Berrange wrote:
> On Wed, Dec 18, 2013 at 11:40:21AM +0100, Thierry Carrez wrote:
>
> > 2. Do not require diversity for incubation, but require it for
> > graduation, and remove projects from incubation if they fail to attract
> > a diverse community
> >
gt; > Subject: Re: [openstack-dev] Diversity as a requirement for incubation
> >
> > Le 18/12/2013 11:40, Thierry Carrez a écrit :
> > > I guess there are 3 options:
> > >
> > > 1. Require diversity for incubation, but find ways to bless or
> > > rec
On Wed, Dec 18, 2013 at 6:18 AM, Daniel P. Berrange wrote:
> On Wed, Dec 18, 2013 at 11:40:21AM +0100, Thierry Carrez wrote:
> > Hi everyone,
> >
> > The TC meeting yesterday uncovered an interesting question which, so
> > far, divided TC members.
> >
> > We require that projects have a number of
On Wed, Dec 18, 2013 at 6:04 AM, Sylvain Bauza wrote:
> Le 18/12/2013 11:40, Thierry Carrez a écrit :
>
> I guess there are 3 options:
>>
>> 1. Require diversity for incubation, but find ways to bless or recommend
>> projects pre-incubation so that this diversity can actually be achieved
>>
>> 2.
On Wed, Dec 18, 2013 at 02:57:27PM +0100, Thierry Carrez wrote:
> Daniel P. Berrange wrote:
> > On Wed, Dec 18, 2013 at 11:40:21AM +0100, Thierry Carrez wrote:
> >> I guess there are 3 options:
> >>
> >> 1. Require diversity for incubation, but find ways to bless or recommend
> >> projects pre-incu
Daniel P. Berrange wrote:
> On Wed, Dec 18, 2013 at 11:40:21AM +0100, Thierry Carrez wrote:
>> I guess there are 3 options:
>>
>> 1. Require diversity for incubation, but find ways to bless or recommend
>> projects pre-incubation so that this diversity can actually be achieved
>>
>> 2. Do not requi
I would vote for the approach number 2. I think there are some distinct
advantages for one company driving the development of a certain feature
sets early in the life of the project, typically, the speed of development
is faster, and it is easier to achieve focus early on.
Allowing important initi
> -Original Message-
> From: Sylvain Bauza [mailto:sylvain.ba...@bull.net]
> Sent: Wednesday, December 18, 2013 5:04 AM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] Diversity as a requirement for incubation
>
>
I think we're all happy that if a project *does* have a broad support base
we're good; this is only the case for projects in one of two situations:
- support is spread so thinly that each company involved in the area has
elected to support a different solution
- the project is just not that interes
On Wed, Dec 18, 2013 at 11:40:21AM +0100, Thierry Carrez wrote:
> Hi everyone,
>
> The TC meeting yesterday uncovered an interesting question which, so
> far, divided TC members.
>
> We require that projects have a number of different developers involved
> before they apply for incubation, mostly
Le 18/12/2013 11:40, Thierry Carrez a écrit :
I guess there are 3 options:
1. Require diversity for incubation, but find ways to bless or recommend
projects pre-incubation so that this diversity can actually be achieved
2. Do not require diversity for incubation, but require it for
graduation,
25 matches
Mail list logo