[FusionDev] Bugzilla

[Kristian Lyngstøl]

I want us to be able to use bugzilla to a larger extent than we ever
used trac with the Beryl project and Bugzilla for compiz core, but we
need a few things sorted out.

First, I suggest we strongly advice users to buddy their issues. That
is, they should seek help on IRC, the forums or a mailinglist to find
confirmation about their issue and possibly narrow it down BEFORE they
create a ticket. Many tickets are created with very little information
about reproduction and whether this is an issue that can be confirmed.
It became a never-ending problem in the beryl tracker that issues were
impossible to reproduce, we should try to prevent that.

And, (this is starting to sound old), we need individual components
for each plugin and we need to assign proper developers to all of
them.

This is a list of plugins taken straight from gitweb, any plugin owned
by 'compiz' should be assigned a developer to take care of it's
tickets.

LIST START

animation  -- NAM (Needs a maintainer)
winrules  -- NAM
expo -- NAM
firepaint  -- Dennis+Kasprzyk
compiz-scheme -- Robert+Carr
wall -- NAM
resizeinfo -- Robert+Carr
screencasting --  Nicholas+Thomas
group -- NAM
addhelper -- Kristian Lyngstol
bench -- NAM
crashhandler -- NAM
extrawm -- NAM
fadedesktop -- NAM
fakeargb -- NAM
jpeg -- NAM
mblur -- NAM
neg -- NAM
opacify -- Kristian Lyngstøl
put -- NAM
reflex -- NAM
ring -- NAM
showdesktop -- NAM
snap -- NAM
snow -- NAM
splash -- NAM
text -- NAM
thumbnail -- NAM
tile -- NAM
trailfocus -- Kristian Lyngstøl
3d -- NAM
cubecaps --  Guillaume+Seguin
goto-viewport --  Robert+Carr
wallpaper -- NAM
scaleaddon -- NAM
cubereflex -- NAM
vpswitch -- NAM
mswitch -- NAM
gears -- NAM
atlantis -- NAM
scalefilter -- Danny+Baumann
shift -- NAM
ezoom -- Kristian+Lyngstol
workarounds --  Andrew+Riedi
colorfilter -- Guillaume+Seguin

LIST END

This list is available on obby at the usual place, but I'd like to
keep any discussion on the ML, and I'll also update the obby document
if people would rather use the ml (and I suggest people notify the
list after grabbing plugins too).

There are many of these plugins which have fairly obvious maintainers
but I don't want to assign anyone in case I miss some other obvious
choice. Also, like I mentioned, these are just the owners of the git
repos (with the exception of my own plugins).

If we have to, I say we assign the dev list to the plugins with no
clear owner. And I don't really want a separate list for that, as
it'll just end up being ignored. And the list of plugins with no
specific maintainer should be short and consist of relatively stable
plugins too.

-- 
Regards,
Kristian