incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ross Gardler <>
Subject Re: Small but otherwise happy podlings
Date Mon, 09 Jan 2012 13:04:52 GMT
On 9 January 2012 12:46, Benson Margulies <> wrote:
> On Mon, Jan 9, 2012 at 5:28 AM, ant elder <> wrote:


>> I don't know about the more autonomy proposal but I had a quick look
>> at Isis. If they've never added any new committers thats a worry but
>> other than that they seem to meet all the other graduation
>> requirements. Do you or the other mentors have any feel for why
>> they've not added any new committers - are they over protective of
>> their code or have they really just had no one ever come along
>> offering patches or anything?
> As far as I've been able to determine, no one has come along.

OK, this is the same problem I have in one of my podlings (Wookie).
The issue is how do we get them to "come along". If potential
contributors just do not exist then then sufficient diversity is not
possible and being in the Incubator will therefore be indefinite. On
the other hand if they are not coming for some other reason is being
in the incubator a contributing factor?

Do we want to allow projects that have little chance of reaching the
diversity requirements?

Do we want to help projects that find the incubator limits their
ability to build diversity?

For example, in the case of Wookie the code is serviceable. We are
aware of a number of people who are using Wookie, but they are all in
the R&D rather than product spaces. Some of them have local forks with
features we want from them. In most cases they are for some, often
unknown, reason reticent to contribute. In one case we had a
contribution but once that particular feature is included they are
happy and engage no more. Of course, this is all perfectly normal for
an open source project. In TLPs appropriate drive by contributions are
not a problem as there is a community to maintain them.

I don't know about Isis but the issue for Wookie, I think, is that it
is building on a W3C standard that has yet to prove itself. Wookie is
one of only a small number of fully compliant implementations of the
standard. Its an interesting project from an R&D perspective, but not
one that people are likely to bet their future on (yet?). As an
incubating project implementing a yet to be proved standard the risks
are just too high.

I don't think Wookie should graduate, but it certainly shouldn't be
kicked out (and I don't think it will be). However, as I not above
incubation may be holding it back. The question for me is, can we do
more for projects that are in this position?

I'm thinking about this from a Wookie perspective and will (I hope)
have something concrete to suggest soon(ish), in the meantime does
anyone have any ideas of how we can help projects like Isis and


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

View raw message