1 |
On 19-10-21 19:37:28, Piotr Karbowski wrote: |
2 |
> Hi, |
3 |
> |
4 |
> I'd like to bring the topic of defining default policy to do changes to |
5 |
> packages within ::gentoo that one does not maintain. |
6 |
> |
7 |
> This topic goes back from time to time on #gentoo-dev, and as I was |
8 |
> told, it was originally sent to gentoo-dev mailing list by robbat2 (I |
9 |
> failed to find this in archive, so if anyone have copy of it, please share). |
10 |
> |
11 |
> Current policy is to never touch ebuild that one did not claim as |
12 |
> maintainer unless maintainer of said package allowed you to do so. |
13 |
> |
14 |
> This is a bit unhealthy, especially when some developers that maintain |
15 |
> packages are out of reach, or the patches to update ebuild just rot on |
16 |
> the bugzilla and are not taken in by maintainers. |
17 |
> |
18 |
> What I'd like to end with would be to set a policy that allows any |
19 |
> developer with write access to ebuilds tree do changes that are small in |
20 |
> scope, like a minor bug fixes, adding missing flags, version bumps, |
21 |
> anything, that does not require complete overhaul of ebuild, with the |
22 |
> option to set in metadata.xml that policy for specified package is to |
23 |
> deny anyone but maintainers from doing changes. |
24 |
> |
25 |
> The packages that would require a flag to prohibit non-maintainers from |
26 |
> doing changes would of course be those of toolchain, or other big in |
27 |
> user base packages that are in very good shape, as in gnome packages, |
28 |
> kde packages, X11 packages and so on. |
29 |
> |
30 |
> Of course, the policy would also define, that if there are any bug |
31 |
> introduced by changes that non-maintainer made, it's responsibility of |
32 |
> those who did the change in first place to fix it and clean any mess |
33 |
> that it has created. |
34 |
> |
35 |
> I personally am fine with others doing changes to packages I own, as |
36 |
> long as they won't break anything and I do know from the discussion on |
37 |
> #gentoo-dev, that there are others who have similar opinion about it. |
38 |
> |
39 |
> Those who feel territorial and those who believe only maintainers should |
40 |
> maintain specified packages can just set the flag in metadata.xml and |
41 |
> continue with the current state of things for their packages. |
42 |
> |
43 |
> The reason why I would like to get default policy to allow-all is that I |
44 |
> do not believe most of developers would want to go around all the |
45 |
> packages they own and set it manually to allow others doing changes even |
46 |
> if they're fine with others touching those packages. |
47 |
> |
48 |
> What do you think folks? |
49 |
> |
50 |
> -- Piotr. |
51 |
> |
52 |
|
53 |
I like the idea of setting metadata.xml options so repoman can help |
54 |
enforce things. Not sure if we talked about it earlier but it was an |
55 |
option that popped up in the last couple of weeks in the -dev channel. |
56 |
|
57 |
-- |
58 |
Matthew Thode (prometheanfire) |