>> > I think that if GNU doesn't have the infrastructure or personnel
>> > to support these, then, yes, the Savannah administrators should
>> > fork (or just patch) cgit to the extent necessary to suppress the
>> > exposure of these snapshot download links. I had no idea they
>> > weren't truly supported. I can't be the only person who assumed
>> > that they were.
>>
>> In fact, this has caused consternation at least once before for a
>> groff user (http://lists.gnu.org/r/groff/2021-05/msg00049.html).
>> That's just one recent thread I happened to remember; I didn't
>> search to see if there were others.
>
> Yes, I remember that too.
... not only groff is affected by the non-working of daily snapshots.
For example, FreeType has exactly the same problem. IMHO, such
snapshots do more harm than good in most cases.
>> Admittedly, part of the problem in that instance is that a groff
>> project page recommends these snapshots and links to Savannah's
>> cgit interface. This is something that could be fixed on the groff
>> page, though I don't know who has the keys to
>> www.gnu.org/software/groff.
>
> Werner, do you happen to know? Is that part of Bertrand's bailiwick
> as official GNU maintainer for groff?
I don't know who has write permissions, and who is responsible for
that, sorry – I still have access to the CVS repository for the
webpages, though (i.e., `cvs -z9 update -dP` worked fine just now).
In the repository's file `CVS/Root` I have
:ext:w...@cvs.savannah.gnu.org:/web/groff
Looking into the log files I see that Peter Schaffter and Bertrand
have both access, too. The last change to the repository was 2018,
BTW.
Hope this helps. I guess it makes sense asking the Savannah people to
give you write access, too.
Werner
