On Sat, 2007-07-28 at 22:57 +0100, Stephen Colebourne wrote: > > More than this is the question of oversight. Personally, I would not > feel comfortable sitting on a PMC with APR or C++ libraries being > released. I would have no measure by which to judge their release > worthiness, or to handle issues from them.
Nobody is suggesting this. Our PMC is for java-based commons components only. The question is whether we want to allow multiple different PMCs to share the same "http://commons.apache.org"; dns entry, ie whether our stuff should appear at commons.apache.org/SOMETHING. The options are: (a) we use commons.apache.org directly, and worry about it if some other commons community ever exists (b) we take over commons.apache.org permanently, and other communities can use commons-python.apache.org etc. (c) we use a subdir as described above. (a) could be a nuisance for us; moving breaks links. With our current move we can transparently redirect jakarta.apache.org/commons to our new home but it won't be possible to transparently redirect commons.apache.org to commons.apache.org/SOMETHING. (c) looks pretty silly if no other commons community exists. My preference would have been to use commons-jakarta.apache.org (or commons-java.apache.org if legal) from the start but that wasn't the consensus. Regards, Simon --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
