Re: [hackathon] Keysigning

2011-04-28 Thread Daniel Shahaf
Daniel Shahaf wrote on Wed, Apr 27, 2011 at 09:42:44 +0300: > So, I propose that we recommend committers to add their then-current > preferred PGP keys (used for key signing and release signing, feel free > to add other keys if you want) to ^/subversion/site/keys/$username.asc . No objections, so

Re: [hackathon] Keysigning

2011-05-02 Thread C. Michael Pilato
On 04/27/2011 02:42 AM, Daniel Shahaf wrote: > We're planning to encourage key signing during the hackathon week. > To facilitate this, we'd like to collect all the key fingerprints in > advance, in order to prepare and distribute a $spreadsheet with > fingerprints to attendees. > > At this point

Re: [hackathon] Keysigning

2011-05-02 Thread Daniel Shahaf
C. Michael Pilato wrote on Mon, May 02, 2011 at 13:20:30 -0400: > On 04/27/2011 02:42 AM, Daniel Shahaf wrote: > > to add other keys if you want) to ^/subversion/site/keys/$username.asc . > > I wonder if we couldn't reduce data duplication by instead recommending that > committers update their Apa

Re: [hackathon] Keysigning

2011-05-02 Thread C. Michael Pilato
On 05/02/2011 01:51 PM, Daniel Shahaf wrote: > C. Michael Pilato wrote on Mon, May 02, 2011 at 13:20:30 -0400: >> On 04/27/2011 02:42 AM, Daniel Shahaf wrote: >>> to add other keys if you want) to ^/subversion/site/keys/$username.asc . >> >> I wonder if we couldn't reduce data duplication by instea

RE: [hackathon] Keysigning

2011-05-03 Thread Bob Archer
> C. Michael Pilato wrote on Mon, May 02, 2011 at 13:20:30 -0400: > > On 04/27/2011 02:42 AM, Daniel Shahaf wrote: > > > to add other keys if you want) to > ^/subversion/site/keys/$username.asc . > > > > I wonder if we couldn't reduce data duplication by instead > recommending that > > committers u

Re: [hackathon] Keysigning

2011-05-05 Thread Daniel Shahaf
Daniel Shahaf wrote on Mon, May 02, 2011 at 20:51:06 +0300: > I'll start a discussion on site-dev@, and I'll post back here if > a centralized solution is up before the hackathon. The centralized solution is as follows: * Tell https://id.apache.org what your keyid or fingerprint is (after loggi