We should probably go with
https://people.apache.org/keys/group/qpid-pmc.ascfor the URL as
suggested in the mail. The other one looks nicer but the PMC
group is really the one that counts.

I'm only really interested in removing the KEYS file from our main code
repo, I'd be happy either way whether there is still one on the mirrors or
not. I'm not clear if there is a preferred process here as it seems the
documentation was never written: "*Note:* this system will be replaced by a
better process in the near future" :P

I had a quick look at some of the other projects to see what they do and
most of them still were distributing a KEYS file in the mirror system.
Hadoop had notes to generate that file using the URL, and I couldnt spot
one in the HTTPD repo but they do have it on the mirrors, whereas the rest
just seemed to still have one in their repo. Of the projects I looked at,
Subversion was the only one that referred to the key group URL on their
site and didn't distribute a file in the mirrors.

Robbie

On 8 February 2014 11:27, Justin Ross <[email protected]> wrote:

> On Thu, Feb 6, 2014 at 12:16 PM, Justin Ross <[email protected]> wrote:
> >> Given this, I wondered if we should look to adopt the updated process
> for
> >> signing keys and get round to removing the KEYS file now as well? We
> could
> >> possibly leave an otherwise empty file including a link to the new home.
> >
> > Sounds good to me.  I'll give it a try.
>
> I took a look, and everything seems to be in order.  Ted, Rafi, you,
> and I have the expected keys under
>
>   https://people.apache.org/keys/group/qpid.asc
>
> I need to update the website to reference the above URL rather than
> the KEYS file.  After that, I believe we're ready to remove it*.
> Please let me know if I missed any steps.
>
> [*] Or change its contents as you suggest.  I think my preference is
> just to remove it.
>
> Justin
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to