On 10 Nov 2003, at 21:05, Geir Magnusson Jr. wrote:
<snip>
Now oversight is another issue entirely, but one that is fixable. If moving projects from j-c to a-c solves the oversight problem, then whatever magic happens when a j-c gets to a-c could easily be applied to jakarta's PMC, right?
i'm not sure that it can.
for a few months now, i've been subscribed to most of the jakarta sub-project mailing lists. it started out with the mirroring but i stayed as an experiment (partly as a result of the constant criticism that the jakarta-pmc receives). last week my email client died. i've spent all last week rebuilding a new IMAP server and transferring my (very precious) email onto it. i still think that it's possible to supervise something as big as jakarta - but only just. i don't spend very much time coding now :(
there are major issues about getting more folks on the jakarta pmc. at the moment, there are *major* procedure difficulties that are preventing our newly elected being officially recognized by the board as well as social ones. it is going to take time to reach our goal.
there are some very good folks in jakarta-oro, jakarta-regex and jakarta-commons who would (IMHO) find themselves pretty quickly elected to help supervise apache-commons if the product moved here. i think that the flatter structure will encourage this.
of course, some folks may see an ulterior motive. it will mean fewer product that i - and the rest of the jakarta pmc - are responsible for. (which may even free up some coding time :) but i really do think that there are products who need this move so that they can progress.
- robert
