Re: PEAR2 package naming standards (namespace usage)

This is the end of this topic for me, I will be taking people's concerns into account as I updated the rfc and make sure it has more examples and is clear. On to specific concerns: Multi-level namespaces lets me type less: If you are going to create an instance more then once then use as is always less typing. If you are only going to create a single instance then the full path at that point is always less typing. Also if a package has you creating hundreds of instances by hand then there is a problem with the package design. SVN is a 3rd party program and shouldn't be a concern in the design: SVN is how we are managing code in pear2, and hopefully soon in all of PHP. It and tools with similar rules like git is how the open source world manages code. Can't an autoloader fix everything: Having packages putting files in other directories is just pain, and any autoloader that does the merging for you is a total hack, see the current code that i wrote in pear2 svn. Plus you end up with a huge number of extra directories and in the end the code is actually harder to work on. But I really want categories: I respect this argument and I see some benefit but the categorization doesn't fit for a large number of packages and it just makes names longer. I'm all for removing any prefix if its not needed like travis's diff case or calling services_shipping just shipping. If you thing this rfc is headed in the wrong direction feel free to write your own, once you find someone on the group to be your co-author, we can look at it during the next group meeting. -josh