[PEPr] Comment on RFC::Package naming, file naming and directory structure RFC

Greg Beaver (http://pear.php.net/user/cellog) has commented on the proposal for RFC::Package naming, file naming and directory structure RFC. Comment: minor typo (ironically) under "Spelling Conventions" Abbrevitions ==> Abbreviations Another typo under "Class Structure" devided ==> divided rewording under "Exceptions": the classes have very few code the classes are defined in very few lines of code typos under "Exceptions": (e.g. Interfaces.php for interfaces of Common.php for commonly used classes). (e.g. Interfaces.php for interfaces or Common.php for commonly used classes). dicisions ==> decisions I would recommend that exceptions be discussed not on pear-dev, but instead on pear-qa typo in "Directory Structure": diretory ==> directory typo in "Other files": unitests => unit tests under "Necessary Actions": Update non-conform packages Update non-conforming packages Current packages are in general required to upgrade to get conformity. In general, current non-conforming packages should only change package names upon upgrading Regarding the above sentence, isn't this point obvious? Coming packages have to implement all of the above described rules. New packages must strictly implement the naming conventions Proposal information: http://pear.php.net/pepr/pepr-proposal-show.php?id=55 -- Sent by PEPr, the automatic proposal system at http://pear.php.net