Re: Sharutils maintenance

--Sig_/uZilUVfkEg0ne925.tfbECm
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Benson,

On behalf of Richard Stallman, the Chief GNUisance, I hereby appoint
you as the new maintainer of GNU Sharutils.  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, 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 [email protected] 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.

Your appointment as maintainer is provisional at first.  We'll make
your appointment full and permanent when we see that you're doing the
job.  Usually that means we see that you've made a release properly,
with the changes that the next release ought to have.  However, if
making a proper release involves a lot of work, and will therefore
take a long time, we could appoint you full maintainer when we see you
have made a good start on the job.

Please tell us the first time you're about to make a release, so we
can guide you on doing it properly following our conventions.

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 [email protected], 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.

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 or update the web pages about the program, to put in
https://www.gnu.org/software/sharutils.  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/sharutils 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/.

Please also write an entry or a change for the page
https://www.gnu.org/people/people.html, and mail that to
[email protected].  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 update the program's entry in our Free Software Directory.  See
https://www.gnu.org/help/directory.html#adding-entries for help.

Mailing lists: Your package should already have a mailing list
[email protected] for reporting bugs.  If not, please create it--see
https://www.gnu.org/prep/maintain/html_node/Mail.html for the details of
creating mailing lists.

Some GNU programs with many users have another mailing list,
[email protected], 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
[email protected].  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.

You can also send announcements to a special list [email protected]
for your program if you think that is warranted.  (This list should be
moderated.)

Please also mention release announcements in the news feed of the
savannah project site, <https://savannah.gnu.org/projects/sharutils>.
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/.

For the basic ideas of GNU and free software, please read these essays:
http://www.gnu.org/gnu/the-gnu-project.html
http://www.gnu.org/philosophy/free-sw.html
http://www.gnu.org/philosophy/categories.html
http://www.gnu.org/philosophy/compromise.html
http://www.gnu.org/philosophy/words-to-avoid.html
http://www.gnu.org/gnu/linux-and-gnu.html
http://www.gnu.org/gnu/gnu-linux-faq.html
http://www.gnu.org/philosophy/open-source-misses-the-point.html

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

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

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Now, a few comments I'd like to make :)

"Your package should already have a mailing list [email protected] for
reporting bugs." =E2=80=94 I see [email protected] is currently being u=
sed for this
purpose.  I don't know the details, so please try to learn from others (Bru=
ce,
or maybe Paul?) why a list named `bug-sharutils' doesn't currently exist.  =
If
there are no obstacles/inconveniences to keep using the `bug-gnu-utils' lis=
t,
then you can keep using it instead of creating `bug-sharutils'.

"gnuorg/maintainers" =E2=80=94 I've already updated it.


Best!
Wojtek


--
W. Kosior

website: https://koszko.org/koszko.html
fediverse: https://friendica.me/profile/koszko/profile
PGP fingerprint: E972 7060 E3C5 637C 8A4F  4B42 4BC5 221C 5A79 FD1A


On Sun, 04 May 2025 11:36:49 +0300
"Benson Muite" <[email protected]> wrote:

> Hi,
>=20
> On Sun, May 4, 2025, at 11:33 AM, W. Kosior wrote:
> > Hello again, Benson.
> > =20
> >> > Now, we'll going to have to wait a bit more time to have the Chief
> >> > GNUisance and Bruce comment on your volunteership.  Please give them=
 ~2
> >> > weeks of time, OK?   =20
> >>=20
> >> Ok. =20
> >
> > We have a green light.  Also, please accept apologies for the delay I
> > caused here.  I admit it's been more than a week since both of them
> > responded positively and it was me being busy during that time.
> > =20
>=20
> Thanks. No worries.
>=20
> >> > In the meantime, you can read the policies that GNU maintainers are
> >> > required to follow.  I am pasting them here.  Please tell if you have
> >> > any comments/questions.
> >> >   =20
> >>=20
> >> Seem ok. =20
> >
> > Do you agree to abide by the policies you were presented? =20
>=20
> Yes.
>=20
> >
> > Best
> > WK
> >
> > --
> > W. Kosior
> >
> > website: https://koszko.org/koszko.html
> > fediverse: https://friendica.me/profile/koszko/profile
> > PGP fingerprint: E972 7060 E3C5 637C 8A4F  4B42 4BC5 221C 5A79 FD1A
> >
> >
> > On Mon, 14 Apr 2025 08:10:25 +0300
> > "Benson Muite" <[email protected]> wrote:
> > =20
> >> > Now, we'll going to have to wait a bit more time to have the Chief
> >> > GNUisance and Bruce comment on your volunteership.  Please give them=
 ~2
> >> > weeks of time, OK?   =20
> >>=20
> >> Ok.
> >>  =20
> >> >
> >> > In the meantime, you can read the policies that GNU maintainers are
> >> > required to follow.  I am pasting them here.  Please tell if you have
> >> > any comments/questions.
> >> >   =20
> >>=20
> >> Seem ok. =20
>=20



--Sig_/uZilUVfkEg0ne925.tfbECm
Content-Type: application/pgp-signature
Content-Description: OpenPGP digital signature

-----BEGIN PGP SIGNATURE-----

iHUEARYKAB0WIQTpcnBg48VjfIpPS0JLxSIcWnn9GgUCaBdi2gAKCRBLxSIcWnn9
Gn+JAQC4trA4kh2gyF2oBOUFHNeaIBH/8VmnoHzpPElBcWD6WwD/eQYBCkSOlKz4
GpdEf/s261NPxGfB6Z0/xpVaqO8cAAY=
=16Gn
-----END PGP SIGNATURE-----

--Sig_/uZilUVfkEg0ne925.tfbECm--