Last modified: 2013-08-31 21:33:18 UTC
Problem: I'm looking at a bug about an extension I'm not completely familiar with. It has it's own bugzilla component. I want to learn more about it, usually by going to it's mediawiki.org page and/or it's gerrit repo. Solution: Lets tie the things together! BZ should "know" about those other things ("Project pages" and "code review") per component/whatever and provide that information to the user.
In some cases you can click the "Component:" link above and then scroll to the component to check if it has a link to some kind of "homepage". Especially for extensions this is often true (though I have not fixed all dumb descriptions like "Foobar: The Foobar extension. (No further info, go find out yourself!)". However, seeing the structure in Git/Gerrit (e.g. extensions/*), it's impossible to make any automated assumptions. Personally I'm waiting for CommunityMetrics to provide some mapping between {Bugzilla products/components, Gerrit repositories, Extension homepages, etc}, and my boring fallback idea would be using DOAP files for this. In both cases some code would be required to gather such info and display it in Bugzilla. Hmm.
