Re: On DOAP Files and Pulse

[Behdad Esfahbod <behdad behdad org>]

On 04/17/2009 11:52 AM, Shaun McCance wrote:
> On Fri, 2009-04-17 at 10:18 +0100, Richard Hughes wrote:
> > Are we meant to install the DOAP file on the destination
> > computer, include it in the tarball or should it just live
> > in git?
>
> DOAP files are to live in git in the top-level directory
> of each module.  They should be named<module>.doap, with
> <module>  replaced with the name of the module.

Lets said, also included in the tarball.  Every file in git should be the 
tarball also.  The only exception I can imagine is something like a 
"README.git" file.


> On Thu, 2009-04-16 at 17:42 -0400, Behdad Esfahbod wrote:
> > Are we moving away from the MAINTAINERS file?
> >
> > /me doesn't like duplicate information
>
> I'm rather ambivalent about this.  I agree that duplicate
> information sucks.  Pulse can read our MAINTAINERS files
> just fine, although there are MAINTAINERS files that
> aren't quite written right.

MAINTAINERS is a GNOME-only convention.  Lets move to the more generic doap 
approach.


> On Fri, 2009-04-17 at 10:18 -0400, Dan Winship wrote:
> > Some examples of additional useful DOAP tags that pulse isn't
> > (currently) generating but which people might want to add:
> >
> >    <download-page
> > rdf:resource="ftp://ftp.gnome.org/pub/GNOME/sources/libsoup/"/>
> >    <bug-database
> > rdf:resource="http://bugzilla.gnome.org/browse.cgi?product=libsoup"/>
> >    <mailing-list
> > rdf:resource="http://mail.gnome.org/mailman/listinfo/libsoup-list"/>
>
> The templates have mailing-list.  The other two are good
> suggestions.

Can you add them to the template please?  The idea being that the template 
would include everything that maintainers are encouraged to include.


> On Fri, 2009-04-17 at 10:18 -0400, Dan Winship wrote:
> > DOAP has tags for describing source code repos too, but it
> > doesn't seem to support git. Oops.
>
> I don't think there's any reason to put this information
> in the DOAP files we store in git.  Pulse can generate
> it.  We do have to do something about the no-git-support
> thing, of course.  We have a small DOAP extensions file
> that we're using for Gnome user IDs.  We could define
> git there.  But really, that belongs upstream.

I know Pulse can do that automatically, but doap files shipped in tarballs can 
be useful in other places too.  Like by downstream tools from distributions. 
Or Google Code Search, etc.


> Also, Owen and I discussed on IRC yesterday how we
> might get module categorization on cgit, like have
> for bugzilla.  Since we're using DOAP files to seed
> cgit already, I suggested using the DOAP category
> property.  We'd have resources defined in our DOAP
> extensions file that we would use for categories.

Makes sense.


behdad