1 |
On Fri, Jun 14, 2013 at 10:51 AM, Chí-Thanh Christopher Nguyễn |
2 |
<chithanh@g.o> wrote: |
3 |
> I was always under the general impression that a maintainer is free to |
4 |
> do whatever he likes with his package within policy. When p.mask'ed even |
5 |
> outside policy to some degree. If you disagree with how a package is |
6 |
> maintained, you are welcome to fork the ebuild and do it better. |
7 |
|
8 |
Sure, but there is more than one maintainer - the original one, and |
9 |
the one who signed up because the original one was being stubborn. |
10 |
They're both welcome to do whatever they want within policy. However, |
11 |
the users don't exactly benefit from daily revision wars. |
12 |
|
13 |
Maintainers don't have the right to exclude others from also being |
14 |
maintainers, and when they do become maintainers they have all the |
15 |
rights the original maintainer had. Nobody owns a package. |
16 |
|
17 |
Bottom line is that bad things happen when developers become stubborn |
18 |
and don't cooperate. However, the fact that maintainers aren't |
19 |
cooperating isn't a reason to delay progress. You can't give every |
20 |
developer a veto on every project in Gentoo or nothing will get done. |
21 |
If the standing policies aren't working for somebody they can always |
22 |
go to Council - that's what it is there for. The standing policies |
23 |
say that anybody can maintain anything, and when it gets bigger than |
24 |
that you have projects that elect leads. |
25 |
|
26 |
Rich |