On Mon, 2013-03-11 at 17:09 +0100, Christian Aistleitner wrote:
On Mon, Mar 11, 2013 at 12:43:44AM +0100, Andre
Klapper wrote:
Are there some thoughts already how to make a
match between a
project in Gerrit and its related Bugzilla product/component?
[Disclaimer: I'm a fan of DOAP metadata files, if used properly.]
While DOAP looks great, is there a standard tag to specify component
etc for a bug tracker?
There are no rules how values should look like; guidelines and checks
are required. (That's what I meant with "if used properly".)
http://bugzilla.wikimedia.org/enter_bug.cgi?product=PRODUCT&component=C…
might work. Plus you could define custom parameters if wanted.
That looks like being too generic to be useful for us.
Yes, it would require strict rules for the URI values, etc.
Generic URIs are as unhelpful as empty values.
However, gerrit already comes with a meta/config ref
that already
stores the project configuration as plain git configuration. And its
publicly visible for our gerrit, so any script can use that. We could
just put something like
[bugzilla]
product = ComponentA
component = ComponentA
in there and pick it up from gerrit's hooks-bugzilla plugin.
Wasn't aware of that. Are there projects in Gerrit that don't use
bugzilla.wikimedia.org? A lot of MediaWiki extensions, I assume?
In that case we're back to the problem that you need a URI value for the
bugtracker.
Rest is offtopic and about DOAP only:
There are a few things I like about DOAP. One thing is that Apache's
DOAP files also include the programming language of a project, so it's
easier to redirect new contributors according to their skills. Or to
store who is the maintainer of a project (in theory). Or where to find
its mailing list, homepage, tarball releases, ...
I like that when I want to find out how active a project is or how large
its community is, apart from code repository activity only.
andre
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/