[Top][All Lists]

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

[commit-womb] gnumaint gnupackages.txt temail-0query.txt tema...

From: karl
Subject: [commit-womb] gnumaint gnupackages.txt temail-0query.txt tema...
Date: Tue, 14 May 2013 18:29:41 +0000

CVSROOT:        /sources/womb
Module name:    gnumaint
Changes by:     karl <karl>     13/05/14 18:29:40

Modified files:
        .              : gnupackages.txt 
Added files:
        .              : temail-0query.txt temail-2dub.txt 
                         temail-4post.txt tpost-need.html 

Log message:
        draft fragments for maintainer processes


Index: gnupackages.txt
RCS file: /sources/womb/gnumaint/gnupackages.txt,v
retrieving revision 1.167
retrieving revision 1.168
diff -u -b -r1.167 -r1.168
--- gnupackages.txt     27 Apr 2013 15:57:27 -0000      1.167
+++ gnupackages.txt     14 May 2013 18:29:39 -0000      1.168
@@ -1,4 +1,4 @@
-# $Id: gnupackages.txt,v 1.167 2013/04/27 15:57:27 karl Exp $
+# $Id: gnupackages.txt,v 1.168 2013/05/14 18:29:39 karl Exp $
 # Public domain.
 # This file is maintained in the CVS repository of GNU womb,
@@ -107,7 +107,7 @@
 doc-summary: Semiconductor device simulator
 doc-url: /software/archimedes/manual/
 gplv3-status: done-in-0.8.0 (14jul08)
-activity-status: ok 20111025 (2.0.0)
+activity-status: ok 20130429 (2.0.1)
 package: aris
 doc-category: Mathematics
@@ -484,7 +484,7 @@
 doc-summary: Statistics and graphics package
 doc-url: none
 gplv3-status: not-done-maintainer-wants-volunteer (4 Sep 2007 22:37:48, 28 Jan 
2008 20:23:40)
-activity-status: newmaint/20130318 20080220 (3.7)
+activity-status:ok 20130502 (3.8)
 last-contact: 19feb12,22jan12 jmd asked
 package: dc
@@ -533,7 +533,7 @@
 gplv3-status: not-done-as-of-0.8.16-old-authors?
-activity-status: ok 20130327 (1.0.0)
+activity-status: ok 20130512 (1.0.2)
 package: dia
@@ -785,7 +785,7 @@
 logo: /software/freeipmi/images/freeipmi-logo-small.jpg
 gplv3-status: in-dev-sources
 last-contact: 14jan10 replied, next major release
-activity-status: ok 20130227 (1.2.5)
+activity-status: ok 20130429 (1.2.6)
 package: freetalk
 doc-category: Internet
@@ -827,7 +827,7 @@
 doc-url: /software/gawk/manual/
 doc-url: htmlxref
 gplv3-status: done-in-3.1.6
-activity-status: ok 20121226 (4.0.2)
+activity-status: ok 20130510 (4.1.0)
 package: gcal
 copyright-holder: notfsf
@@ -1598,7 +1598,7 @@
 doc-summary: Numerical library for C and C++
 doc-url: htmlxref
 gplv3-status: done-in-1.10 (gnumaint-reply 21 Aug 2007 10:01:29)
-activity-status: newmaint/20120214 2010506 (1.15)
+activity-status: newmaint/20120214 2011506 (1.15)
 package: gsrc
 mundane-name: GNU Source Release Collection
@@ -1676,7 +1676,7 @@
 doc-summary: Guile bindings to ncurses
 doc-url: /software/guile-ncurses/manual/
 gplv3-status: done-in-0.9
-activity-status: ok 20110202 (1.3)
+activity-status: ok 20130427 (1.4)
 package: guile-rpc
 copyright-holder: fsf-ok-with-external-#786605
@@ -2023,7 +2023,7 @@
 doc-url: /software/libmicrohttpd/#using
 doc-url: /software/libmicrohttpd/manual/
 gplv3-status: depends-on-gnunet-lgplv2.1+
-activity-status: ok 20130330 (0.9.26)
+activity-status: ok 20130505 (0.9.27)
 package: libredwg
 copyright-holder: fsf-no-info-in-reply-#786464
@@ -3269,7 +3269,7 @@
 doc-summary: Graphical user interface for chess programs
 doc-url: /software/xboard/manual/
 gplv3-status: done-as-of-4.4.2
-activity-status: ok 20130220 (4.7.0)
+activity-status: ok 20130505 (4.7.1)
 package: xhippo
 doc-category: Audio

Index: temail-0query.txt
RCS file: temail-0query.txt
diff -N temail-0query.txt
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ temail-0query.txt   14 May 2013 18:29:39 -0000      1.1
@@ -0,0 +1,125 @@
+[This is generic text to send to prospective (co-)maintainers, that is,
+ before they are appointed.  Of course the intro text should be adjusted
+ to suit the case at hand.  The crucial thing is that all maintainers
+ must explicitly agree to follow GNU policies.]
+Below is our general info on policies and conventions for maintaining
+GNU programs.  Please take a look; assuming you're ok with them, we'll
+be glad to officially appoint you the new maintainer.
+GNU is not simply a collection of useful programs.  We started the GNU
+Project with a specific overall goal: to create a free software
+operating system, the GNU System.  To keep the GNU system technically
+coherent, we make sure that the parts fit well together.
+Thus, becoming a GNU maintainer is a somewhat formal process, since
+affiliating with the GNU project as a maintainer means you must agree to
+work (within the confines of the maintenance) with the GNU project's
+mission for software freedom.
+So, please read the GNU policies in the Maintainers Information and
+Coding Standards document linked at the end.  A summary of the major
+policies is appended, but the details are in the documents.
+Here's the explanation of what it means for a program to be a GNU
+package, which also explains at a general level the responsibilities
+of a GNU maintainer.
+Making a program GNU software means that its developers and the GNU
+project agree that "This program is part of the GNU project, released
+under the aegis of GNU"--and say so in the program.
+This means that we normally put the program on (although
+we can instead refer to your choice of ftp site).
+This means that the official site for the program should be on, specifically in /software/PROGRAMNAME.  Whenever you give
+out the URL for the package home page, you would give this address.
+It is ok to use another site for secondary topics, such as pages meant
+for people helping develop the package, and for running data bases.
+(We can make an exception and put the web pages somewhere else if
+there is a really pressing reason.)
+It means that the developers agree to pay attention to making the
+program work well with the rest of the GNU system--and conversely that
+the GNU project will encourage other GNU maintainers to pay attention
+to making their programs fit in well with it.
+Just what it means to make programs work well together is mainly a
+practical matter that depends on what the program does.  But there are
+a few general principles.  Certain parts of the GNU coding standards
+directly affect the consistency of the whole system.  These include
+the standards for configuring and building a program, and the
+standards for command-line options.  It is important to make all GNU
+programs follow these standards, where they are applicable.
+Another important GNU standard is that GNU programs should come with
+documentation in Texinfo format.  That is the GNU standard
+documentation format, and it can be converted automatically into
+various other formats.  You can use DocBook format or another suitable
+format for the documentation sources, as long as converting it
+automatically into Texinfo gives good results.
+If a GNU program wants to be extensible, it should use GUILE
+( as the programming
+language for extensibility--that is the GNU standard extensibility
+package.  For some programs there's a reason to do things differently,
+but please use GUILE if that is feasible.
+A GNU program should use the latest version of the license that the
+GNU Project recommends--not just any free software license.  For most
+packages, this means using the GNU GPL.
+A GNU program should not recommend use of any non-free program, and it
+should not refer the user to any non-free documentation for free
+software.  The campaign for free documentation to go with free
+software is a major focus of the GNU project (see
+; to show that we are
+serious about it, we must not undermine our position by recommending
+documentation that isn't free.
+Occasionally there are issues of terminology which are important for
+the success of the GNU project as a whole.  So we expect maintainers
+of GNU programs to follow them.  For example, the documentation files
+and comments in the program should speak of GNU/Linux systems, rather
+than calling the whole system "Linux", and should use the term "free
+software" rather than "open source".  Since a GNU program is released
+under the auspices of GNU, it should not say anything that contradicts
+the GNU Project's views.
+For a program to be GNU software does not require transferring
+copyright to the FSF; that is a separate question.  If you transfer
+the copyright to the FSF, the FSF will enforce the GPL for the program
+if someone violates it; if you keep the copyright, enforcement will be
+up to you.
+As the GNU maintainer of the package, please make sure to stay in
+touch with the GNU Project.  If we come across a problem relating to
+the package, we need to tell you about it, and to discuss with you how
+to solve it.  Sometimes we will need to ask you to work with other
+maintainers to solve a problem that involves using multiple packages
+together.  This probably will happen less than once a year, but please
+make sure we can contact you in case it does happen.
+Finally, if you decide to step down as maintainer at any time, please
+inform us (see
+More details are available in these documents:
+  Information For Maintainers of GNU Software:
+  GNU Coding Standards:
+For the basic ideas of GNU and free software, please read these essays:

Index: temail-2dub.txt
RCS file: temail-2dub.txt
diff -N temail-2dub.txt
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ temail-2dub.txt     14 May 2013 18:29:40 -0000      1.1
@@ -0,0 +1,140 @@
+From: address@hidden (Karl Berry)
+Cc: address@hidden, address@hidden
+BCC: address@hidden
+Subject: maintaining GNU 
+I hereby appoint you as the new maintainer of GNU
+Thanks for volunteering.
+Being a package maintainer is a relationship between you personally
+and the GNU Project.  The maintainer or maintainers are the ones
+who take the overall responsibility for the work done on the package.
+If you recruit others to contribute to the package (and some packages
+have hundreds of contributors), they work under your supervision.
+The GNU Project will sometimes need to talk with you, sometimes
+privately, so please make sure we know a personal email address which
+you read frequently.  We normally publish these email addresses in the
+Free Software Directory.  We would also like to know other ways to get
+in touch with you if email fails; we do not give them out.
+If you ever want to step down as maintainer, or would like someone
+else to replace you, please talk with address@hidden and address@hidden
+about it.  When a package has no maintainer, we need to know about the
+problem so we can look for a new one.  Likewise, if you think someone
+else should join you as co-maintainer or take over from you as
+maintainer, please talk with us, since we will need to establish a
+relationship with that person.
+The GNU maintainer information in
+describes a lot of procedures for GNU maintainers.  It also
+describes who you can ask for various kinds of support or advice.  If
+you encounter a situation where it isn't clear what to do, you can
+also ask address@hidden, which is a list of a few other GNU
+maintainers who have offered to answer questions for new maintainers.
+We will add you to the gnu-prog mailing list, a moderated list for
+announcements to GNU maintainers.  We will also add you to the
+gnu-prog-discuss list, which can be used for discussion among GNU
+maintainers, but whether to stay on the list is up to you.
+Please send a note to gnu-prog-discuss now with a brief description of
+your package, so that other GNU developers will learn about it.
+We strongly recommend using to make distributions
+available.  Please see the GNU maintainers guide for the procedure,
+When that is set up, you'll be able to do uploads yourself.  If you
+want to also distribute the package from a site of your own, that is
+fine.  To use some other site instead of is acceptable,
+provided it allows connections from anyone anywhere.
+Please write or update the web pages about the program, to put in
+  These pages should be the
+main web site for the program, and they should really have the
+information for users, not just a link to another site; please use
+ whenever you give out the URL
+for the home page of the program.  Please don't set up a "site for the
+program" anywhere else--if you want to do work on additional web pages
+about the program, please put them on
+(It is ok to put pages that address developers-only topics on another
+site, and likewise for pages that access databases.)
+In writing the web pages, please follow the style guidelines in
+   See also
+We ask that you register your package on Savannah, at least to maintain
+your package's web pages.  This is independent of where the actual
+program sources are hosted (although we encourage you to use Savannah
+for that too).  This makes it easy to update the web pages, since you
+will have access to a CVS repository for the web pages and can update it
+as you like.  Using Savannah will help the GNU Project in other ways,
+too.  To set this up, visit
+If your package was already being developed on Savannah as nongnu, email
address@hidden and ask them to mark it there as a GNU
+package.  This should happen without your intervention, but feel free to
+ask them if a day or two has gone by without the change being made.
+Please also write an entry or a change for the page
+, and mail that to
address@hidden  Note that we don't want to talk about
+proprietary software, so if you have worked on any, please don't
+mention it here.  Your entry can include a link to your home page
+provided it fits our usual criteria for what we link to.
+Please make sure that the program has an up-to-date entry in our Free
+Software Directory.  See  If it needs updating,
+please write address@hidden to arrange that.  See
+ for the details
+which are needed.
+Mailing lists: Your package should already have a mailing list
address@hidden for reporting bugs.  If not, please create it--see
+ for the details of
+creating mailing lists.
+Some GNU programs with many users have another mailing list,
address@hidden, for people to ask other users for help.  If
+your program has many users, you should create such a list for it.
+For a fairly new program, which doesn't have a large user base yet, it
+is better not to bother with this.
+Please post announcements of new releases of the program to
address@hidden  Include a brief description of the program so people
+can tell whether they are interested in using it.  The announcement
+should mention the web pages on, and say where to get the
+program by ftp.
+You can also send announcements to a special list address@hidden
+for your program if you think that is warranted.  (This list should be
+Please also mention release announcements in the news feed of the
+savannah project site, <>.
+The news feeds from the GNU project are aggregated at
+For more details about writing and publicizing announcements, please see
+For details on all policies and recommendations for GNU packages,
+please see the GNU maintainers information, at
+, and GNU coding standards, at
+For the basic ideas of GNU and free software, please read these essays:
+new-gnu people, could you please enter XYZ in
+gnuorg/maintainers and add him to the gnu-prog lists?

Index: temail-4post.txt
RCS file: temail-4post.txt
diff -N temail-4post.txt
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ temail-4post.txt    14 May 2013 18:29:40 -0000      1.1
@@ -0,0 +1,27 @@
+[stuff to talk to new maintainers about, right after they are appointed.]
+[a first msg.]
+[check savannah; if they aren't there, get them to create an account.]
+I added you to the gnu-prog lists.  You should have received the welcome
+msgs just before this.
+Meanwhile, can you please send me a phone number / mailing address /
+alternative email, just to have as backup?  We try to collect these for
+all GNU maintainers.  Of course we won't publicize the information
+anywhere on the web.
+Thanks for the contact info.
+Please go ahead and update any of the information at the savannah
+project and on the web pages (e.g., remove the looking-for-a-maintainer
+notice :) as needed.
+ talks about
+handling web pages, including a template you can use if you like.
+If any questions or problems with the GNU infrastructure, please feel
+free to email us (or address@hidden, as mentioned in the welcome email).
+Happy hacking,

Index: tpost-need.html
RCS file: tpost-need.html
diff -N tpost-need.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ tpost-need.html     14 May 2013 18:29:40 -0000      1.1
@@ -0,0 +1,8 @@
+<!-- blurb to put on the web pages of packages that need maintainers. -->
+<hr><p>GNU XXX is looking for a maintainer.
+If you're interested, please take a look at this <a
+href="/help/evaluation.html#whatmeans">general information about GNU
+packages and being a GNU maintainer</a>, and then email
address@hidden with a bit about your background and particular
+interest in this package.  Thanks.</p><hr>

reply via email to

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