Bruno Haible <br...@clisp.org> writes: > Hi Simon, > >> >> 1) Add a section to the gnulib manual describing what gnulib publish at >> >> ftp.gnu.org and that it is a Git bundle for archival purposes. >> >> I've pushed the patch below to start this, what do you all think? > > I would change ftp:// -> https:// (because browsers like Firefox no longer > support the 'ftp' protocol and few people have a program named 'ftp' or > 'ncftp' > installed).
Ooops, fully agree. I'll keep this change around locally until I've managed to successfully make an upload, there may be some more tweaks needed. >> >> 2) Upload a README to ftp.gnu.org/gnu/gnulib/ with a URL to that gnulib >> >> manual section. >> >> I suppose that to get a working URL, the gnulib manual on www.gnu.org >> needs to be refreshed > > Correct. > >> -- is doc/README accurate? I can try those steps >> to see if they work for me. > > I've updated doc/README just now. > >> >> 3) Prepare and upload the PGP-signed Git bundle. ... >> >> If someone add me as administrator of the 'gnulib' project on Savannah, >> I can make the upload. > > ftp uploads are not managed through savannah, but from GNU administrators. Right, I forget the details between every use of that process. However isn't the canonical set of PGP keys for a project distributed from Savannah though? If I'm signing the git bundle, it would be nice if the gnulib PGP keys on Savannah included my key. /Simon
signature.asc
Description: PGP signature
