Possible error re Savannah in "Information for Maintainers of GNU Software"

[Tristan Miller]

Dear GNU Coding Standards maintainers,

I'm writing to report an apparent contradiction in Section 11.6.1 
("Automated Upload Registration") of the Information for Maintainers of 
GNU Software guide at 
<https://www.gnu.org/prep/maintain/maintain.html#Automated-Upload-Registration>.

The second list item in this section instructs developers to upload 
their GPG package signing key "In the 'My Account Conf' page on 
savannah".  However, that page (visible at 
<https://savannah.gnu.org/my/admin/> for logged-in users) has an "Edit 
GPG Key" section which seems to instructs developers that the proper 
place to upload their signing keys is elsewhere:

> Keys for signing releases are registered in the "Public Information"
> area of your group.


Even more confusingly, following the "Edit GPG Key" link takes you to a 
form, <https://savannah.gnu.org/my/admin/change.php?item=gpgkey>, that 
seems to accept signing keys:

> For GNU maintainers: If these keys are to be used for GNU uploads,
> you must also email them to ftp-upload@gnu.org. There is no automatic
> propagation. See the GNU Maintainer Information, node Automated Upload
> Registration.


The last three words in that message link back to Section 11.6.1 of the 
aforementioned guide.

Could you please resolve this contradiction?  Are package signing keys 
to be uploaded to the "Edit GPG Key" form of the "My Account Conf" page, 
or to the "GPG Keys Used for Releases" form of the group's "Public 
Information" page at 
<https://savannah.gnu.org/project/admin/editgroupinfo.php?group=NAME_OF_GROUP>, 
or both?  If the current wording in Section 11.6.1 is correct, then 
perhaps you could relay this information to the Savannah maintainers so 
that they can update their forms accordingly?

Regards,
Tristan

--
Usenet Big-8 Management Board
https://www.big-8.org/
board@big-8.org