I disagree .. and we've had this conversation here before; with ActiveMQ
IIRC. Org.apache.* is a way to let the programmer know that they're using
an Apache product and IMO its important to make that transition as part of
incubation.
I'm +1 to the staged model Niclas proposed.
Sanjiva.
William A. Rowe, Jr. wrote:
Ted Husted wrote:
IMHO, unless there are trademark or licensing issues involved, there
should be no "Apache rules" about Java package naming schemes. Package
names are an arbitrary implementation detail, and the one and only
concern should be what makes the most sense to the individual
community. When it comes to implementation details, the controlling
"Apache rule" should be that "The PMC as a whole is the entity that
controls the project, nobody else."
There are rules, and then again there are guidelines. I don't think that
a generic statement about packaging conventions is a bad thing to help
projects new to the incubator.
Adding a statement something along the lines of what you wrote above would
be a good thing, so that PMC's know they have flexibility beyond the guidelines.
Bill
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Sanjiva Weerawarana, Ph.D.
Founder & Director; Lanka Software Foundation; http://www.opensource.lk/
Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
Director; Open Source Initiative; http://www.opensource.org/
Member; Apache Software Foundation; http://www.apache.org/
Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
