[ALL] DOAP file placement - move out of trunk?

classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

[ALL] DOAP file placement - move out of trunk?

sebb-2-2
The DOAP files are currently held under

/commons/proper/<component>/trunk/doap_<component>.rdf

This is sort of convenient for editting, but means the doap file gets
included in tags and branches and may get included in source.
If included in source, the release date may be missing or inaccurate.

The DOAP files are only needed for building projects.apache.org, so
don't really belong as part of the source.

So I think the files should be moved out of trunk.

They could be moved into the parent directory, i.e.

/commons/proper/<component>/doap_<component>.rdf

The advantage is that it is still part of the component SVN tree; the
disadvantage is that it is slightly awkward to update, as one must
checkout the folder using --depth filesonly.

Another possibility would be to create a separate directory for all
the DOAP files.
This would create a bigger workspace, but would be slightly easier to
use - omitting the --depth qualifier would not result in a huge
accidental checkout of all tags and branches.

[Whatever directory is chosen, it would be trivial to update the
projects.a.o build config file.]

Thoughts?

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [ALL] DOAP file placement - move out of trunk?

garydgregory
Hi All,

My thought would be to leave it where it is. I only want to fiddle with one
"place" (a SVN local dir) when working and releasing a project/component.
It seems to me that moving it out is asking for it to become out of sync.

Gary


On Mon, Mar 11, 2013 at 7:30 PM, sebb <[hidden email]> wrote:

> The DOAP files are currently held under
>
> /commons/proper/<component>/trunk/doap_<component>.rdf
>
> This is sort of convenient for editting, but means the doap file gets
> included in tags and branches and may get included in source.
> If included in source, the release date may be missing or inaccurate.
>
> The DOAP files are only needed for building projects.apache.org, so
> don't really belong as part of the source.
>
> So I think the files should be moved out of trunk.
>
> They could be moved into the parent directory, i.e.
>
> /commons/proper/<component>/doap_<component>.rdf
>
> The advantage is that it is still part of the component SVN tree; the
> disadvantage is that it is slightly awkward to update, as one must
> checkout the folder using --depth filesonly.
>
> Another possibility would be to create a separate directory for all
> the DOAP files.
> This would create a bigger workspace, but would be slightly easier to
> use - omitting the --depth qualifier would not result in a huge
> accidental checkout of all tags and branches.
>
> [Whatever directory is chosen, it would be trivial to update the
> projects.a.o build config file.]
>
> Thoughts?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>


--
E-Mail: [hidden email] | [hidden email]
JUnit in Action, 2nd Ed: <http://goog_1249600977>http://bit.ly/ECvg0
Spring Batch in Action: <http://s.apache.org/HOq>http://bit.ly/bqpbCK
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory
Reply | Threaded
Open this post in threaded view
|

Re: [ALL] DOAP file placement - move out of trunk?

Stefan Bodewig
In reply to this post by sebb-2-2
On 2013-03-12, sebb wrote:

> The DOAP files are currently held under

> /commons/proper/<component>/trunk/doap_<component>.rdf

> This is sort of convenient for editting, but means the doap file gets
> included in tags and branches and may get included in source.
> If included in source, the release date may be missing or inaccurate.

> The DOAP files are only needed for building projects.apache.org, so
> don't really belong as part of the source.

> So I think the files should be moved out of trunk.

I agree with Gary, if we move them to a different place we increase the
risk they are forgotten when a new release is made.

If we agree to move them out of the components' trunks then I'd prefer a
separate directory with all DOAP files.

Stefan

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [ALL] DOAP file placement - move out of trunk?

Simone Tripodi-2
In reply to this post by sebb-2-2
In my humble opinion, DOAP files should be auto-generated and
published to public components sites.
What's the reason to distribute it in the source archive, when
releasing? DOAPs are intended to be consumed by crawlers/robots/...
and doesn't affect the build at all.

In Apache Onami we are using the Maven DOAP Plugin[1] to built it and
attach it to the site generation, it rebuilds every time the releases
history, and populates metadata just grabbing them from the POM,
avoiding manual maintenance of same metadata in two different places.
Indeed, in components I've touched, I have always had to fill missing
data of years of releases, and we often overlooked, while voting a
release, that wrong DOAPs have been included in archives - have a look
at the 1.2.2 tag of fileupload[1] where 1.2, 1.2.1 and 1.2.2 itself
are missing.

my 2 cents,
-Simo

[1] http://maven.apache.org/plugins/maven-doap-plugin/
[2] http://svn.apache.org/repos/asf/commons/proper/fileupload/tags/commons-fileupload-1.2.2/doap_fileupload.rdf

http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/


On Tue, Mar 12, 2013 at 12:30 AM, sebb <[hidden email]> wrote:

> The DOAP files are currently held under
>
> /commons/proper/<component>/trunk/doap_<component>.rdf
>
> This is sort of convenient for editting, but means the doap file gets
> included in tags and branches and may get included in source.
> If included in source, the release date may be missing or inaccurate.
>
> The DOAP files are only needed for building projects.apache.org, so
> don't really belong as part of the source.
>
> So I think the files should be moved out of trunk.
>
> They could be moved into the parent directory, i.e.
>
> /commons/proper/<component>/doap_<component>.rdf
>
> The advantage is that it is still part of the component SVN tree; the
> disadvantage is that it is slightly awkward to update, as one must
> checkout the folder using --depth filesonly.
>
> Another possibility would be to create a separate directory for all
> the DOAP files.
> This would create a bigger workspace, but would be slightly easier to
> use - omitting the --depth qualifier would not result in a huge
> accidental checkout of all tags and branches.
>
> [Whatever directory is chosen, it would be trivial to update the
> projects.a.o build config file.]
>
> Thoughts?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [ALL] DOAP file placement - move out of trunk?

Benedikt Ritter-4
Hi Simo,


2013/3/12 Simone Tripodi <[hidden email]>

> In my humble opinion, DOAP files should be auto-generated and
> published to public components sites.
> What's the reason to distribute it in the source archive, when
> releasing? DOAPs are intended to be consumed by crawlers/robots/...
> and doesn't affect the build at all.
>

As far as I understand, this was the intention of sebb's proposal (making
sure that the DOAP doesn't get included in source distributions by moving
it out of a components SVN directory).


>
> In Apache Onami we are using the Maven DOAP Plugin[1] to built it and
> attach it to the site generation, it rebuilds every time the releases
> history, and populates metadata just grabbing them from the POM,
> avoiding manual maintenance of same metadata in two different places.
> Indeed, in components I've touched, I have always had to fill missing
> data of years of releases, and we often overlooked, while voting a
> release, that wrong DOAPs have been included in archives - have a look
> at the 1.2.2 tag of fileupload[1] where 1.2, 1.2.1 and 1.2.2 itself
> are missing.
>
> my 2 cents,
> -Simo
>
> [1] http://maven.apache.org/plugins/maven-doap-plugin/
> [2]
> http://svn.apache.org/repos/asf/commons/proper/fileupload/tags/commons-fileupload-1.2.2/doap_fileupload.rdf
>
> http://people.apache.org/~simonetripodi/
> http://simonetripodi.livejournal.com/
> http://twitter.com/simonetripodi
> http://www.99soft.org/
>
>
> On Tue, Mar 12, 2013 at 12:30 AM, sebb <[hidden email]> wrote:
> > The DOAP files are currently held under
> >
> > /commons/proper/<component>/trunk/doap_<component>.rdf
> >
> > This is sort of convenient for editting, but means the doap file gets
> > included in tags and branches and may get included in source.
> > If included in source, the release date may be missing or inaccurate.
> >
> > The DOAP files are only needed for building projects.apache.org, so
> > don't really belong as part of the source.
> >
> > So I think the files should be moved out of trunk.
> >
> > They could be moved into the parent directory, i.e.
> >
> > /commons/proper/<component>/doap_<component>.rdf
> >
> > The advantage is that it is still part of the component SVN tree; the
> > disadvantage is that it is slightly awkward to update, as one must
> > checkout the folder using --depth filesonly.
> >
> > Another possibility would be to create a separate directory for all
> > the DOAP files.
> > This would create a bigger workspace, but would be slightly easier to
> > use - omitting the --depth qualifier would not result in a huge
> > accidental checkout of all tags and branches.
> >
> > [Whatever directory is chosen, it would be trivial to update the
> > projects.a.o build config file.]
> >
> > Thoughts?
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>


--
http://people.apache.org/~britter/
http://www.systemoutprintln.de/
http://twitter.com/BenediktRitter
http://github.com/britter
Reply | Threaded
Open this post in threaded view
|

Re: [ALL] DOAP file placement - move out of trunk?

Simone Tripodi-2
Hi Bene,

> As far as I understand, this was the intention of sebb's proposal (making
> sure that the DOAP doesn't get included in source distributions by moving
> it out of a components SVN directory).

my question was a remark indeed, I was not really looking for a reply.

http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/


On Tue, Mar 12, 2013 at 8:57 AM, Benedikt Ritter <[hidden email]> wrote:

> Hi Simo,
>
>
> 2013/3/12 Simone Tripodi <[hidden email]>
>
>> In my humble opinion, DOAP files should be auto-generated and
>> published to public components sites.
>> What's the reason to distribute it in the source archive, when
>> releasing? DOAPs are intended to be consumed by crawlers/robots/...
>> and doesn't affect the build at all.
>>
>
> As far as I understand, this was the intention of sebb's proposal (making
> sure that the DOAP doesn't get included in source distributions by moving
> it out of a components SVN directory).
>
>
>>
>> In Apache Onami we are using the Maven DOAP Plugin[1] to built it and
>> attach it to the site generation, it rebuilds every time the releases
>> history, and populates metadata just grabbing them from the POM,
>> avoiding manual maintenance of same metadata in two different places.
>> Indeed, in components I've touched, I have always had to fill missing
>> data of years of releases, and we often overlooked, while voting a
>> release, that wrong DOAPs have been included in archives - have a look
>> at the 1.2.2 tag of fileupload[1] where 1.2, 1.2.1 and 1.2.2 itself
>> are missing.
>>
>> my 2 cents,
>> -Simo
>>
>> [1] http://maven.apache.org/plugins/maven-doap-plugin/
>> [2]
>> http://svn.apache.org/repos/asf/commons/proper/fileupload/tags/commons-fileupload-1.2.2/doap_fileupload.rdf
>>
>> http://people.apache.org/~simonetripodi/
>> http://simonetripodi.livejournal.com/
>> http://twitter.com/simonetripodi
>> http://www.99soft.org/
>>
>>
>> On Tue, Mar 12, 2013 at 12:30 AM, sebb <[hidden email]> wrote:
>> > The DOAP files are currently held under
>> >
>> > /commons/proper/<component>/trunk/doap_<component>.rdf
>> >
>> > This is sort of convenient for editting, but means the doap file gets
>> > included in tags and branches and may get included in source.
>> > If included in source, the release date may be missing or inaccurate.
>> >
>> > The DOAP files are only needed for building projects.apache.org, so
>> > don't really belong as part of the source.
>> >
>> > So I think the files should be moved out of trunk.
>> >
>> > They could be moved into the parent directory, i.e.
>> >
>> > /commons/proper/<component>/doap_<component>.rdf
>> >
>> > The advantage is that it is still part of the component SVN tree; the
>> > disadvantage is that it is slightly awkward to update, as one must
>> > checkout the folder using --depth filesonly.
>> >
>> > Another possibility would be to create a separate directory for all
>> > the DOAP files.
>> > This would create a bigger workspace, but would be slightly easier to
>> > use - omitting the --depth qualifier would not result in a huge
>> > accidental checkout of all tags and branches.
>> >
>> > [Whatever directory is chosen, it would be trivial to update the
>> > projects.a.o build config file.]
>> >
>> > Thoughts?
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: [hidden email]
>> > For additional commands, e-mail: [hidden email]
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>>
>
>
> --
> http://people.apache.org/~britter/
> http://www.systemoutprintln.de/
> http://twitter.com/BenediktRitter
> http://github.com/britter

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [ALL] DOAP file placement - move out of trunk?

sebb-2-2
In reply to this post by Simone Tripodi-2
On 12 March 2013 07:26, Simone Tripodi <[hidden email]> wrote:
> In my humble opinion, DOAP files should be auto-generated and
> published to public components sites.

Provided that it is possible to control the contents adequately, that
seems sensible.

> What's the reason to distribute it in the source archive, when
> releasing? DOAPs are intended to be consumed by crawlers/robots/...
> and doesn't affect the build at all.

Indeed, that is my point.

> In Apache Onami we are using the Maven DOAP Plugin[1] to built it and
> attach it to the site generation, it rebuilds every time the releases
> history, and populates metadata just grabbing them from the POM,
> avoiding manual maintenance of same metadata in two different places.

But Onami does not appear in projects.apache.org!

I could not find the Onami DOAP - where is it?

> Indeed, in components I've touched, I have always had to fill missing
> data of years of releases, and we often overlooked, while voting a
> release, that wrong DOAPs have been included in archives - have a look
> at the 1.2.2 tag of fileupload[1] where 1.2, 1.2.1 and 1.2.2 itself
> are missing.

Which suggests that having the doap in trunk does not actually help
with ensuring it is updated.
It would be easier to fix up the manually created doaps if they were
all in one directory.

> my 2 cents,
> -Simo
>
> [1] http://maven.apache.org/plugins/maven-doap-plugin/
> [2] http://svn.apache.org/repos/asf/commons/proper/fileupload/tags/commons-fileupload-1.2.2/doap_fileupload.rdf
>
> http://people.apache.org/~simonetripodi/
> http://simonetripodi.livejournal.com/
> http://twitter.com/simonetripodi
> http://www.99soft.org/
>
>
> On Tue, Mar 12, 2013 at 12:30 AM, sebb <[hidden email]> wrote:
>> The DOAP files are currently held under
>>
>> /commons/proper/<component>/trunk/doap_<component>.rdf
>>
>> This is sort of convenient for editting, but means the doap file gets
>> included in tags and branches and may get included in source.
>> If included in source, the release date may be missing or inaccurate.
>>
>> The DOAP files are only needed for building projects.apache.org, so
>> don't really belong as part of the source.
>>
>> So I think the files should be moved out of trunk.
>>
>> They could be moved into the parent directory, i.e.
>>
>> /commons/proper/<component>/doap_<component>.rdf
>>
>> The advantage is that it is still part of the component SVN tree; the
>> disadvantage is that it is slightly awkward to update, as one must
>> checkout the folder using --depth filesonly.
>>
>> Another possibility would be to create a separate directory for all
>> the DOAP files.
>> This would create a bigger workspace, but would be slightly easier to
>> use - omitting the --depth qualifier would not result in a huge
>> accidental checkout of all tags and branches.
>>
>> [Whatever directory is chosen, it would be trivial to update the
>> projects.a.o build config file.]
>>
>> Thoughts?
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [ALL] DOAP file placement - move out of trunk?

Simone Tripodi-2
Hi, Seb

>
> But Onami does not appear in projects.apache.org!
>
> I could not find the Onami DOAP - where is it?
>

each Onami's component website's page has a <link /> element which
points to its related DOAP, i.e.

 * the main site <http://onami.incubator.apache.org/> points to the parent doap:

<link title="DOAP" rel="meta" type="application/rdf+xml"
href="http://onami.incubator.apache.org/doap_org.apache.onami.parent.rdf"/>

 * the onami-logging component
<http://onami.incubator.apache.org/logging/> points to

<link title="DOAP" rel="meta" type="application/rdf+xml"
href="http://onami.incubator.apache.org/logging/doap.rdf"/>

and so on.

HTH,
-Simo

http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]