Yes they recommend the key to be with an @apache.org email. But we can add an email to an existing key.
gpg --edit-key <original email or key id> We then can add an new email through the gpg cli and upload it when we're done. On Wed, Dec 18, 2019 at 2:12 PM Gregory Nutt <spudan...@gmail.com> wrote: > > > >> I saw the option to send the SSH keys, so I suppose we will need to fill it > >> later (for those who didn't it yet). > > Also if you do not have your PGP keys yet, you should do that soon. These > > are needed for cryptographically signing releases. Several people need to > > sign each release in order to release it. > > > > See: > > > > https://www.apache.org/dev/new-committers-guide.html#set-up-security-and-pgp-keys > > > > and the more detailed document here: > > > > https://www.apache.org/dev/release-signing.html > > I assume that this should be the <apache ID>@apache.org? > > Then if we have existing keys all we should have to do is: > > |gpg --edit-key <apache ID>@apache.org| > > |Right?| > > |Greg > | > > || >
