While we're talking about name changes, we should change dbmail-adduser to dbmail-users, or something along those lines. I'd also like to replace the screwy arguments with a consistent getopt system.
I'd like to make these changes before the 2.0 release. So far we're all early adopters, and so we're accustomed to dealing with mostly-finished and partyly-polished software. Once we have a real 2.0 release, we're going to start getting lots more users who won't put up with screwy command lines and unintuitive program names. xing <[EMAIL PROTECTED]> said: > A lot of you might find this irrelevant but I think it would be a good > change regardless of how small it is. > Actually, this is exactly the kind of usability detail that can make or break DBMail for some users. Annoyance factors should certainly be minimized. [snip] > 1) dbmail-util (this is probably the most sensible replacement) > 2) dbmail-check > 3) dbmail-maint I'm a fan of dbmail-check. It's a full word and it fully explains what the program does (what exactly is maintenance? different things to different people!). My second choice is dbmail-util. It's a good name, but I think that we might want to use that name for something else, although I have no idea what. > Maintenance is one of the most frequently misspelled words in the English > dictionary which is why it has earned the distinction as being part of the > K-12 spelling test words which include other infamies such as mosquito. > > Just a little help for all the spelling challenged out there...like myself.. > Learn something new every day! Aaron
