Gentoo Archives: gentoo-dev

From: Markos Chandras <hwoarang@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] introduce a soft-limit policy for changing other developers ebuilds
Date: Tue, 04 Dec 2012 09:23:46
Message-Id: CAG2jQ8ixNidz8jH4G3L-ZVQ+xXGvLCYDtuc98xf9yTJRUQ+Fyw@mail.gmail.com
In Reply to: Re: [gentoo-dev] introduce a soft-limit policy for changing other developers ebuilds by "Rick \\\"Zero_Chaos\\\" Farina"
1 On 4 December 2012 08:10, Rick "Zero_Chaos" Farina <zerochaos@g.o> wrote:
2 > -----BEGIN PGP SIGNED MESSAGE-----
3 > Hash: SHA1
4 >
5 > On 12/02/2012 10:21 AM, hasufell wrote:
6 >> As I was told in my recruiting process we usually don't just fix up
7 >> ebuilds of other devs unless it's trivial, very severe or something.
8 >>
9 >> The usual process is nothing new: try to contact the maintainer, open a
10 >> bug, set a deadline when you will go and fix yourself.
11 >>
12 >> Only question is now what is a sane soft limit, before you go on and fix
13 >> stuff.
14 >>>From a discussion in #gentoo-dev we thought 2-4 weeks depending on the
15 >> severity of the bug is fine. Ofc this should exclude major changes or
16 >> delicate packages from base-system/core/toolchain.
17 >>
18 >> I tried to document that a bit:
19 >> https://bugs.gentoo.org/show_bug.cgi?id=445402
20 >>
21 >> any objections? This is nothing new, just a clarification of already
22 >> existing policy and a reminder.
23 >>
24 >>
25 > If we are going to document this policy and make it official (which
26 > since it's not documented it's not official) then it only makes sense to
27 > have an opt-out option. I personally don't wish to see my users suffer
28 > for 2-4 weeks because I'm busy and people are pretending to be polite.
29 >
30 > I have no issue with this policy, but to do it without an explicit
31 > option to opt-out is not acceptable to me. I would suggest something in
32 > the metadata.xml under the maintainer section. We could have a specific
33 > maintainer section : <maintainer><name>help welcome></name></maintainer>
34 > or a specific tag to put under our own maintainer section
35 > <maintainer><name>Rick Farina</name><demeanor>just fix it</demeanor></name>
36
37 Nobody said the opposite. The devaway message should always be checked
38 for people who appear to be inactive and if they
39 say "Do not touch my packages" then you shouldn't touch them even if
40 he doesn't even touch them himself. Let the retirement team
41 kick him out.
42
43 There is always the <description> tag on metadata.xml you can use eg
44
45 <maintainer>
46 <email>foo@g.o</email>
47 <name>Me</name>
48 <description>Primary maintainer but feel free to fix the bugs<description>
49 </maintainer>
50
51 --
52 Regards,
53 Markos Chandras / Gentoo Linux Developer / Key ID: B4AFF2C2

Replies

Subject Author
Re: [gentoo-dev] introduce a soft-limit policy for changing other developers ebuilds "Rick \\\"Zero_Chaos\\\" Farina" <zerochaos@g.o>