1 |
On Sun, Sep 03, 2006 at 01:57:10PM +0200, Stefan Schweizer wrote: |
2 |
> Kevin F. Quinn wrote: |
3 |
> > I don't think it's a good idea for devs to be putting stuff into the |
4 |
> > tree without taking responsibility for it. |
5 |
> sure I can put myself in there but it will help no one because I cannot test |
6 |
> the thing. Furthermore I am actually part of maintainer-needed and commit |
7 |
> fixes there. I am also on the maintainer-needed email alias. |
8 |
> |
9 |
> Also maintainer-needed makes obvious to everyone that they do not have to |
10 |
> ask me to fix sth. or take over the package -> less communication overhead. |
11 |
Ok, let me see if I can get this straight.. You're saying that |
12 |
maintainer-needed requires less communication overhead compared to |
13 |
ebuilds with maintainers assigned? And that maintainer-needed is |
14 |
therefore better than ebuilds having maintainers. |
15 |
|
16 |
I don't even want to comment on how insane I find that line of thought.. |
17 |
> |
18 |
> > I would expect that either |
19 |
> > the herd is set appropriately (which means either the committer be a |
20 |
> > member of the herd, or the herd explicitly agree to be proxy), |
21 |
> which is the case here. |
22 |
> |
23 |
Maintainer-needed being the waste basket for unmaintained packages in |
24 |
the portage tree that doesn't give me a lot of confidence tbh. |
25 |
> > or the |
26 |
> > committer be listed as a maintainer email address along with whoever is |
27 |
> > being proxied. |
28 |
> the committer in this case has no interest in maintaining the thing. And for |
29 |
> proxying it does not matter who is proxying. |
30 |
Of course it matters. There's a big difference between a proxy |
31 |
maintainer having to ask a *specific* dev that's proxying his ebuild |
32 |
updates/changes or trying to find a random dev willing to help. |
33 |
> |
34 |
> > Further I believe bugs against such packages should be |
35 |
> > assigned to the @gentoo.org address (proxy maintainer if there is one, |
36 |
> > herd otherwise), and CC'ed to the proxied maintainer address. |
37 |
> |
38 |
> this does not allow the actual maintainer to close the bug and causes a lot |
39 |
> of bugspam for a person who does not care about it and should be only |
40 |
> contacted in the end to commit fixes/patches/bumps. |
41 |
Shouldn't matter too much as a gentoo dev is still responsible for the |
42 |
package? Nobody shoud be adding stuff to portage without taking |
43 |
responsibility for it. |
44 |
|
45 |
Regards, |
46 |
Bryan Østergaard |
47 |
-- |
48 |
gentoo-dev@g.o mailing list |