[Top][All Lists]

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

[gfsd]Re: Being a co-maintainer of GNU Go

From: Bradley M. Kuhn
Subject: [gfsd]Re: Being a co-maintainer of GNU Go
Date: Sun, 28 Jan 2001 17:36:31 -0500
User-agent: Mutt/1.2.5i

Richard Stallman <address@hidden> wrote:
> I hereby appoint you as the new maintainer of GNU Go.

We now have co-maintainers listed of GNU Go:

Daniel Bump <address@hidden>, Gunnar Farneback <address@hidden>

Here's the typical information we send to new maintainers.  Many of these
things are likely already being done for GNU Go, since it's been around for
a while.  I send it so that Gunnar can see it.

Congratulations on becoming a new GNU maintainer!  We are happy to have you
as part of our team!  In this message, there are some final logistical
issues we need to take care of to set you up as a maintainer.

Included below is a copy of the maintainer information file, if you haven't
seen it already.  You can always find it on at
/gd/gnuorg/maintain.{text,texi} and online at  This document describes the
responsibilities of maintaining a GNU program.  If you have any questions,
please let us know.

The most important issues to note right away concerning this are the

  (0) For GNU software, we either like to (a) distribute it from, or (b) put a README there to tell users
      where they can get the program.

      If you'd like to do (a), please just send a message to
      <address@hidden> each time you make a release.  If you are able,
      please do include a m5sum of the distribution, and GPG sign the
      message, so we can authenticate that it's you making the release, and
      the file is the one you sent us.  (If you aren't able use GPG and
      m5sum, then you don't need to worry about this issue.)

      If you'd prefer (b), then please simply email <address@hidden> the
      information for the README.  Normally, in the README, we place a short
      paragraph describing what the program does, and a FTP URL where the
      source can be found.

      BTW, when you make major releases, please do send an announcement to

  (1) We would like to set up a <address@hidden> right away if it
      doesn't already exist.  This can be (a) a mailing list on the GNU
      machines, (b) a mailing list on some other machine, or (c) a simple
      aliases that forwards to you (and possibly some other interested
      parties, too).

      If you'd like (a), let <address@hidden> know, and they'll
      set it up.  If you'd like (b) or (c), please tell <address@hidden>
      know the pertinent addresses so they can set things up.

  (2) Also, please consider making a <address@hidden> list where users
      can get informal help (if it doesn't already exist).  If you already
      have such a list, please tell <address@hidden> where so we can
      forward to it.  If you don't have such a list yet, we can easily
      create one on the GNU machines---just ask <address@hidden>.

  (3) We are building a Free Software Directory, which is a directory of all
      free software that we have found.  We'd like for you to write an entry
      for your program for the Free Software Directory.  Please contact
      <address@hidden> to write an entry.

  (4) The web site for your program should be hosted at  Please send the site as a
      .tar.gz file to the GNU Web Masters <address@hidden> or ask
      <address@hidden> for an account on so that you can
      edit the webiste yourself directly.

Also, since you are a GNU maintainer, we have added you to the extremely low
traffic <address@hidden> mailing list.  Here is the charter for that list:

     gnu-prog is a moderated list. Traffic is kept to the most essential
     issues and the number of messages is kept minimal (at most a few a
     month). The reason is that we wish all active GNU programmers and
     maintainers to remain on it, including those who are only cooperating
     with the FSF (because their program has been included in GNU. The FSF
     doesn't want anyone unsubscribing because they find volume too
     high. Many members of this list have indicated they wish the volume
     kept low.

     Most inquiries should be directed to address@hidden
     instead. The members of address@hidden list expect discussion
     and lots of email.

     This list, address@hidden, is used to update all active GNU
     programmers and maintainers on changes made in GNU project policy and
     very occasionally query the community of active GNU programmers on
     programming issues of great importance. Usually, though, a query
     directly to address@hidden or address@hidden and/or a discussion on
     address@hidden is sufficient.

     address@hidden should not be mentioned in other contexts. It is meant
     to be a private mailing list. Please do not include it in mail sent to
     those not on it.

You are welcome to be on <address@hidden>, if you'd like.  You can
subscribe by sending a message to <address@hidden> or
visiting  Here's
the charter for that list:

   gnu-prog-discuss is for those who would like to discuss issues of
   programming that affect the GNU Project (e.g coding style or library

   gnu-prog-discuss should not be mentioned in other contexts. It is meant
   to be an internal mailing list. Do not include it in mail sent to those
   not on it.

   Also, gnu-prog-discuss automagically receives a unidiff of the GNU Coding
   Standards, GNU Maintainers Guide, and related documents when changes are

Please let us know if you have any questions.

Attachment: maintain.text
Description: Text document

Attachment: pgpgb7EYx0TvH.pgp
Description: PGP signature

reply via email to

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