Object v. bugzilla-type confusion ... any thoughts on it?
by Matej Cepl
Hi,
so I am now in the stage, that I use default (aka trunk) for my daily
work, so I have some time to think about some higher level stuff.
Remaining exact tasks are all posted to the Tracker, so that whoever
wants to look at them and send me a patch is more than welcome.
First of all I have this confusion between type of bugzilla (i.e., URL
we are currently on in Firefox) and type of bugzilla model we use (i.e.,
in lib/main.js around line 145).
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.
This is the idea, but the problem is that I work almost exclusively on
bugzilla.redhat.com (and bit of b.m.o but I cannot do much there) so I
am afraid those two concepts got incredibly mixed together. I would
really need somebody else to start using my code on b.m.o (or elsewhere)
and hitting all those RH-centric warts.
Possible option is announce the project on some lists where other bug
triagers socialize to find more users.
Andre, BTW, do you think that there is nothing here which could be
useful on b.gnome.org?
Comments?
Best,
Matěj
--
Economics is the only discipline where two people can win a Nobel
Prize for saying exactly the opposite thing!
-- Eamonn Butler of Adam Smith Institute
on Nobel Prize awards for year 2001
13 years, 9 months
Further progress!!! [Was: Re: Bugzilla-triage-scripts-devel subscription notification]
by Matej Cepl
Dne 20.6.2010 14:07, mailman-bounces(a)lists.fedorahosted.org napsal(a):
> Philipp Kewisch<mozilla(a)kewis.ch> has been successfully subscribed to
> Bugzilla-triage-scripts-devel.
So, I have a progress ... the scripts now load a page without crash and
some parts seem to be working, also there is no jetpack-prototype
function used in any parts which are actually used for something. I
couldn't switch yet (I deadly need logger.js to be working), but we seem
to be getting closer to that. And when I get there, I think the progress
will be fast.
Matěj
--
The main idea of the pope's asking for forgiveness was not to be
afraid of the truth. DO NOT BE AFRAID OF TRUTH! We have to have
faith in the God's governing power to be able not to be afraid.
-- On NPR The Connection from March 13, 2000
13 years, 10 months
Status report
by Matej Cepl
Hi,
as promised I am sending report about the current status of my bugzilla
Jetpack scripts.
The code is now available at
http://hg.fedorahosted.org/hg/bugzilla-triage-scripts/ (Mercurial
repository, in the end I have decided that when dealing with code
related to Jetpack it is obnoxious to use git and I should rather stay
with hg). There are two branches in this repository:
a) Branch "prototype" contains production code which I currently use in
my work; it uses Jetpack-prototype (currently version 0.8). From my
point of view it is in the maintenance mode, but it is possible that
integration with other bugzillas could be done on it, as it is currently
the only code which actually works.
b) Branch "default" contains currently non-functional code for new
Jetpack-SDK.
Currently the port is not complete and there are many exceptions thrown
when it is started, but the most complicated (I think) part (inheritance
of objects) is functional, and most of the supporting code is (I
believe) done including unit tests.
Jetpack-SDK is currently not complete and I had to write some parts
which I hope will be provided by the framework (e.g., I have my
primitive version of pageMods in main.js). Some pieces are missing
(there is no equivalent of jetpack.storage.settings) and I don't think
we have to rewrite them ourselves as it should be possible to develop
script without them (and have configuration hardcoded in the code or
.json file or anywhere else).
This branch also contains HACKING file with the first attempt to write
coding guidelines.
Of course, patches are more than welcome (for anything including HACKING
-- I have just recorded my current practice there, I am open to
discussion about it).
Trac for the project is at
https://fedorahosted.org/bugzilla-triage-scripts/.
That's it, I think. Any questions?
Matěj
--
I know of no country in which there is so little independence of
mind and real freedom of discussion as in America.
-- Alexis de Tocqueville
13 years, 10 months