<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
рель май wrote:
<blockquote cite="midAD3C9D4C-86A4-4F6E-8162-853DDA510A94@gmail.com"
type="cite">hello.
<br>
<br>
i'm using bugzilla for my local projects and bugzilla html is very bad.
<br>
may i help you with prettify your html?</blockquote>
Absolutely! A number of the problems have already been reported in the
User Interface component in the Bugzilla product on
bugzilla.mozilla.org, where we use Bugzilla to track its own bugs. The
best way to improve Bugzilla's HTML is to look at the User Interface
component to see <a
href="http://bugzilla.mozilla.org/buglist.cgi?bug_status=NEW,ASSIGNED,REOPENED&product=Bugzilla&component=User%20Interface">what
bugs have been reported</a>, choose some bugs to fix, file new bug
reports if there aren't existing ones for the work you want to do,
attach patches, and ask reviewers to review the changes.<br>
<br>
Note that the most successful patches are small ones that fix
individual problems rather than large ones that bundle multiple
(potentially unrelated) fixes. Note also that as soon as the Bugzilla
tree reopens for 2.22 development I'll be holding weekly online UI
hackathons where each week we target a specific part of the Bugzilla
interface for improvements. Your participation in those hackathons
would be welcome!<br>
<br>
<blockquote cite="midAD3C9D4C-86A4-4F6E-8162-853DDA510A94@gmail.com"
type="cite">examples:
<br>
labels for inputs
<br>
moving colors and styles to css file
<br>
(may be) replace table menus with ul/li menus
<br>
move html code from perl code to templates</blockquote>
These changes sound good (except possibly the table->ul change,
which would depend on the particular table in question).<br>
<br>
See bugs blocking the <a
href="https://bugzilla.mozilla.org/show_bug.cgi?id=253449">Bugzilla UI
code conversion meta-bug</a> for examples of work that has already been
done in this vein.<br>
<br>
<blockquote cite="midAD3C9D4C-86A4-4F6E-8162-853DDA510A94@gmail.com"
type="cite">if i may help you, then please say me, which version to
patch - 2.18 or 2.19 ?</blockquote>
For a patch to be accepted into the Bugzilla tree for inclusion into
the next release, it should be made against the latest Bugzilla code
available in CVS. You can obtain such a version by CVS updating a
Bugzilla installation (back it up first, and don't do it on your main
production version).<br>
<br>
If you can't make your patch against the latest code from CVS, you may
be able to get away with making it against the most recent developer
release (i.e. 2.19.x at the moment) if the code you are changing hasn't
been modified since that version. But that's a risky proposition;
you're much better off working from the Bugzilla tip.<br>
<br>
-myk<br>
<br>
</body>
</html>