1 |
On Thu, 2007-04-26 at 15:16 -0700, Robin H. Johnson wrote: |
2 |
> On Thu, Apr 26, 2007 at 05:46:24PM -0400, Daniel Drake wrote: |
3 |
> > Robin H. Johnson wrote: |
4 |
> > > Case 2 - Metadata contains a single maintainer |
5 |
> > > ---------------------------------------------- |
6 |
> > > - The herd field is not used. |
7 |
> > > - The maintainer address is used as the bugzilla assignee. |
8 |
> > At least for some packages I'm involved with, this will result in me |
9 |
> > deleting myself from metadata.xml (but I'd rather not do so). |
10 |
> > |
11 |
> > I like these bugs to go to the herd, not me directly. I get the bug mail |
12 |
> > anyway (I'm in the herd) but sometimes other herd members who see the mail |
13 |
> > jump in and help resolve the bug, for which I'm very grateful. |
14 |
> This is handled by a later case in the proposal. |
15 |
> Simply interest a maintainer element with the herd email address, and |
16 |
> add the contact=0 attribute to your maintainer element in the file. |
17 |
> |
18 |
> > That aside, I like having myself in the metadata alongside the herd, to |
19 |
> > point out that I am the primary maintainer within the herd for the package |
20 |
> > in question. It is also useful for others so that when they have questions |
21 |
> > about the package, they know who to approach on IRC or whatever. |
22 |
> This is exactly the reason that I proposed the contact=0 attribute - for |
23 |
> some of the packages that I maintain, I do not want the bugs assigned |
24 |
> directly to me, but to the herd instead. While for others I _do_ want |
25 |
> the duplicate. |
26 |
|
27 |
Could "contact" be named differently then? |
28 |
|
29 |
contact=0 in metadata.xml in this context means that the automatic |
30 |
reassigning should not assign to that maintainer, but when a user looks |
31 |
whom to ask specific questions from and sees contact=0 he/she will |
32 |
understand he/she is not to contact that person as the value is zero, |
33 |
but Daniel wants them to contact precisely him in that case. |
34 |
A different keyword might be better for that reason. |
35 |
|
36 |
Good proposal otherwise! |
37 |
I do have some reservations due to no human looking over new bugs |
38 |
(before they get reassigned to a possibly otherwise busy maintainer), as |
39 |
someone already has expressed, but we can always try it out and see how |
40 |
it goes, I think. |
41 |
|
42 |
Regards, |
43 |
Mart Raudsepp |
44 |
|
45 |
-- |
46 |
gentoo-dev@g.o mailing list |