On 5/21/07, Rony G. Flatscher <[EMAIL PROTECTED]> wrote:
There may be many reasons why a project turned "dormant": no interest
(dead technology), committers having gone astray, etc.
One reason that may be special is a project which got developed, is
used, but there is no reason to develop it further. If classifying a
project as "matured" it still may need fixing of problems and/or
enhancements over time, making it necessary to create a new distribution.
The idea of putting a "matured" project into the "incubator" realm does
not sound "right" to me.
That's is *not* what is being said.
What is being said is that if a codebase loses all of its committers,
and there is no one to nominate new committers, and one or more new
volunteers come along that want to work on the codebase, then those
individuals could become committers by applying to the Incubator.
Anyone who is the position where they have become the last one or two
committers to a codebase should put out a bulletin, first asking for
other ASF Committers to step up, and if no one replies, then
nominating likely candidates from the user list.
Unless there are already rules that mandate that projects that got
developed to a point after which they go into "maintenance" mode need to
go into the "incubator", I would suggest to create a new classification
for such projects.
Again, no one is suggesting that any codebase be unilaterally moved anywhere.
If we are short of committers for a codebase, then what committers
remain should recruit new committers.
If we lose all the committers, and new volunteers come along, then the
Incubator becomes the way that we bootstrap the new set of committers.
When we realize that have no committers, for whatever reason, then
someone should patch the website so that everyone knows where we
stand.
-Ted.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
