We use mailing lists mainly to discuss anything and everything related to GNU/Linux and Open Source in general, as well as to confide core issues, and spread out announcements and important news.
Why did we go for a mailing list and not a forum?
Simple.The mailing list will assure that content is pushed to the user. We have 4 mailing lists all in all, users, announce, core and cvs.
You can subscribe to any of the lists. Core and Announce are read-only lists, as only core member discussions will take place (pertaining to policy issues, working out main events etc...).
To subscribe to the mailing lists, go to the following page: http://lists.leglug.org/mailman/listinfo
Quick Links:
Users: http://lists.leglug.org/mailman/listinfo/leglug-usersAnnounce: http://lists.leglug.org/mailman/listinfo/leglug-announce
Core: http://lists.leglug.org/mailman/listinfo/leglug-core
CVS: http://lists.leglug.org/mailman/listinfo/leglug-cvs
Mailing Lists Archive:
Users: http://lists.leglug.org/pipermail/leglug-users/Announce: http://lists.leglug.org/pipermail/leglug-announce/
Core: http://lists.leglug.org/pipermail/leglug-core/
CVS: http://lists.leglug.org/pipermail/leglug-cvs/
General email guidelines
- Text / HTML emails:
I've noticed that some people here are sending HTML emails. While there's nothing wrong with that, I would highly encourage that we strictly stick to text-only emails for several reasons. The first reason would be that this being a *nix related list, some of us might be using text-only email clients (mutt, pine, etc.), so those people do not appreciate getting HTML emails because they simply can not read them properly. The second reason is that HTML emails will make it hard for us to use the email archives for indexing and searching or any sort of conversion because it would yield fake results and would make that job harder. - Replies and consistency:
I know that this is not English class, but some rudimentary email and punctuation skills would highly improve the readability and content of the emails. When writing an email, try to use simple statements that fully express your ideas with proper punctuation in order to spare everyone the hassle of trying to decipher what you mean. When replying to emails, it is always good practice to keep the "John Smith wrote:" phrase at the top, delete any irrelevant text, keep the text you want to reply to, and reply under that text in a point by point fashion. An example would be:
*** example begin ***
On Wednesday, October 24 2006, John Smith wrote:
> I really think we should decrease the latency in the schedualer in order
> to improve performance on desktop systems.
I completely agree, but could you please illustrate more?
*** example end *** - Reply-to / Reply-to-all / Reply-to-list:
When replying to an email, if you simply hit "Reply". "Reply-to", or "Reply-to-all" you are going to end up replying to both the sender and the list, and your email might end up being received twice by the original author. To avoid giving the author a hard time, you could either use your client's (if available) "Reply-to-list" or simply delete the original author's email address from the receiver's list. I'm sure a lot of us would appreciate not getting multiple emails.