Bugzilla CSS plan

[Myk Melez]

Christian Robottom Reis wrote:

>Maybe. Maybe skins are mainly coming up as an alternative to the sorry
>state of our user interface.
>  
>
Maybe, but I don't think so.  Skins are coming up because people see and 
want their promise of flexibility.  Even once our UI doesn't suck 
anymore (or sucks less) we'll still see lots of local customizations, 
some of which will graduate to significant UI overhauls to suit some 
need the standard Bugzilla look doesn't target.  It should be possible 
for local customizations to graduate to UI overhaul (i.e. skin), and it 
should be possible for skins to get redistributed and installed on other 
installations that want the same thing.

>(I honestly don't see what skins would give us that wouldn't need to be
>complemented by custom fields and template changes
>
One longstanding request for b.m.o has been to implement different 
show_bug.cgi views for different audiences (programmers, QA, and project 
managers).  Each view hides a different set of fields that don't 
interest its audience.  It's costly (code implementation and ongoing 
support) to do this in Perl and templates.  It's trivial (once Bugzilla 
is cssified and browsers persist alternate stylesheet selection) to do 
this with CSS without any custom fields or template changes.

>unless it's fixing
>our user interface without going through the Bugzilla patch approval
>process!)
>  
>
Which is a good thing if the fixers wouldn't go through our approval 
process anyway, which has been the case for most site customizations to 
date, and we can get access to their fixes, which we can just by 
browsing their site if they make their changes in CSS rather than templates.

-myk