1 |
On Sun, Jan 05, 2020 at 03:55:22PM +0100, Piotr Karbowski wrote: |
2 |
> Hi, |
3 |
> |
4 |
> On 30/12/2019 00.30, William Hubbs wrote: |
5 |
> > All, |
6 |
> > |
7 |
> > the Gentoo Council will meet on 2020-01-12 at 19:00 utc in the |
8 |
> > #gentoo-council channel on freenode. |
9 |
> > |
10 |
> > Please reply to this message with any items you would like us to add |
11 |
> > to the agenda. |
12 |
> |
13 |
> I'd like to request Council to define rules regarding maintainership |
14 |
> boundaries and provide guidance regarding under what conditions one is |
15 |
> allowed to make changes to packages that are by metadata.xml maintained |
16 |
> by another party. |
17 |
> |
18 |
> The current situation is land of undefined rules and double standards |
19 |
> under disguise of 'common sense'. Although it does work for most part, |
20 |
> it's not uncommon to come across people that are overly territorial, |
21 |
> treating Gentoo packages as their own personal property, who openly |
22 |
> prohibit others from joining them as maintainers on packages, with the |
23 |
> solo reasoning that they feel territorial and do not want others |
24 |
> touching it. |
25 |
> |
26 |
> This leads to a situations, where some bugs reported on bugzilla are not |
27 |
> fixed in timely fashion, even when there are other developers that are |
28 |
> willing to fix those bugs and deal with whatever aftermath of doing |
29 |
> those changes would bring. |
30 |
> |
31 |
> Because those rules are unsanctioned, we have land of middle |
32 |
> inconvenience where one can never be sure if by declaring maintainer |
33 |
> fimeout and fixing a bug would not bring ComRel on him, for touching the |
34 |
> package one does not maintain. By defining rules and guidelines, it |
35 |
> would greatly benefit Gentoo as a whole as well as reduce the |
36 |
> frustration that come from dealing with people who are gate keeping |
37 |
> while being unable to provide a valid reason why they do not want anyone |
38 |
> toucing their property. |
39 |
|
40 |
The maintainership policy is here. |
41 |
|
42 |
https://devmanual.gentoo.org/general-concepts/package-maintainers/index.html |
43 |
|
44 |
By default you aren't supposed to touch packages you don't maintain |
45 |
without the maintainer approving your changes unless the changes are |
46 |
trivial. |
47 |
|
48 |
If you open a bug or contact a maintainer and they don't respond to your |
49 |
request in 2-4 weeks, you can use maintainer-timeout to make the change. |
50 |
|
51 |
I think this is fine at the distro level. |
52 |
|
53 |
The uncertainty around this is that some maintainers give devs |
54 |
permission to change any or some of their packages without contacting |
55 |
them as long as they clean up any breakages they cause, and we don't |
56 |
have a way of knowing who those maintainers are. There was a proposal a |
57 |
while back for a tag that would go in metadata.xml for a package that |
58 |
would specify one of three levels of non-maintainer permission for a |
59 |
package, but it seems to have died. I do think we should bring it back. |
60 |
|
61 |
William |