Ken, > i see the incubator as having two roles. one is the > entry path for new packages and their communities
I think that everyone agrees on this, although not everyone may understand all of the nuances. For example, I wasn't clear on why a project should go through Incubator if there is an existing TLP into which it will go until recently. And I think that the destination TLP needs to be made aware that they have to be intimiately involved with the podling. They need to steward it, not leave it like a boy in a bubble to be cared for by the nursing staff until its immune system develops. > the other role is basically as a documentation repository for all of the > aspects of that last bit -- how the asf works, what the different parts > are, how they interact, what/how/why is a pmc/project/subproject/committer/ > member/... and so on. I don't know if everyone agrees, but I do favor a single point of reference for those documents. I find it frustrating to require people to engage in a scavenger hunt that often leads to redundant and occassionally conflicting documents that have played whispering down the lane. But there are others who see such documents as turf to be protected. As for time, didn't you recently resign as Commons Chair because you didn't have time? Are you sure that you have the time to devote to Incubator, which I see as being far more important and active at this point in time? --- Noel --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]