1 |
I am sorry, but I don't even understand what a co-maintainer is. |
2 |
|
3 |
In my understanding there are only package maintainers. Everyone listed |
4 |
in metadata.xml is a maintainer and has the competence to do any kind of |
5 |
changes. |
6 |
|
7 |
If one of the other maintainers disagree, then it's not a question of |
8 |
who is the master-maintainer and who is the co-maintainer. |
9 |
|
10 |
That's an internal problem of those people and they should deal with it. |
11 |
If they are unable to do that, then they can contact devrel. Period. |
12 |
|
13 |
If a developer refuses to add enhancements to an ebuild without giving |
14 |
technical reasons, then it's a matter for devrel as well. |
15 |
|
16 |
Honestly... In case of systemd I'd just open a bug, attach the fixes and |
17 |
wait for some time. In case of no response I'd just apply it. If the dev |
18 |
reverts it without giving a reason, I will contact him and if necessary |
19 |
devrel. |
20 |
|
21 |
I don't see a reason to introduce a special policy for this. We could go |
22 |
on about such things all day, because there are and will be more. |
23 |
|
24 |
And I am not really sorry about devs dropping maintainership because of |
25 |
such silly issues. If they can't work out something like that, then it's |
26 |
better that way. |
27 |
|
28 |
|
29 |
reasoning > authority |