Re: Re: [PEPr] Comment on Versioning::PCVS
| From: | Clay Loveless | Date: | Tue, 24 Oct 2006 15:38:04 +0000 |
| Subject: | Re: Re: [PEPr] Comment on Versioning::PCVS | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-44737@lists.php.net to get a copy of this message | ||
On Oct 24, 2006, at 6:40 AM, Markus Niewerth wrote:
i'am very new to PEAR, so i don't know much over naming conventions, only the stuff i read in the documentation of PEAR. I will have a look on your hints.Here it is, right in the documentation of PEAR: http://pear.php.net/manual/en/standards.php
Also i have some other questions. I read the other comments on my proposal. First i got a naming problem in my PEAR package. Now my class called Versioning_PCVS.There's a document somewhere, which I don't have a link to presently, which defines some guidelines for package naming. One of the recommendations of that document is that names be kept clear. What is "PCVS"? A person casually scanning a list of packages will think that this package isn't for the CVS versioning system, but for some system called PCVS. Why confuse people when there's an option to be more clear? I realize that the "P" is to indicate that it's for "PEAR", but no other package in the repository follows this naming convention. And, since it will be served from PEAR's site if the proposal is accepted, the P is redundant. Please drop the P.
But i saw another category called VersionControll. But it seems to me a bit too long. So i took a new category for my package. Can you give me some hints about naming the class?Sure -- don't make up new categories just because something is personally troublesome to you about an existing category name. I didn't like the name "VersionControl_" when I did the Subversion package (I'd started with VC_), but it was agreed upon by the group that "VersionControl_" was the most clear. Since you're proposing a new package related to Version Control, it goes in VersionControl_ category. Imagine if everyone who had a minor beef with category names just made up new ones? We'd have a half-dozen similar-yet-different categories scattered throughout PEAR, and chaos would then ensue. Please change the package name to "VersionControl_CVS". I do believe you'll find as the proposal goes on to the voting stage this name change will be an absolute requirement for package acceptance. -Clay -- Killersoft.com