Gentoo Logo
Gentoo Spaceship

Installation:
Gentoo Handbook
Installation Docs

Documentation:
Home
Listing
About Gentoo
Philosophy
Social Contract

Resources:
Bug Tracker
Developer List
Discussion Forums
Gentoo BitTorrents
Gentoo Linux Enhancement Proposals
IRC Channels
Mailing Lists
Mirrors
Name and Logo Guidelines
Online Package Database
Security Announcements
Staffing Needs
Supporting Vendors
View our CVS

Graphics:
Logos and themes
Icons
ScreenShots

Miscellaneous Resources:
Gentoo Linux Store
Gentoo-hosted projects
IBM dW/Intel article archive




List Archive: gentoo-dev
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-dev@g.o
From: Jeroen Roovers <jer@g.o>
Subject: Prioritising contact information in metadata.xml
Date: Thu, 24 Apr 2008 22:05:35 +0200

 1.1

     Hi developers and other users,


since jakub[1] went completely missing a few weeks ago a few others and
I have been wrangling the bugs. I've heard rumours that this isn't
working smoothly yet. Of course most of that can be fully blamed on
bugzilla itself, but there are some things that need to be pointed out
or discussed.

One thing I'd like to point out is that if you don't agree with a
specific mangle, just CC whoever did it on the bug and explain.
If you don't give me the feedback, I can never know how you would
rather have wanted to get bugs delivered.

One other thing is that it is sometimes difficult to figure out to
whom a bug should be assigned, because metadata.xml for many packages
simply isn't clear. If you list a few developers as well as a herd,
does that mean you want bugs assigned to the herd or to a single
developer who happens to be in that list? Some packages list several
herds in metadata.xml. Bugs can be assigned to just one address
(or you get "Assignee: jer@g.o,bug-wranglers@g.o did not
match anything").

[2] has nothing explicit to say on this subject, sadly. It seems some
editors of metadata.xml use the file as a sort of CREDITS or AUTHORS.
While that may seem OK, the file is intended to give information about
ebuilds. ChangeLog is intended to credit authors (specifically
mentioning ebuild authors and contributors[3]).

So maybe this needs to be layed out more specifically in the Developer
Handbook, or maybe this needs to be discussed more. I can tell that
from my end, and possibly from the viewpoint of any user who is seeking
support contacts, listing more than one contact in metadata.xml is
rather pointless, unless descriptions are added so that it's clear
which component of a package is supported by whom.

All in all I guess we need to make the rules up as we go and decide
policy later. I suggest the first herd/address in the list should be
the primary contact. If you don't agree with that, please consult
metadata.xml for the package or reassign to bug-wranglers with an
explanation (and perhaps a promise to quickly change metadata.xml. :)


Kind regards,
     JeR


[1] Where is the old bugger? Anyone know? On a strictly human level, I
am getting quite worried.
[2]
http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=2&chap=4
[3]
http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=3&chap=1#doc_chap3_sect6
-- 
gentoo-dev@g.o mailing list


Replies:
Re: Prioritising contact information in metadata.xml
-- Tiziano Müller
Re: Prioritising contact information in metadata.xml
-- Robin H. Johnson
Re: Prioritising contact information in metadata.xml
-- Luis Francisco Araujo
Re: Prioritising contact information in metadata.xml
-- Mike Frysinger
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Last Rights: x11-themes/openbox-themes
Next by thread:
Re: Prioritising contact information in metadata.xml
Previous by date:
Re: lastrite: net-fs/coda-kernel (treecleaners)
Next by date:
Re: Prioritising contact information in metadata.xml


May 29, 2008

Donate to support our development efforts.

Gentoo Centric Hosting: vr.org

VR Hosted

Tek Alchemy

Tek Alchemy

SevenL.net

SevenL.net

php|architect

php|architect

Copyright 2001-2007 Gentoo Foundation, Inc. Questions, Comments? Email www@gentoo.org.