You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@incubator.apache.org by Jukka Zitting <ju...@zitting.name> on 2015/10/12 17:08:57 UTC

Incubation capacity

Hi,

It sounds like ruminations about the Incubator are on the increase again,
so I figured I'd wake up from my slumber and share an insight of mine.

I believe the way the Incubator is organized sets an upper bound on the
number of podlings it can effectively manage. Based on experience and
historical data (http://incubator.apache.org/history/ *) I believe this
limit is somewhere around 30 podlings.

Assuming my theory is correct, proposed changes to the Incubator structure
should be primarily evaluated on whether they increase bandwidth (number of
podlings we can manage), decrease latency (time to graduation or
termination) or tighten the entry criteria (implicit or explicit).

Proposals that tighten exit criteria or add extra constraints (voting,
reporting, etc.) during incubation may solve some immediate issues, but
will likely not help with the big picture unless they come with termination
clauses for podlings that fail to meet the constraints.

*) That graph was one of the key metrics I looked at during my time as the
Incubator VP.

BR,

Jukka Zitting

Re: Incubation capacity

Posted by "Mattmann, Chris A (3980)" <ch...@jpl.nasa.gov>.
Fantastic analysis Jukka.

Fan-freaking-tastic.

Cheers,
Chris

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Chief Architect
Instrument Software and Science Data Systems Section (398)
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 168-519, Mailstop: 168-527
Email: chris.a.mattmann@nasa.gov
WWW:  http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Associate Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++





-----Original Message-----
From: Jukka Zitting <ju...@gmail.com>
Reply-To: "general@incubator.apache.org" <ge...@incubator.apache.org>
Date: Monday, October 12, 2015 at 2:13 PM
To: general <ge...@incubator.apache.org>
Subject: Re: Incubation capacity

>Hi,
>
>On Mon, Oct 12, 2015 at 2:50 PM Marvin Humphrey <ma...@rectangular.com>
>wrote:
>> On Mon, Oct 12, 2015 at 8:08 AM, Jukka Zitting <ju...@zitting.name>
>>wrote:
>> > It sounds like ruminations about the Incubator are on the increase
>>again,
>>
>> I hope that we can make use of some of this bursting energy and channel
>>it
>> into incremental improvements.
>>
>> The Incubator is a stable platform, and it has been functioning well by
>> historical terms, and with blessedly low drama compared to a few years
>>ago.
>> My impression is that frustration with the institutional resistance of
>> Incubator to change is skewing impressions of how well it is doing its
>>job of
>> incubating podlings.
>
>Yes, we're far from the drama of 2011.
>
>> > I believe the way the Incubator is organized sets an upper bound on
>>the
>> > number of podlings it can effectively manage. Based on experience and
>> > historical data (http://incubator.apache.org/history/ *) I believe
>>this
>> > limit is somewhere around 30 podlings.
>>
>> I'm curious, Jukka.  Why 30?
>
>I don't have a firm theory on why this is happening, only some key
>observations:
>
>* The entry rate of new podlings has been amazingly constant
>throughout the existence of the Incubator even though the total number
>of open source projects has been growing exponentially for much of
>this time.
>
>* The "limit" was first reached in 2006 during which the board first
>pushed back on Incubator reports and the current monthly 1/3 reporting
>schedule was adopted and the process of retiring dormant podlings was
>adopted.
>
>* The Incubator stayed at or slightly above the 30 podlings limit
>until around mid-2010 after which many podlings started getting stuck,
>leading to the crisis of late 2011.
>
>* We solved that problem with a concentrated effort in 2012 that
>brought the Incubator back to around 30 active podlings, a level that
>stayed mostly stable for the next two years.
>
>* The number of current podlings is again growing, and some of the
>issues that have shown up recently remind me of the problems seen five
>years ago.
>
>It could be that I'm just selectively interpreting history to match my
>theory, but from a systems perspective it does look as if the
>Incubator indeed has a structural bandwidth cap that probably feeds
>into and limits the entry rate.
>
>>  What are the scarce resources?
>
>Some possible answers:
>
>* Mailing list. There is only so much general@ traffic that a single
>IPMC member can reasonably process without starting to skip
>significant parts.
>
>* Mentors. The growth rate of the IPMC is fairly constant and, with
>most members becoming inactive over time, I believe the number of
>active mentors has not grown too much over the years.
>
>* Chair/Report Manager. Someone still needs to pay attention to
>everything that's going around, which I believe you and all other
>recent chairs agree is a daunting task.
>
>One could run some numbers to better quantify the above possibilities.
>
>> And how is this supposed degradation manifesting?
>
>The noise got loud enough to wake me up. :-) I don't have hard
>numbers, but we do have a couple of recent failures and it sounds like
>some people are getting concerned, which does remind me of early 2011.
>Of course the one thing you can learn from history is that things are
>never quite the same.
>
>> Additionally, I'll note that while we're at 43 or so podlings right
>>now, we
>> have multiple podlings about to retire (Droids, Kalumet, likely
>>Corinthia) and
>> others about to graduate (Kylin, Groovy).
>
>Right, this might be just a fluke.
>
>BR,
>
>Jukka Zitting
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>For additional commands, e-mail: general-help@incubator.apache.org
>


Re: Incubation capacity

Posted by Bertrand Delacretaz <bd...@apache.org>.
On Tue, Oct 13, 2015 at 6:26 AM, Ted Dunning <te...@gmail.com> wrote:
> The (gut) feeling I have about scarce resources are:
> 1) me.  As Marvin noted, I am a failure mode as much as a contributor
> lately.  This is largely due to my crazy travel schedule combined with lots
> of short term deliverables....

This can hopefully be solved by delegating many of the IPMC chair's
tasks - as you say, thanks for Marvin and others for making this a
reality.

> ...2) mentors. As Jukka mentions, the number of mentors is roughly constant if
> you subtract away those who are MiA...

Using mentors availability (counting only actually active mentors) to
regulate the flow of podlings is the best way IMO.

-Bertrand

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: Incubation capacity

Posted by Ted Dunning <te...@gmail.com>.
Thanks Ross.

Good point.  And it has been long enough ago that people might be able to
look at it a bit more dispassionately.



On Mon, Oct 12, 2015 at 9:40 PM, Ross Gardler <Ro...@microsoft.com>
wrote:

> With respect to " I hope that we can manage that a bit by pushing to
> recognize common points of reference, move on to points difference and only
> then start discussing solutions." I remind everyone of a perfect starting
> point for this - perhaps we can focus on constructively updating
> http://wiki.apache.org/incubator/IncubatorIssues2013
>
> -----Original Message-----
> From: Ted Dunning [mailto:ted.dunning@gmail.com]
> Sent: Monday, October 12, 2015 9:26 PM
> To: general@incubator.apache.org
> Subject: Re: Incubation capacity
>
> I think that this is an excellent analysis.
>
> The (gut) feeling I have about scarce resources are:
>
> 1) me.  As Marvin noted, I am a failure mode as much as a contributor
> lately.  This is largely due to my crazy travel schedule combined with lots
> of short term deliverables. Marvin has lightened that load enormously with
> the report group and I see that as a good way forward
>
> 2) mentors. As Zukka mentions, the number of mentors is roughly constant
> if you subtract away those who are MiA
>
>
> I worry that the lull that others have noted in drama level may be
> increasing again. I hope that we can manage that a bit by pushing to
> recognize common points of reference, move on to points difference and only
> then start discussing solutions.
>
>
>
>
> On Mon, Oct 12, 2015 at 2:13 PM, Jukka Zitting <ju...@gmail.com>
> wrote:
>
> > Hi,
> >
> > On Mon, Oct 12, 2015 at 2:50 PM Marvin Humphrey
> > <ma...@rectangular.com>
> > wrote:
> > > On Mon, Oct 12, 2015 at 8:08 AM, Jukka Zitting <ju...@zitting.name>
> > wrote:
> > > > It sounds like ruminations about the Incubator are on the increase
> > again,
> > >
> > > I hope that we can make use of some of this bursting energy and
> > > channel
> > it
> > > into incremental improvements.
> > >
> > > The Incubator is a stable platform, and it has been functioning well
> > > by historical terms, and with blessedly low drama compared to a few
> > > years
> > ago.
> > > My impression is that frustration with the institutional resistance
> > > of Incubator to change is skewing impressions of how well it is
> > > doing its
> > job of
> > > incubating podlings.
> >
> > Yes, we're far from the drama of 2011.
> >
> > > > I believe the way the Incubator is organized sets an upper bound
> > > > on the number of podlings it can effectively manage. Based on
> > > > experience and historical data
> > > > (https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fi
> > > > ncubator.apache.org%2fhistory%2f&data=01%7c01%7cRoss.Gardler%40mic
> > > > rosoft.com%7c16c58f0566a547707af408d2d3868e32%7c72f988bf86f141af91
> > > > ab2d7cd011db47%7c1&sdata=6DkLFL2cvSI%2bi9cpO%2fbrzR6vmzQE4xKDInxbq
> > > > %2b270bE%3d *) I believe
> > this
> > > > limit is somewhere around 30 podlings.
> > >
> > > I'm curious, Jukka.  Why 30?
> >
> > I don't have a firm theory on why this is happening, only some key
> > observations:
> >
> > * The entry rate of new podlings has been amazingly constant
> > throughout the existence of the Incubator even though the total number
> > of open source projects has been growing exponentially for much of
> > this time.
> >
> > * The "limit" was first reached in 2006 during which the board first
> > pushed back on Incubator reports and the current monthly 1/3 reporting
> > schedule was adopted and the process of retiring dormant podlings was
> > adopted.
> >
> > * The Incubator stayed at or slightly above the 30 podlings limit
> > until around mid-2010 after which many podlings started getting stuck,
> > leading to the crisis of late 2011.
> >
> > * We solved that problem with a concentrated effort in 2012 that
> > brought the Incubator back to around 30 active podlings, a level that
> > stayed mostly stable for the next two years.
> >
> > * The number of current podlings is again growing, and some of the
> > issues that have shown up recently remind me of the problems seen five
> > years ago.
> >
> > It could be that I'm just selectively interpreting history to match my
> > theory, but from a systems perspective it does look as if the
> > Incubator indeed has a structural bandwidth cap that probably feeds
> > into and limits the entry rate.
> >
> > >  What are the scarce resources?
> >
> > Some possible answers:
> >
> > * Mailing list. There is only so much general@ traffic that a single
> > IPMC member can reasonably process without starting to skip
> > significant parts.
> >
> > * Mentors. The growth rate of the IPMC is fairly constant and, with
> > most members becoming inactive over time, I believe the number of
> > active mentors has not grown too much over the years.
> >
> > * Chair/Report Manager. Someone still needs to pay attention to
> > everything that's going around, which I believe you and all other
> > recent chairs agree is a daunting task.
> >
> > One could run some numbers to better quantify the above possibilities.
> >
> > > And how is this supposed degradation manifesting?
> >
> > The noise got loud enough to wake me up. :-) I don't have hard
> > numbers, but we do have a couple of recent failures and it sounds like
> > some people are getting concerned, which does remind me of early 2011.
> > Of course the one thing you can learn from history is that things are
> > never quite the same.
> >
> > > Additionally, I'll note that while we're at 43 or so podlings right
> > > now,
> > we
> > > have multiple podlings about to retire (Droids, Kalumet, likely
> > Corinthia) and
> > > others about to graduate (Kylin, Groovy).
> >
> > Right, this might be just a fluke.
> >
> > BR,
> >
> > Jukka Zitting
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: general-help@incubator.apache.org
> >
> >
>

RE: Incubation capacity

Posted by Ross Gardler <Ro...@microsoft.com>.
With respect to " I hope that we can manage that a bit by pushing to recognize common points of reference, move on to points difference and only then start discussing solutions." I remind everyone of a perfect starting point for this - perhaps we can focus on constructively updating http://wiki.apache.org/incubator/IncubatorIssues2013

-----Original Message-----
From: Ted Dunning [mailto:ted.dunning@gmail.com] 
Sent: Monday, October 12, 2015 9:26 PM
To: general@incubator.apache.org
Subject: Re: Incubation capacity

I think that this is an excellent analysis.

The (gut) feeling I have about scarce resources are:

1) me.  As Marvin noted, I am a failure mode as much as a contributor lately.  This is largely due to my crazy travel schedule combined with lots of short term deliverables. Marvin has lightened that load enormously with the report group and I see that as a good way forward

2) mentors. As Zukka mentions, the number of mentors is roughly constant if you subtract away those who are MiA


I worry that the lull that others have noted in drama level may be increasing again. I hope that we can manage that a bit by pushing to recognize common points of reference, move on to points difference and only then start discussing solutions.




On Mon, Oct 12, 2015 at 2:13 PM, Jukka Zitting <ju...@gmail.com>
wrote:

> Hi,
>
> On Mon, Oct 12, 2015 at 2:50 PM Marvin Humphrey 
> <ma...@rectangular.com>
> wrote:
> > On Mon, Oct 12, 2015 at 8:08 AM, Jukka Zitting <ju...@zitting.name>
> wrote:
> > > It sounds like ruminations about the Incubator are on the increase
> again,
> >
> > I hope that we can make use of some of this bursting energy and 
> > channel
> it
> > into incremental improvements.
> >
> > The Incubator is a stable platform, and it has been functioning well 
> > by historical terms, and with blessedly low drama compared to a few 
> > years
> ago.
> > My impression is that frustration with the institutional resistance 
> > of Incubator to change is skewing impressions of how well it is 
> > doing its
> job of
> > incubating podlings.
>
> Yes, we're far from the drama of 2011.
>
> > > I believe the way the Incubator is organized sets an upper bound 
> > > on the number of podlings it can effectively manage. Based on 
> > > experience and historical data 
> > > (https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fi
> > > ncubator.apache.org%2fhistory%2f&data=01%7c01%7cRoss.Gardler%40mic
> > > rosoft.com%7c16c58f0566a547707af408d2d3868e32%7c72f988bf86f141af91
> > > ab2d7cd011db47%7c1&sdata=6DkLFL2cvSI%2bi9cpO%2fbrzR6vmzQE4xKDInxbq
> > > %2b270bE%3d *) I believe
> this
> > > limit is somewhere around 30 podlings.
> >
> > I'm curious, Jukka.  Why 30?
>
> I don't have a firm theory on why this is happening, only some key
> observations:
>
> * The entry rate of new podlings has been amazingly constant 
> throughout the existence of the Incubator even though the total number 
> of open source projects has been growing exponentially for much of 
> this time.
>
> * The "limit" was first reached in 2006 during which the board first 
> pushed back on Incubator reports and the current monthly 1/3 reporting 
> schedule was adopted and the process of retiring dormant podlings was 
> adopted.
>
> * The Incubator stayed at or slightly above the 30 podlings limit 
> until around mid-2010 after which many podlings started getting stuck, 
> leading to the crisis of late 2011.
>
> * We solved that problem with a concentrated effort in 2012 that 
> brought the Incubator back to around 30 active podlings, a level that 
> stayed mostly stable for the next two years.
>
> * The number of current podlings is again growing, and some of the 
> issues that have shown up recently remind me of the problems seen five 
> years ago.
>
> It could be that I'm just selectively interpreting history to match my 
> theory, but from a systems perspective it does look as if the 
> Incubator indeed has a structural bandwidth cap that probably feeds 
> into and limits the entry rate.
>
> >  What are the scarce resources?
>
> Some possible answers:
>
> * Mailing list. There is only so much general@ traffic that a single 
> IPMC member can reasonably process without starting to skip 
> significant parts.
>
> * Mentors. The growth rate of the IPMC is fairly constant and, with 
> most members becoming inactive over time, I believe the number of 
> active mentors has not grown too much over the years.
>
> * Chair/Report Manager. Someone still needs to pay attention to 
> everything that's going around, which I believe you and all other 
> recent chairs agree is a daunting task.
>
> One could run some numbers to better quantify the above possibilities.
>
> > And how is this supposed degradation manifesting?
>
> The noise got loud enough to wake me up. :-) I don't have hard 
> numbers, but we do have a couple of recent failures and it sounds like 
> some people are getting concerned, which does remind me of early 2011.
> Of course the one thing you can learn from history is that things are 
> never quite the same.
>
> > Additionally, I'll note that while we're at 43 or so podlings right 
> > now,
> we
> > have multiple podlings about to retire (Droids, Kalumet, likely
> Corinthia) and
> > others about to graduate (Kylin, Groovy).
>
> Right, this might be just a fluke.
>
> BR,
>
> Jukka Zitting
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>

Re: Incubation capacity

Posted by Ted Dunning <te...@gmail.com>.
I think that this is an excellent analysis.

The (gut) feeling I have about scarce resources are:

1) me.  As Marvin noted, I am a failure mode as much as a contributor
lately.  This is largely due to my crazy travel schedule combined with lots
of short term deliverables. Marvin has lightened that load enormously with
the report group and I see that as a good way forward

2) mentors. As Zukka mentions, the number of mentors is roughly constant if
you subtract away those who are MiA


I worry that the lull that others have noted in drama level may be
increasing again. I hope that we can manage that a bit by pushing to
recognize common points of reference, move on to points difference and only
then start discussing solutions.




On Mon, Oct 12, 2015 at 2:13 PM, Jukka Zitting <ju...@gmail.com>
wrote:

> Hi,
>
> On Mon, Oct 12, 2015 at 2:50 PM Marvin Humphrey <ma...@rectangular.com>
> wrote:
> > On Mon, Oct 12, 2015 at 8:08 AM, Jukka Zitting <ju...@zitting.name>
> wrote:
> > > It sounds like ruminations about the Incubator are on the increase
> again,
> >
> > I hope that we can make use of some of this bursting energy and channel
> it
> > into incremental improvements.
> >
> > The Incubator is a stable platform, and it has been functioning well by
> > historical terms, and with blessedly low drama compared to a few years
> ago.
> > My impression is that frustration with the institutional resistance of
> > Incubator to change is skewing impressions of how well it is doing its
> job of
> > incubating podlings.
>
> Yes, we're far from the drama of 2011.
>
> > > I believe the way the Incubator is organized sets an upper bound on the
> > > number of podlings it can effectively manage. Based on experience and
> > > historical data (http://incubator.apache.org/history/ *) I believe
> this
> > > limit is somewhere around 30 podlings.
> >
> > I'm curious, Jukka.  Why 30?
>
> I don't have a firm theory on why this is happening, only some key
> observations:
>
> * The entry rate of new podlings has been amazingly constant
> throughout the existence of the Incubator even though the total number
> of open source projects has been growing exponentially for much of
> this time.
>
> * The "limit" was first reached in 2006 during which the board first
> pushed back on Incubator reports and the current monthly 1/3 reporting
> schedule was adopted and the process of retiring dormant podlings was
> adopted.
>
> * The Incubator stayed at or slightly above the 30 podlings limit
> until around mid-2010 after which many podlings started getting stuck,
> leading to the crisis of late 2011.
>
> * We solved that problem with a concentrated effort in 2012 that
> brought the Incubator back to around 30 active podlings, a level that
> stayed mostly stable for the next two years.
>
> * The number of current podlings is again growing, and some of the
> issues that have shown up recently remind me of the problems seen five
> years ago.
>
> It could be that I'm just selectively interpreting history to match my
> theory, but from a systems perspective it does look as if the
> Incubator indeed has a structural bandwidth cap that probably feeds
> into and limits the entry rate.
>
> >  What are the scarce resources?
>
> Some possible answers:
>
> * Mailing list. There is only so much general@ traffic that a single
> IPMC member can reasonably process without starting to skip
> significant parts.
>
> * Mentors. The growth rate of the IPMC is fairly constant and, with
> most members becoming inactive over time, I believe the number of
> active mentors has not grown too much over the years.
>
> * Chair/Report Manager. Someone still needs to pay attention to
> everything that's going around, which I believe you and all other
> recent chairs agree is a daunting task.
>
> One could run some numbers to better quantify the above possibilities.
>
> > And how is this supposed degradation manifesting?
>
> The noise got loud enough to wake me up. :-) I don't have hard
> numbers, but we do have a couple of recent failures and it sounds like
> some people are getting concerned, which does remind me of early 2011.
> Of course the one thing you can learn from history is that things are
> never quite the same.
>
> > Additionally, I'll note that while we're at 43 or so podlings right now,
> we
> > have multiple podlings about to retire (Droids, Kalumet, likely
> Corinthia) and
> > others about to graduate (Kylin, Groovy).
>
> Right, this might be just a fluke.
>
> BR,
>
> Jukka Zitting
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>

Re: Incubation capacity

Posted by Jukka Zitting <ju...@gmail.com>.
Hi,

On Mon, Oct 12, 2015 at 2:50 PM Marvin Humphrey <ma...@rectangular.com> wrote:
> On Mon, Oct 12, 2015 at 8:08 AM, Jukka Zitting <ju...@zitting.name> wrote:
> > It sounds like ruminations about the Incubator are on the increase again,
>
> I hope that we can make use of some of this bursting energy and channel it
> into incremental improvements.
>
> The Incubator is a stable platform, and it has been functioning well by
> historical terms, and with blessedly low drama compared to a few years ago.
> My impression is that frustration with the institutional resistance of
> Incubator to change is skewing impressions of how well it is doing its job of
> incubating podlings.

Yes, we're far from the drama of 2011.

> > I believe the way the Incubator is organized sets an upper bound on the
> > number of podlings it can effectively manage. Based on experience and
> > historical data (http://incubator.apache.org/history/ *) I believe this
> > limit is somewhere around 30 podlings.
>
> I'm curious, Jukka.  Why 30?

I don't have a firm theory on why this is happening, only some key observations:

* The entry rate of new podlings has been amazingly constant
throughout the existence of the Incubator even though the total number
of open source projects has been growing exponentially for much of
this time.

* The "limit" was first reached in 2006 during which the board first
pushed back on Incubator reports and the current monthly 1/3 reporting
schedule was adopted and the process of retiring dormant podlings was
adopted.

* The Incubator stayed at or slightly above the 30 podlings limit
until around mid-2010 after which many podlings started getting stuck,
leading to the crisis of late 2011.

* We solved that problem with a concentrated effort in 2012 that
brought the Incubator back to around 30 active podlings, a level that
stayed mostly stable for the next two years.

* The number of current podlings is again growing, and some of the
issues that have shown up recently remind me of the problems seen five
years ago.

It could be that I'm just selectively interpreting history to match my
theory, but from a systems perspective it does look as if the
Incubator indeed has a structural bandwidth cap that probably feeds
into and limits the entry rate.

>  What are the scarce resources?

Some possible answers:

* Mailing list. There is only so much general@ traffic that a single
IPMC member can reasonably process without starting to skip
significant parts.

* Mentors. The growth rate of the IPMC is fairly constant and, with
most members becoming inactive over time, I believe the number of
active mentors has not grown too much over the years.

* Chair/Report Manager. Someone still needs to pay attention to
everything that's going around, which I believe you and all other
recent chairs agree is a daunting task.

One could run some numbers to better quantify the above possibilities.

> And how is this supposed degradation manifesting?

The noise got loud enough to wake me up. :-) I don't have hard
numbers, but we do have a couple of recent failures and it sounds like
some people are getting concerned, which does remind me of early 2011.
Of course the one thing you can learn from history is that things are
never quite the same.

> Additionally, I'll note that while we're at 43 or so podlings right now, we
> have multiple podlings about to retire (Droids, Kalumet, likely Corinthia) and
> others about to graduate (Kylin, Groovy).

Right, this might be just a fluke.

BR,

Jukka Zitting

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: Incubation capacity

Posted by Marvin Humphrey <ma...@rectangular.com>.
On Mon, Oct 12, 2015 at 8:08 AM, Jukka Zitting <ju...@zitting.name> wrote:

> It sounds like ruminations about the Incubator are on the increase again,

I hope that we can make use of some of this bursting energy and channel it
into incremental improvements.

The Incubator is a stable platform, and it has been functioning well by
historical terms, and with blessedly low drama compared to a few years ago.
My impression is that frustration with the institutional resistance of
Incubator to change is skewing impressions of how well it is doing its job of
incubating podlings.

> I believe the way the Incubator is organized sets an upper bound on the
> number of podlings it can effectively manage. Based on experience and
> historical data (http://incubator.apache.org/history/ *) I believe this
> limit is somewhere around 30 podlings.

I'm curious, Jukka.  Why 30?  What are the scarce resources?  And how is this
supposed degradation manifesting?

*   One single point of failure has been the Chair, especially with regards to
    the report.  However, we have addressed that to some extent by having
    other people produce the report while leaving the Chair with editorial
    prerogative.
*   You could argue that we have a shortage of shepherds since participation
    has been flagging, but I don't see that as a bad thing.  The critical
    function of the shepherds -- keeping neglected podlings from falling
    through the cracks -- is now handled by the Report Manager.  And the
    expectation that it is the shepherd's role to provide review of podling
    reports is harmful in that it discourages Mentors from commenting.
*   It used to be the case that we were perpetually short on IPMC votes for
    releases, but since late 2013 we have been using that limited capacity
    much more effectively -- thanks to improved understanding of release
    policy and improved consensus about when leniency is appropriate, we now
    cycle through fewer release candidates.

Additionally, I'll note that while we're at 43 or so podlings right now, we
have multiple podlings about to retire (Droids, Kalumet, likely Corinthia) and
others about to graduate (Kylin, Groovy).

It would probably be healthy to nudge some podlings here and there towards
graduation or retirement, but we're doing that.  Podlings which don't report
get put into the "monthly" reporting category, as are podlings whose reports
are not signed-off by their Mentors -- and they are not removed until they
provide a proper signed-off report.  Recently this has triggered action on
Droids, Kalumet, and Wave.  Before that, NPanday and others.

So... I can see an argument that some individual Mentors might sometimes
stretch themselves too thin by taking on multiple projects, but I don't yet
grok how the Incubator's central institutions are having capacity problems.

Marvin Humphrey

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org