| 1 2 3 4 5 6 | ||
|
Editor: karlberry
Time: 2011/11/15 00:21:25 GMT+0 |
||
| Note: typos, rewording | ||
changed: - - savannah-help-public@gnu.org: alias to savannah-hackers@gnu.org; sv-hackers was not renamed so that archives urls stay valid. - savannah-help-public@gnu.org: alias to savannah-hackers@gnu.org; sv-hackers was not renamed so that archive urls stay valid. changed: - - system-hackers-announce@gnu.org: Announcements of FSF sysadmin issues, which may effect Savannah. - - - system-hackers@gnu.org: For people interested in helping with the issues announced in the announce list etc. The point is that both FSF employees and Savannah volunteers can (and do) subscribe to this list. This list is open to GNU maintainers. - system-hackers-announce@gnu.org: Announcements of FSF sysadmin issues which may affect Savannah. - system-hackers@gnu.org: For people interested in helping with the issues announced in the announce list, etc. The point is that both FSF employees and Savannah volunteers can (and do) subscribe to this list. This list is open to GNU maintainers. changed: - - savannah-announce@gnu.org - to be developed announcement list. Check SavannahAnnounce. - savannah-announce@gnu.org - announcement list. Front page news items are automatically sent here. Check SavannahAnnounce. removed: - All the 'savannah-*' posts are hand-checked so you do not risk receiving spam. changed: - However all non-spam posts are accepted - there is no "moderation". All non-spam posts are accepted - there is no "moderation".
As a general guideline we use public lists as much as possible (searchable archives, transparency...). Private lists are provided for users who wish to communicate about confidential matters, or when the Savannah Hackers need a private discussion (immediate security issue).
Try to keep the carbon-copy list intact when you reply to e-mails, unless you think this is needed (in which case, explain briefly why and who you added/removed from Cc: list) :)
Users do not receive notification when their message is being held, so as to prevent "backscatter" spam. All non-spam posts are accepted - there is no "moderation".
Check https://savannah.gnu.org/mail/?group=administration for more information.
ToDo: Check /com/mailer/aliases and clean-up savannah-related stuff, including savannah-compromise and savannah-daily-reports
ToDo: deal with savannah-compromise, an alias of sv-root. We could move it to sv-ha-priv, after checking the archive at fencepost.
root, postmaster, hostmaster, admin, and webmaster for both savannah.gnu.org and savannah.nongnu.org point to savannah-hackers-private.
Useful for, eg. CAcert.org that uses those adresses to reach a domain owner.
#savannah on irc.oftc.net is a real-time medium meant to synchronize each other when working at the same time.
Savannah's ChangeLog? is monitored by diffmon and sent to savannah-hackers-private The one at lists.gnu.org isn't.
savannah-root was once used as an alias for root@sv, hosted private discussions, and received savannah-compromise. List is now closed.