You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by David Crossley <cr...@apache.org> on 2006/01/25 01:09:44 UTC
Re: [jira] Updated: (FOR-617) Forrest DOAP file
The new http://projects.apache.org/ is now
available. Forrest is not yet listed.
Do we need to change our DOAP file [1]
or maybe transform into a different syntax?
[1] http://forrest.apache.org/doap.xml
Will it still serve the existing purpose
or do we need to maintain two files?
There are some guidelines at the site.
See some example DOAP RDF at each project
listing.
When it is ready, then Ross or i can add
it to the list in the "site-tools' SVN.
infrastructure/site-tools/trunk/projects/files.xml
-David
Re: [jira] Updated: (FOR-617) Forrest DOAP file
Posted by David Crossley <cr...@apache.org>.
David Crossley wrote:
> Ross Gardler wrote:
> > Diwaker Gupta wrote:
> > >David Crossley wrote:
> > >
> > >>The new http://projects.apache.org/ is now
> > >>available. Forrest is not yet listed.
> > >>
> > >>Do we need to change our DOAP file [1]
> > >>or maybe transform into a different syntax?
> > >>[1] http://forrest.apache.org/doap.xml
> > >>
> > >>Will it still serve the existing purpose
> > >>or do we need to maintain two files?
> > >
> > >I had created the aforementioned file to facilitate indexing in O'Reilly's
> > >CodeZoo [2]. The current doap.xml is not really a DOAP file -- its
> > >actually an ATOM feed, that contains an embedded DOAP spec as an entry. My
> > >bad in not naming it appropriately.
> > [2] http://codezoo.com/
> >
> > I've not looked at the final code for projects.a.o but the original code
> > acepted the DOAP as either a DOAP or an ATOM feed of a DOAP. I hope that
> > this feature has been kept.
>
> I noticed yesterday that David Reid added [1] to
> the list of descriptors. Now we show up and our page
> has the basic info. So your hope is satisfied.
>
> We should try adding some of the ASF-specific info.
I have done some of that over the last few weeks.
See the current result at:
http://projects.apache.org/projects/forrest.html
Would Forrest developers please review the
categories that i have assigned:
build-management, database, graphics, http,
network-client, network-server, web-framework, xml
The idea of categories is to create linkages
between projects.
The definitions are at:
http://projects.apache.org/categories.html
One thing that is not yet done, is to define
the standards that we implement. See Apache FOP
for example.
http://projects.apache.org/guidelines.html
http://projects.apache.org/doap-extensions.html
How do we modify the one at O'Reilly CodeZoo [2] above.
I thought that it automatically picked up our changes
but evidently not.
-David
Re: [jira] Updated: (FOR-617) Forrest DOAP file
Posted by David Crossley <cr...@apache.org>.
Ross Gardler wrote:
> Diwaker Gupta wrote:
> >David Crossley wrote:
> >
> >>The new http://projects.apache.org/ is now
> >>available. Forrest is not yet listed.
> >>
> >>Do we need to change our DOAP file [1]
> >>or maybe transform into a different syntax?
> >>[1] http://forrest.apache.org/doap.xml
> >>
> >>Will it still serve the existing purpose
> >>or do we need to maintain two files?
> >
> >I had created the aforementioned file to facilitate indexing in O'Reilly's
> >CodeZoo [2]. The current doap.xml is not really a DOAP file -- its
> >actually an ATOM feed, that contains an embedded DOAP spec as an entry. My
> >bad in not naming it appropriately.
>
> I've not looked at the final code for projects.a.o but the original code
> acepted the DOAP as either a DOAP or an ATOM feed of a DOAP. I hope that
> this feature has been kept.
I noticed yesterday that David Reid added [1] to
the list of descriptors. Now we show up and our page
has the basic info. So your hope is satisfied.
We should try adding some of the ASF-specific info.
-David
> >So what we need to do is:
> >
> >o create a proper DOAP file for Forrest. There's even a web-based form to
> >help creating/updating it [3]
>
> May not be necessary, see above, but also see below.
>
> There are also a number of RDF additions to the DOAP format in the file
> requried by projects.a.o. So we need to add those, hopefully they have
> been documented at projects.a.o (not had time to look yet). If not then
> I guess a look over the httpd DOAP will show the full range of
> additional info since David Reid (who wrote the scripts for this) is an
> HTTPD dev.
>
> >o make sure the embedded DOAP in the Atom feed (rename the current
> >doap.xml to atom.xml?) remains in sync with the actual DOAP.
>
> If it is necessary then we should add a pipeline to the projectinfo
> plugin that creates the Atom feed from the DOAP file.
>
> In fact, it may be a good idea to do it this way anyway, then we are
> able to provide both formats. Maybe we should ewven think about
> providing a pattern that strips out all the additional rdf info just in
> case it messes with external applications (I don't think it wil though).
>
> Ross
Re: [jira] Updated: (FOR-617) Forrest DOAP file
Posted by Ross Gardler <rg...@apache.org>.
Diwaker Gupta wrote:
> On Tuesday 24 January 2006 4:09 pm, David Crossley wrote:
>
>>The new http://projects.apache.org/ is now
>>available. Forrest is not yet listed.
>>
>>Do we need to change our DOAP file [1]
>>or maybe transform into a different syntax?
>>[1] http://forrest.apache.org/doap.xml
>>
>>Will it still serve the existing purpose
>>or do we need to maintain two files?
>
>
> I had created the aforementioned file to facilitate indexing in O'Reilly's
> CodeZoo [2]. The current doap.xml is not really a DOAP file -- its actually
> an ATOM feed, that contains an embedded DOAP spec as an entry. My bad in not
> naming it appropriately.
I've not looked at the final code for projects.a.o but the original code
acepted the DOAP as either a DOAP or an ATOM feed of a DOAP. I hope that
this feature has been kept.
> So what we need to do is:
>
> o create a proper DOAP file for Forrest. There's even a web-based form to help
> creating/updating it [3]
May not be necessary, see above, but also see below.
There are also a number of RDF additions to the DOAP format in the file
requried by projects.a.o. So we need to add those, hopefully they have
been documented at projects.a.o (not had time to look yet). If not then
I guess a look over the httpd DOAP will show the full range of
additional info since David Reid (who wrote the scripts for this) is an
HTTPD dev.
> o make sure the embedded DOAP in the Atom feed (rename the current doap.xml to
> atom.xml?) remains in sync with the actual DOAP.
If it is necessary then we should add a pipeline to the projectinfo
plugin that creates the Atom feed from the DOAP file.
In fact, it may be a good idea to do it this way anyway, then we are
able to provide both formats. Maybe we should ewven think about
providing a pattern that strips out all the additional rdf info just in
case it messes with external applications (I don't think it wil though).
Ross
Re: [jira] Updated: (FOR-617) Forrest DOAP file
Posted by Diwaker Gupta <di...@apache.org>.
On Tuesday 24 January 2006 4:09 pm, David Crossley wrote:
> The new http://projects.apache.org/ is now
> available. Forrest is not yet listed.
>
> Do we need to change our DOAP file [1]
> or maybe transform into a different syntax?
> [1] http://forrest.apache.org/doap.xml
>
> Will it still serve the existing purpose
> or do we need to maintain two files?
I had created the aforementioned file to facilitate indexing in O'Reilly's
CodeZoo [2]. The current doap.xml is not really a DOAP file -- its actually
an ATOM feed, that contains an embedded DOAP spec as an entry. My bad in not
naming it appropriately.
So what we need to do is:
o create a proper DOAP file for Forrest. There's even a web-based form to help
creating/updating it [3]
o make sure the embedded DOAP in the Atom feed (rename the current doap.xml to
atom.xml?) remains in sync with the actual DOAP.
[2] http://codezoo.com
[3] http://projects.apache.org/create.html
Diwaker
--
Web/Blog/Gallery: http://floatingsun.net
On Apache: http://people.apache.org/~diwaker