[Top][All Lists]

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

[Groff] Next release - maintainership

From: Bertrand Garrigues
Subject: [Groff] Next release - maintainership
Date: Sat, 16 Sep 2017 21:11:27 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/25.2 (gnu/linux)

Hi all,

I'm currently preparing the next release of groff (I still have to
commit a few changes in the build system but I'm not far from making a
candidate package).  In order to upload a tarball (into
and I mailed address@hidden so that they could give me
access to these ftp site, but apparently not being the official
maintainer is a problem, here is was they answered:

"The currently listed maintainer for groff is Ted Harding
<address@hidden>. Only him or an uploader nominated by him
can have their key added to the ftp server. If he has stepped down as
a maintainer this needs to be resolved prior to requesting a new
uploader key to be added. Please discuss this within the project and
request any changes in the maintainers to address@hidden When
the new maintainer(s) are added to the files then they can request
their key to be added to the ftp, alternatively they can nominate
uploaders to have their keys added too."

I can take in charge part of the job of the maintainer: the build
system, making release; I've also studied src/roff/troff source code and
I'm planning to propose changes in `troff' to support Knuth-Plass
paragraph formating algorithm (a long-term task and of course not for
the next release).  But I'm not competent for questions/bugs on macro
packages (there are currently lots of open bugs and patch requests for
macro packages) and I can't be a technical lead like Werner, I could be
at most a "co-maintainer".

So what should we do now?


Bertrand Garrigues

reply via email to

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