11 Mailing lists administration
12 ============================
15 link:https://alioth.debian.org/mail/?group_id=30602[mailing list], to support
16 users and developers. These can administered at the following addresses:
18 - link:http://lists.alioth.debian.org/cgi-bin/mailman/admin/nut-upsuser[Nut-upsuser]
19 - link:http://lists.alioth.debian.org/cgi-bin/mailman/admin/nut-upsdev[Nut-upsdev]
23 The password is the same for all administrators, and is provided to any new
26 Best moderation practices
27 -------------------------
29 These are the general rules that apply to mailing list moderation:
32 - ACCEPT: complete entry submission (ie no need for further mail)
33 - ACCEPT: foreign reply to cross mailing list post (ex: reply from FreeIPMI
34 Al Chu to a mail from Arnaud on upsdev...)
35 - ACCEPT: people that are already members, with another address.
37 - spams: always DISCARD, not REJECT, and apply a general ban to this address.
40 - source code commits: forward the header, which mentions the changes, but
41 not the actual changes details.
42 - others (users feedback): ask for attachment compression, or using a link
45 - other (ie report or request requiring more than 1 mail): REJECT with a
46 message explaining the reason. The following can serve as a base:
49 Your message to the nut-upsXXX mailing was rejected because you must
50 suscribe to the mailing list. This is just to eradicate spam noise from
53 Use the following link to subscribe to this mailing list:
54 https://lists.alioth.debian.org/mailman/listinfo/nut-upsXXX
56 where 'XXX' can be replaced by 'user', 'dev' or 'packaging'.
61 ///////////////////////////////////////////////////////////////////////////////
68 - we will only work on the trunk for the day to day bugfixing and
69 standard modifications (what was mostly happening in Testing
71 - the trunk will be used to generate the testing releases (only using
72 the tags, after a small freeze period),
73 - bigger changes, invasive modifications and cutting edge developments
74 will have to be addressed in separate branches, until stabilization.
75 When things are ok and validated to enter the trunk, merging these
76 branches into the trunk can happen.
77 I insist on the *validation* to enter the trunk, since some changes
78 might have to wait for major releases, to match our current release
81 ///////////////////////////////////////////////////////////////////////////////