On 3 November 2010 10:52, Upayavira <[email protected]> wrote: > > > On Wed, 03 Nov 2010 10:44 +0000, "sebb" <[email protected]> wrote: >> On 3 November 2010 10:28, Mads Toftum <[email protected]> wrote: >> > On Wed, Nov 03, 2010 at 10:22:35AM +0000, Upayavira wrote: >> >> How about we copy the doap files over to a writable attic location, and >> >> change the references to point to those files? >> >> >> >> That way, we can continue to update our doaps as needs require. >> >> >> > +1. Seems like the right way to go about it leaving the project >> > untouched. >> >> In that case, the Attic docs need to be updated, as they currently >> state that the DOAPs are changed. > > Delete the DOAP before removing write access? > >> Why would there be any need to update the DOAPs further? > > Because we improve projects.apache.org and require additional info in > that file?
That would cause lots of grief, so hopefully won't happen... > >> Also, having a different copy of the DOAP is likely to be confusing if >> the project emerges from the Attic. > > Good point. Hence remove it before locking down. If the DOAP is in trunk, then there will also be copies in tags and maybe branches ... > Just a suggestion - I recognise I'm not doing the work... > > Upayavira >
