The DOAP template files in Pulse are just there to help maintainers put actual DOAP files in their repositories. In addition to providing a description for cgit, these DOAP files can be then used by Pulse itself.
The notion is that Pulse will be able to serve DOAP files for any module. It will cull information from various sources, including the DOAP files we put in git as well as all the jazz it crawls over now. If people want to access DOAP files for Gnome projects, they should then get them from Pulse. I want to address some questions and misconceptions. 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. 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. 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. 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. On Fri, 2009-04-17 at 16:38 +0200, Patryk Zawadzki wrote: > I'd love to see an extension that lets you also list build- and > runtime dependencies per release so I don't have to constantly > re-read configure.am in vim every time a package is updated ;) Pulse could compute that automatically and put that into its generated DOAP files. 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. -- Shaun _______________________________________________ desktop-devel-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/desktop-devel-list
