You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@attic.apache.org by sebb <se...@gmail.com> on 2010/11/03 10:45:06 UTC
Projects.a.o - how to handle projects in the Attic?
I originally asked this on the site-dev list (and got no reply), but
having read the Attic web-site, it looks like the DOAPs are supposed
to be updated when moved to the Attic.
I think I can grant myself permission to fix the incorrect DOAPs - is
it OK if I start on this?
=====
At present, there is just one project which is shown as being in the
Attic, which is Beehive.
The parent PMC is identified by a line in the project DOAP file, e.g.
for Beehive:
<Project rdf:about="http://beehive.apache.org">
...
<name>Apache Beehive</name>
<homepage rdf:resource="http://beehive.apache.org" />
<asfext:pmc rdf:resource="http://attic.apache.org" />
Now the DOAPs are normally in the project SVN which is marked
read-only when in the Attic.
If it is OK to update the DOAP in each Attic project, then I can start
making the changes.
WDYT?
Re: Projects.a.o - how to handle projects in the Attic?
Posted by Upayavira <uv...@odoko.co.uk>.
Mine were just suggestions - I'm quite happy for you to do as you need -
if that is to edit the doap files in trunk for relevant projects.
Upayavira
On Wed, 03 Nov 2010 11:18 +0000, "sebb" <se...@gmail.com> wrote:
> On 3 November 2010 10:52, Upayavira <uv...@odoko.co.uk> wrote:
> >
> >
> > On Wed, 03 Nov 2010 10:44 +0000, "sebb" <se...@gmail.com> wrote:
> >> On 3 November 2010 10:28, Mads Toftum <ma...@toftum.dk> 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
> >
>
Re: Projects.a.o - how to handle projects in the Attic?
Posted by sebb <se...@gmail.com>.
On 3 November 2010 10:52, Upayavira <uv...@odoko.co.uk> wrote:
>
>
> On Wed, 03 Nov 2010 10:44 +0000, "sebb" <se...@gmail.com> wrote:
>> On 3 November 2010 10:28, Mads Toftum <ma...@toftum.dk> 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
>
Re: Projects.a.o - how to handle projects in the Attic?
Posted by Upayavira <uv...@odoko.co.uk>.
On Wed, 03 Nov 2010 10:44 +0000, "sebb" <se...@gmail.com> wrote:
> On 3 November 2010 10:28, Mads Toftum <ma...@toftum.dk> 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?
> 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.
Just a suggestion - I recognise I'm not doing the work...
Upayavira
Re: Projects.a.o - how to handle projects in the Attic?
Posted by sebb <se...@gmail.com>.
On 3 November 2010 10:28, Mads Toftum <ma...@toftum.dk> 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.
Why would there be any need to update the DOAPs further?
Also, having a different copy of the DOAP is likely to be confusing if
the project emerges from the Attic.
> vh
>
> Mads Toftum
> --
> http://soulfood.dk
>
Re: Projects.a.o - how to handle projects in the Attic?
Posted by Mads Toftum <ma...@toftum.dk>.
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.
vh
Mads Toftum
--
http://soulfood.dk
Re: Projects.a.o - how to handle projects in the Attic?
Posted by Upayavira <uv...@odoko.co.uk>.
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.
Upayavia
On Wed, 03 Nov 2010 09:45 +0000, "sebb" <se...@gmail.com> wrote:
> I originally asked this on the site-dev list (and got no reply), but
> having read the Attic web-site, it looks like the DOAPs are supposed
> to be updated when moved to the Attic.
>
> I think I can grant myself permission to fix the incorrect DOAPs - is
> it OK if I start on this?
>
> =====
> At present, there is just one project which is shown as being in the
> Attic, which is Beehive.
>
> The parent PMC is identified by a line in the project DOAP file, e.g.
> for Beehive:
>
> <Project rdf:about="http://beehive.apache.org">
> ...
> <name>Apache Beehive</name>
> <homepage rdf:resource="http://beehive.apache.org" />
> <asfext:pmc rdf:resource="http://attic.apache.org" />
>
> Now the DOAPs are normally in the project SVN which is marked
> read-only when in the Attic.
>
> If it is OK to update the DOAP in each Attic project, then I can start
> making the changes.
>
> WDYT?
>