Mailing-List: contact dev-help@forrest.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@forrest.apache.org
Received-SPF: neutral (asf.osuosl.org: local policy)
Date: Thu, 26 Jan 2006 11:10:28 +1100
From: David Crossley <crossley@apache.org>
To: dev@forrest.apache.org
Subject: Re: [jira] Updated: (FOR-617) Forrest DOAP file
Message-ID: <20060126001028.GA11209@igg.indexgeo.com.au>
References: <65263936.1123657324687.JavaMail.jira@ajax.apache.org>
 <200508112257.35550.diwaker@apache.org>
 <20060125000944.GA8855@igg.indexgeo.com.au>
 <200601242345.55376.diwaker@apache.org> <43D752E4.1030603@apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <43D752E4.1030603@apache.org>
User-Agent: Mutt/1.4i

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