incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eelco Hillenius" <>
Subject Re: incubation process for open development open source projects [WAS Re: Glasgow - community? specs? other issues?]
Date Sun, 06 Aug 2006 21:19:34 GMT
> IMHO the incubator should not impose timescales or a schedule on a
> project but a project may decide to impose a timescale on itself.

My thought is that a time scale would be part of the proposal. If that
proposal is voted in, it would also mean the time scale is excepted
and thus - unless urgent reasons exist not to - should be adhered to
by all parties involved.

> the project is (of course) equally free to ignore or interpret this
> schedule as it pleases since it is not binding on apache.

Time scales without such binding would not be very useful. Democracy
and timelines do not conflict. There are many instances where
timelines in open development are agreed upon, such as waiting periods
and vote windows. I don't see why that can't be applied to the
incubation process, other than that it is less convenient for ASF
(though I believe it would bring convenience of clarity and a
stream-lined process in the long run).

Adopting time lines could be a step towards making the incubation
process less soft and single-sided. The current process is convenient
for everyone but the members of the project to incubate - whether that
is because of things like the 'prior proof' issue I talked about
earlier or things like the lack of timelines. Improving such things
would make the process more straightforward to execute and less
vulnerable for subjectivity, and regarding the incubating party as
more of an equal would imvho be very much 'the open development way'.


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message