Re: Re: Renaming "Recommendations"

Stefan Neufeind wrote:

some much different to a "standard"? As Lukas put it, people are afraid if they read of too many "standards" they are demanded to support.

Standards or conventions, they are required (expected?) to follow them anyway. The way I see it is that if they are afraid, maybe they are not ready to maintain a PEAR module. How about "Coding requirements?". Simply putting the name "coding" seems to be a little bit more descriptive to me. Personnaly, as Greg suggested, I tend to like "Coding Guidelines". You never have to follow the guide, but you might get lost in the woods if you don't ;) Oliver -- GB/E/IT d+ s+:+ a-- C++$ UL++++$ P++++ L+++$ E- W++$ N- ?o ?K w--(---) !O M+$ V- PS+ PE- Y PGP t++ 5-- X+@ R- tv++ b++(+++) DI++++ D+ G++ e+>++ h(*) r y+(?)