Re: On DOAP Files and Pulse

On 04/17/2009 01:32 PM, Shaun McCance wrote:

I thought MAINTAINERS was a GNU convention, but that we had
our own quasi-format for it that we introduced a short while
ago for Mango.

My memory is that it's not a GNU convention, and indeed I can't find it in GNU Coding Standards. Another proof being that autotools doesn't automatically distribute it.

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:

The templates have mailing-list.  The other two are good
Can you add them to the template please?  The idea being that the template
would include everything that maintainers are encouraged to include.


Cool.  Can you change this:

  <download-page rdf:resource="$name/"; />


  <download-page rdf:resource="$name/"; />

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.

Good point.  What information would we want in shipped
DOAP files?  We certainly don't want maintainers to have
to put lots of computable information in there.  We could
build tarball DOAP files from git DOAP files, plus extra
information we can ascertain.

Sure.  We can include in git and generate pango.doap from it.

Some of the things Pulse can do are pretty straightforward,
and we could put that code into a tool in gnome-common or
something.  But some other things can't be done without
hitting the net, like releases.

Feel free to elaborate here or in any other list.

I'm looking into adding ChangeLog generation as well as .gitignore generation rules into gnome-common. What other interesting stuff is desired across all modules?



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]