Bug 3215

Summary:	OCAL: Add a category for openclipart.org bugs
Product:	freedesktop.org	Reporter:	Jon Phillips <jon>
Component:	Bugzilla	Assignee:	fd.o Admin Massive <sitewranglers>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	high	CC:	bryce
Version:	unspecified
Hardware:	x86 (IA32)
OS:	Linux (All)
URL:	http://openclipart.org
Whiteboard:
i915 platform:		i915 features:

Description Jon Phillips 2005-05-06 00:41:03 UTC

The openclipart.org would like to request a category for bugs, called
openclipart.org (just like there are other categories for various projects). Our
project is in dire need of a bug tracking system, as we previously setup mantis,
and think it is better to centralize with bugzilla rather than offer another
setup that we would have to maintain.

Thanks sitewranglers!

Comment 1 Carl Worth 2005-05-06 04:46:50 UTC

I've gone ahead and made a new bugzilla "product" named openclipart.org.

In addition the product must have one or more "components" which have descriptions
and initial owners, (email address of person responsible for the bug). I just
took a wild guess and created two components:

clipart - Bugs regarding the clip art content... - jon@rejon.org
website - Bugs regarding the openclipart.org website - jon@rejon.org

The right answer is to set things up so that you guys, the maintainers of
openclipart.org can maintain this list of components yourselves. If someone
can tell me what the policy and mechanism are for granting that access, then
I will be glad to do that.

Comment 2 Jon Phillips 2005-05-07 23:34:07 UTC

Can you set the emails for the products to:

clipart@lists.freedesktop.org

This way bugs will go to our mailing list. I have set the mailing list to allow
bugzilla-daemon@freedesktop.org to post to the list.

Also, can you add the products: dms and tools

Thanks!

Comment 3 Stuart Anderson 2005-05-08 21:36:47 UTC

default address changed, and two new groups added.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.