Rodent of Unusual Size wrote:
David Crossley wrote:
>We need an authoritative set of such stuff at the >top-level. Then each *project can consistently point >to "The ASF Guidelines" from their own doco. They then >provide the URL to each committer that is proposed. Easy. > >If the top-level documents also had named sections, then >each project could clearly refer to those when they need >to express some local clarification or extend the principle.
since the incubator project is supposed to 'train' new
committers and to-be committers, i think that it would
be a good project to take at least initial responsibility
for drafting these documents (and yes, it's an excellent
idea).
I disagree.
For sure the 'incubator' will be a great *user* of those documents, but the *development* of that documents should happen where the experts about ASF development communities are. Thus: here.
i'm going to be doing a bunch of writing and cross-referencing and putting the results there and asking for comment from the community; then pushing them up to the www.apache.org site once people are agreed that they contain the right message and information would seem a logical next step.
but this sounds like a good plan to me anyway.
Just wanted to point out that this mail list should be the one used to discuss the creation/wording/activity of those guidelines. I don't see any other mail list with fits better and will also serve as a great starting point to put differences on the table about how the ASF is supposed to do stuff (read, the infamous apache way)
-- Stefano Mazzocchi <[EMAIL PROTECTED]> --------------------------------------------------------------------
