Fwd: GNU Fussy

[Sanjay Bhatnagar]

Hi,

Our project, named "fussy" was dubbed a GNU package recently -- GNU Fussy
and I, Sanjay Bhatngar, is it's maintainer.  The entire message from RMS is
copied below.

The project is hosted on Savannah (
https://savannah.nongnu.org/projects/fussy) but is still marked as
"nongnu".  The email from RMS requested that I write to
savannah-help-public mailing list if after a few days fussy project is not
automatically marked as "gnu" (see excerpt from his email below).  Could
someone please do the needful (mark fussy as a gnu project)?  I assume that
once that happens, the address for fussy will become
https://savannah.gnu.org/projects/fussy (or something similar).

Thanks.

sanjay


From: Richard Stallman <address@hidden>
Date: Mon, Jan 27, 2020 at 7:56 PM
Subject: GNU Fussy
To: Sanjay Bhatnagar <address@hidden>
Cc: <address@hidden>, <address@hidden>, <address@hidden>

:
:
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.

---------- Forwarded message ---------
From: Richard Stallman <address@hidden>
Date: Mon, Jan 27, 2020 at 7:56 PM
Subject: GNU Fussy
To: Sanjay Bhatnagar <address@hidden>
Cc: <address@hidden>, <address@hidden>, <address@hidden>


[[[ To any NSA and FBI agents reading my email: please consider    ]]]
[[[ whether defending the US Constitution against all enemies,     ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

I hereby dub Fussy a GNU package -- GNU Fussy -- and appoint
you as its maintainer.

Please don't forget to mention prominently in the README file and
other suitable documentation places that it is a GNU program.

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, on
behalf of the GNU Project.  The maintainers generally make the
specific decisions about the package, following the project's general
standards and principles.  Once in a rare while, perhaps once every
few years, the GNU Project may make a concrete decision about the
package -- about features or implementation methods for the code, or
about text in accompanying files -- which you as maintainer should
implement.

If you recruit others to contribute to the package (and some packages
have hundreds of contributors), they work under your supervision.  You
can delegate some of your authority to them, but you can also take it
back.  Please make sure they don't come to think that you have ceded
your authority to them and that they no longer have to follow your
directions.

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 about it.
When a package has no maintainer, we need to know about the problem so
we can look for a new one.  The program remains a GNU package
unless/until the GNU project decides to drop ties with it.

Likewise, if you think someone else should join you as co-maintainer
or take over from you as maintainer, please suggest that to us, since
we will need to establish a relationship with that person.  A person
cannot become a GNU package maintainer except by being appointed by
the GNU Project.

The GNU maintainer information in https://www.gnu.org/prep/maintain/
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 now with a brief description of
your package, so that other GNU developers will learn about it.

We strongly recommend using ftp.gnu.org to make distributions
available.  Please see the GNU maintainers guide for the procedure,
https://www.gnu.org/prep/maintain/html_node/Automated-FTP-Uploads.html.
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 ftp.gnu.org is acceptable,
provided it allows connections from anyone anywhere.

Please write some useful web pages about the program, to put in
https://www.gnu.org/software/PROGNAME.  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
https://www.gnu.org/software/PROGNAME 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 www.gnu.org.

(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
https://www.gnu.org/server/fsf-html-style-sheet.html.  See also
https://www.gnu.org/prep/maintain/html_node/Web-Pages.html.

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 https://savannah.gnu.org/.

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
https://www.gnu.org/people/people.html, 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 create or update the entry for your program in
directory.fsf.org.  It will then be reviewed by (one of) the directory
admin(s).  Please update the package's entry when they release
software updates.  See
https://www.gnu.org/help/directory.html#adding-entries for help.

Mailing lists: please see
https://www.gnu.org/prep/maintain/html_node/Mail.html for the details of
creating mailing lists.  Every GNU package should have at least one,
address@hidden, for reporting bugs.

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 mail an announcement to address@hidden about the existence of
the program, either when the program is released, or now if the
program is already released.  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 www.gnu.org and say
where to get releases, normally ftp.gnu.org.

Once your program is released, you should make announcements of new
releases.  Please send them to address@hidden; you can also send them
to a special list address@hidden for your program if you think
that is warranted.  (These lists should be moderated.)

Please also mention release announcements in the news feed of the
savannah project site, <https://savannah.gnu.org/projects/PROGNAME>.
The news feeds from the GNU project are aggregated at
<https://planet.gnu.org/>.

For more details about writing and publicizing announcements, please see
https://www.gnu.org/prep/maintain/html_node/Announcements.html.

For details on all policies and recommendations for GNU packages,
please see the GNU maintainers information, at
https://www.gnu.org/prep/maintain/, and GNU coding standards, at
https://www.gnu.org/prep/standards/.

new-gnu people, could you please enter Sanjay Bhatnagar in
gnuorg/maintainers and add him to the gnu-prog lists?

Savannah hackers, could you please ensure that Sanjay Bhatnagar is an
administrator of the project on Savannah (if there is one)?

-- 
Dr Richard Stallman
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)




-- 
संजय