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: Luis Francisco Araujo <araujo@g.o>
Subject: Re: Prioritising contact information in metadata.xml
Date: Thu, 24 Apr 2008 18:07:07 -0400

 1.1

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jeroen Roovers wrote:
|      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").
|

I'd say that in the case of a herd listed , the bug should be sent
there. If it doesn't specify a herd but several developers, sending the
bug to any or all of them should be the rule.

| 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

I agree.


- --

Luis F. Araujo "araujo at gentoo.org"
Gentoo Linux

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)

iEYEARECAAYFAkgRBIoACgkQNir3WYj9aLp8UwCfeiHyHDQCDXd1nw0/oauctVVc
UWkAn0Y4b1Be65A0ThXqDQIbTXRGbKSv
=YVb7
-----END PGP SIGNATURE-----
-- 
gentoo-dev@g.o mailing list


Replies:
Re: Prioritising contact information in metadata.xml
-- Ulrich Mueller
References:
Prioritising contact information in metadata.xml
-- Jeroen Roovers
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: Prioritising contact information in metadata.xml
Next by thread:
Re: Prioritising contact information in metadata.xml
Previous by date:
Re: config_eth0 deprecated - new name?
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.