Hi Matěj,
finally this evening I found an hour to look a bit into this.
(Better late than never.) Sorry, was/am busy with work, university
exams, and my own guadec presentation...
Am Donnerstag, den 24.06.2010, 14:12 +0200 schrieb Matěj Cepl:
The idea is that types of objects used (i.e., MozillaBugzilla v.
RHBugzillaPage v. whatever-else-somebody-writes; could we call them
"models"?) should differentiate between the style of UI we want to have
(more complicated my style v. much lighter Philipp's style) on whatever
bugzilla we are. On the other hand scripts must distinguish between
different bugzilla instances, because of differences between them (e.g.,
does b.m.o has XML-RPC method bugzilla.updateAttachMimeType for getting
rid of all those application/octet-stream attachments?). Everything
which could be at least theoretically useful for both models should go
to their shared parent BZPage.
I expected RHBugzillaPage to be a derived class of a generic Bugzillas
extension class, but maybe I don't get the concept yet.
Looking at the available functions it looks quite powerful and probably
has the potential to supersede all those homegrown Greasemonkey scripts
that are currently around, if you/we manage to get the "critical mass"
together (advanced bugtriagers from several projects)
The GreaseMonkey script that I currently use for
bugs.maemo.org is at
http://home.arcor.de/ak-47/pub/bugsmaemoorg_triage_help.user.js and
basically is just a copy of the "Stock Answers" functionality from GNOME
Bugzilla, nothing else.
In GNOME Bugzilla stuff like the clickable "Stock answers" when you go
on any open bug report is patched into the code on the GNOME Bugzilla
server, see
http://git.gnome.org/browse/bugzilla-newer/tree/template/en/default/bug/e... and
search for "addStockLink".
I'm not aware of much other stuff that is used in GNOME Bugzilla, have
to dive deeper into your docs to say more.
Stuff like sendBugUpstream() in RHBugzillaPage definitely looks useful
for my work in
bugs.maemo.org but so far I miss a basic introduction to
the concept of all this (I suck in reading API docs because I'm a quite
bad developer).
Andre, BTW, do you think that there is nothing here which could be
useful on b.gnome.org?
I think I need more documentation to answer this (already starts at the
very beginning: What to do exactly after checking out the hg repository
and installing JetPack in Firefox by going to
https://jetpack.mozillalabs.com/install.html to get this loaded and
visible in a browser page, probably bugzilla.redhat.com?).
Many bugtriagers are no developers (I don't consider myself to be one
either) and hence need an idiotproof how-to...
Make the barrier lower to join and play around with it. :-)
Also, some documentation seems vague (RHBugzillaPage/closeSomeRelease:
"Auxiliary function to computer more complicated resolution" - what does
that mean?)
Hope this initial feedback is helpful & see you at GUADEC!,
andre
--
mailto:ak-47@gmx.net | failed
http://blogs.gnome.org/aklapper