Greetings all, It seems to me that this is similar to Apple's Finder creator type registry problem. What they've done is to allow developers to search an online database of creator types to determine whether their type is already in use, and then register that type with the database. The FSF could easily set up a similar database to manage the gnu.* namespace, reserving whichever packages are needed for current and future projects, allowing other developers to use the namespace with a great deal of freedom. This system isn't perfect. If the potential for abuse exists a human needs to be involved in the registration process. Also, it only serves as a mechanism for determining who has dibs on a particular package, it doesn't save you the trouble of enforcement. Just another $.02 for discussion. David Himelright
- Re: gnu.* namespace discussion Nic Ferrier
- Re: gnu.* namespace discussion Aaron M. Renn
- Re: gnu.* namespace discussion Brian Jones
- Re: gnu.* namespace discussion Emil Eifrem
- Re: gnu.* namespace discussion Nic Ferrier
- Re: gnu.* namespace discussion Emil Eifrem
- Re: gnu.* namespace discussion Tom Tromey
- Re: gnu.* namespace discussion Bryce McKinlay
- Re: gnu.* namespace discussion Nic Ferrier
- Re: gnu.* namespace discussion Nic Ferrier
- Re: gnu.* namespace discussion David Himelright
- Re: gnu.* namespace discussion Nic Ferrier
- Re: gnu.* namespace discussion Tom Tromey
- Re: gnu.* namespace discussion Aaron M. Renn
- Re: gnu.* namespace discussion Mark Wielaard
- Re: gnu.* namespace discussion Nic Ferrier
- Re: gnu.* namespace discussion Tom Tromey
- Re: gnu.* namespace discussion Paul Fisher
- javax.sound (Was: gnu.* namespace discussion) Mark Wielaard

