I'm certainly not brave enough to attempt to change it, but I have often been bothered by the terminology. Subscriber is the exact right word in this case, member or employee might be a good fit, but then again, they might not. I have lists in which member, employee, and stockholder would be appropriate, but I also have a couple of lists where subscriber is the only correct word, and it is correct in all cases.
So, I'll second the suggestion to globally change the terminology, but I don't want to get out my broadaxe and try it myself!
Van
Bob Weissman wrote:
This is a linguistic subtlety in the English version of Mailman.
Maliman refers to list subscribers as "members," for example when rejecting a post from a "non-member" to a "members-only" list. This terminology is confusing in some circumstances. Here's why.
I run lists for a professional, non-profit, organization which has dues-paying members. Not all paying members subscribe to all lists, and not all subscribers are paying members. If a dues-paying member has a posting rejected to what Mailman calls a "members-only" list, he will promptly complain to me that he is, in fact, a "member." And he's right. He's just not a *subscriber* to the list in question.
In my own Mailman 2.0.11 installation, I've scoured the sources for user-visible strings and changed "member" to "subscriber" everywhere I thought it was important. I would like to suggest this become an official terminology change for future versions of Mailman.
- Bob
Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
--
Sign up now for Quotes of the Day, a handful of quotations on a theme delivered every morning. Enlightenment! Daily, for free! mailto:twisted@whidbey.com?subject=Subscribe_QOTD