Re: Re: implementing emeritus
| From: | Klaus Guenther | Date: | Fri, 12 Mar 2004 18:44:13 +0000 |
| Subject: | Re: Re: implementing emeritus | ||
| References: | 1 2 3 4 5 6 7 8 9 10 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-26356@lists.php.net to get a copy of this message | ||
Lukas Smith wrote:
> So we expect developers to learn non developer related terms yet common
> developers terms are off limits, like "BC"?
I personally am not in favor of becoming excessively verbose. Things like
BC, CS and MFH may need to be defined somewhere, but developers generally
should understand them. We aren't writing for third-graders here. Developers
tend to easily pick up frequently used terms. After all, even "php" isn't a
commonly used word... but within the domain of web programming, it is not
hard to remember. All the useful other acronyms and abreviations spring to
mind: LASER, FAX, km, HTML, XML, etc. They are very commonly used -- enough
so that they appear in dictionaries and often are no longer capitalized. I
wouldn't want to be without them.
In this case, the term "emeritus" will not appear anywhere except in
package.xml, and then only when someone no longer wishes to actively
participate in package development. It will be merely a matter of looking it
up. Nothing complicated about that. And what if you use a word like
"retired"? There are a number of other words that could conceivably be
substituted depending on the level of English knowledge of the developer. So
it will have to be looked up anyway. Where's the problem?
Klaus