[maemo-developers] [maemo-developers] Bugzilla modules and components hierarchy not very easy

From: José Dapena Paz jdapena at igalia.com
Date: Fri Nov 17 01:12:31 EET 2006
	Hi,

	Mmm well, the subject is very descriptive. I feel a bit lost in maemo
bugzilla (http://bugs.maemo.org). I've been issuing some bugs last days,
but it's not easy to decide the module they should go.

	First point is all that "haf" thing. It's where hildon-libs, python and
osso live, but, not very intuitive. Many important modules are there in
bugzilla (hildon-libs, sapwood, osso-application-installer, ...).

	But the most annoying thing is not finding the proper module for a bug.
I suppose bugzilla should encourage people to submit the issues they
find. And a good way to encourage people is making it very easy to send
good reports to the proper box:
	* Errors in custom gtk+. Should they go to the upstream gtk+ bugzilla?
	* Should bugs found in maemo-af-desktop svn module should go to
bugzilla "haf/desktop" component? Shouln't it be better that maemo af
desktop would be a product, with components like "status bar",
"navigator", "home", etc.?
	* If we assume an "applications" product, shouldn't application
installer, control panel, etc, go there? Or, most likely, shouldn't they
be products themselves?

	I think Gnome bugzilla is at least easier to browse (names of modules
in cvs are equal to names of modules in bugzilla, products are more or
less equivalent to projects, etc).

	These are some problems (of course, dramaticed ;) I found working with
maemo bugzilla. I think that, now that there aren't too much bugs
registered, it's a good time to recategorize bugs, and fix this, as it
seems a bit messy now.

-- 
José Dapena Paz <jdapena at igalia.com>
Igalia

More information about the maemo-developers mailing list