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."
-Ted. On 7/22/07, Niclas Hedhman <[EMAIL PROTECTED]> wrote:
On Sunday 22 July 2007 17:52, Dan Creswell wrote: > We would appreciate some clarification in respect of the above and some > guidance on what the minimum requirements might be. For example would > it be acceptable to create a compatibility layer and thus, for at least > this first release, have both com.sun and org.apache namespaces present > in our codebase and release? This would allow our users some time to > transition smoothly to the new package namespace.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
