UI module owner

[timeless]

On 6/26/06, Gervase Markham <gerv at mozilla.org> wrote:
> So Bugzilla needs to ship with versions of the search page to meet every
> possible need from every company which uses it?

Bugzilla should ship such that most companies don't feel the need to
implement dozens of horrible hacks that cause them to refuse to
upgrade to a newer version of Bugzilla later.

> Let's turn the question on its head: is one of the goals of the Bugzilla
> project to get as many companies and organisations using it as possible?

Bugzilla should be the standard tracking system that companies and
organizations use, so that when I have a problem with any product
anywhere, I can turn to a comfortable fairly standard Bugzilla
installation which I can easily log into, select my standard per user
custom settings and feel right at home explaining my problem or
finding out the status of a preexisting report that I was able to find
about my problem.

Bugzilla should enable any company to easily send a problem report to
the next company or organization's Bugzilla without resorting to
hacks. Note that in almost all cases this communication is
bidirectional, it's not just a "move", it's some sort of "keep these
bugs in sync" or "share comments across bugs" or "establish a
dependency between these bugs". It's fairly rare for anything to be a
simple "move" (the hack implemented for bugscape), most customers or
consumers appreciate at least being told "this is fixed in the next
version" and "the next version shipped with this fixed, you can
actually download it now", which are things you don't get if you just
"move" a bug.

> Clearly, it's not good to have only a few places using it - but we are
> well past that stage.

It's not good for every single consumer of this product to fork it
just to make it work for them.

It's not good for every single organization that does this to end up
w/ dozens or hundreds of complaints which are lost in some internal
problem report area. Every single organization I visit is either using
or has tried to setup or use (sometimes both depending on the size of
the organization) Bugzilla, and they all have valuable feedback about
what's wrong or unusable about it. But we lose most of that feedback
because it's internal.

> Re-skinning an application (in the usual sense of the word "skin" - i.e.
> changing colours and logos) has no effect on TCO.

The skinning we're interested in is more akin to guided, it's not the
same as modern v. classic, it's the difference between advanced and
simplified.

> > We just need a samples bundled in distro.
> They are.

We have samples half bundled, we still have people asking how to
integrate things very much like the guided entry form, which if they
were fully integrated shouldn't happen.