savannah-cvs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Savannah-cvs] [219] more on gnu-prog[+discuss] and info-gnu; rm direct


From: karl
Subject: [Savannah-cvs] [219] more on gnu-prog[+discuss] and info-gnu; rm direct link to gnu-prog
Date: Fri, 2 Sep 2016 15:40:36 +0000 (UTC)

Revision: 219
          
http://svn.sv.gnu.org/viewvc/?view=rev&root=administration&revision=219
Author:   karl
Date:     2016-09-02 15:40:33 +0000 (Fri, 02 Sep 2016)
Log Message:
-----------
more on gnu-prog[+discuss] and info-gnu; rm direct link to gnu-prog

Modified Paths:
--------------
    trunk/sviki/MailingListNotes.mdwn

Modified: trunk/sviki/MailingListNotes.mdwn
===================================================================
--- trunk/sviki/MailingListNotes.mdwn   2016-08-30 21:08:06 UTC (rev 218)
+++ trunk/sviki/MailingListNotes.mdwn   2016-09-02 15:40:33 UTC (rev 219)
@@ -1,15 +1,11 @@
 Mailing List Notes
 ==================
 
-I wanted a place to keep notes about mailing lists.  I expect to keep
-adding notes here about the mailing lists.
+gnu-prog[+discuss] subscription requests?
+-----------------------------------------
+Membership in the gnu-prog and gnu-prog-discuss mailing lists is
+restricted to direct GNU contributors, and thus moderated.
 
-gnu-prog subscription requests?
--------------------------------
-
-The [gnu-prog mailing list](https://lists.gnu.org/mailman/admin/gnu-prog)
-is a moderated and private list.  Membership is moderated.
-
 Question: Is there a recipe for knowing when to approve and when to
 discard subscription requests?
 
@@ -19,6 +15,44 @@
     - ok to approve.
 2. If the person has an account on fencepost,
     - ok to approve.
-3. If the person is a member of GNU package(s) on Savannah,
+3. If the person is a member of GNU (not nongnu) package(s) on Savannah,
     - ok to approve.
 4. When in doubt, ask address@hidden before approving.
+
+gnu-prog posting
+----------------
+All members of gnu-prog should remain moderated.  Postings should be
+approved if they are announcements intended for the whole GNU community.
+Replies should be discarded; they should go to gnu-prog-discuss, which
+should happen automatically, but sometimes doesn't.
+
+gnu-prog-discuss posting
+------------------------
+gnu-prog-discuss is a normal discussion list, with the exception of the
+restricted membership.  Alternate addresses for members should be
+allowed/approved for posting, etc.  Replies are ok.
+
+As described in the maintainers guide, it is best if neither gnu-prog
+nor gnu-prog-discuss are ever included in cross-postings including other
+lists, or people not on the lists, but humans being human, sometimes
+that happens, and it's ok to approve such posts for gnu-prog-discuss,
+but not gnu-prog.  Messages to gnu-prog should be specifically and only
+to gnu-prog.
+
+info-gnu posting
+----------------
+info-gnu is a public list for announcements of interest to anyone using
+GNU software, new official releases of GNU packages and, very
+occasionally, for beta releases.  Announcements of non-GNU packages or
+other non-GNU activities are not accepted.  Replies should be discarded.
+
+Furthermore, announcements, even of GNU releases, should follow the
+usual terminology for GNU community, such as "free software" and not
+"open source".  Such posts should be returned to the poster with an
+explanation; all GNU authors should be familiar with them and be
+following them already but, humans being human, sometimes they don't.
+These rules are explicated in the maintainers guide; if you are not
+comfortable with applying them, do not touch the list.
+
+Subscription to info-gnu is open.  Members should remain moderated so
+that each post can be read by a human before approving.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]