Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Message-ID: <4898B011.5030507@onehippo.com>
Date: Tue, 05 Aug 2008 21:54:57 +0200
From: Jeroen Reijn <j.reijn@onehippo.com>
Organization: Hippo
User-Agent: Thunderbird 2.0.0.16 (X11/20080724)
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: Import my key into the KEYS file
References: <48621C07.2000802@onehippo.com> <48622DEB.9030505@apache.org>
 <4862337C.3000203@onehippo.com> <20080707070055.GC924@igg.indexgeo.com.au>
 <488DC0E6.8070306@tuffmail.com> <20080729020211.GD3646@igg.indexgeo.com.au>
In-Reply-To: <20080729020211.GD3646@igg.indexgeo.com.au>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Gregorz,

I'm not really sure if I have the karma to do that as well, but I just 
changed the one in

http://svn.apache.org/repos/asf/cocoon/trunk/commons/KEYS

Did you copy it from there, or is the KEYS file in the dist folder 
located elsewhere in the SVN?

Regards,

Jeroen

David Crossley wrote:
> Grzegorz Kossakowski wrote:
>> David Crossley pisze:
>>> Jeroen Reijn wrote:
>>>> Thanks Carsten!
>>>>
>>>> I'll give it a try. If found this message, but it was a but inclear, but 
>>>> after reading it 3 times.. I get it. I'll give it a go. Once I commit it 
>>>> into SVN will it also appear on the /dist/ or is SVN the only place it 
>>>> has to go in?
>>> That KEYS file is a separate one to that at the /dist/ directory.
>>> Most of the files there are in SVN at
>>> https://svn.apache.org/repos/asf/cocoon/site/mirrors/
>>> but not the KEYS file. It should be, and be kept synchonised
>>> with the other one.
>> David, could elaborate on this KEYS issue?
>>
>> Here is the output of svn st:
>> [gkossakowski@minotaur /www/www.apache.org/dist/cocoon]$ svn st
>> ?      bricks-cms
>> ?      2.2
>> ?      subprojects
>> ?      KEYS
>> ?      events/gt2004
>>
>>
>> It is clear that KEYS is not maintained by SVN. Should this be changed?
> 
> Yes, as said above.
> 
> Thanks for helping with such stuff.
> 
> When faced with issues like this, i often look at
> how other projects have done it. Primarily i follow
> Apache HTTP Server, being the original project, and
> therefore most likely doing the proper stuff. So see:
> http://svn.apache.org/repos/asf/httpd/site/trunk/dist/
> Also APR because lots of old ASF hands there. So see:
> http://svn.apache.org/repos/asf/apr/site/trunk/dist
> Apache Forrest will also give some clues, as when i
> set it up as a top-level project i reviewed many other
> existing practices.
> 
> There are also notes about KEYS and such in the
> "Guide for new committers" and "Release signing"
> http://apache.org/dev/
> 
> Also Henk's guide says to put your own key at
> people.apache.org:~/.pgpkey
> 
>> As for now I'm going to just replace this file with newer version I'm going 
>> to commit right now.
> 
> That is fine as a temporary measure, and will bring that
> static file up-to-date.
> 
> -David