1 |
On Fri, 2009-05-15 at 06:25 -0400, Richard Freeman wrote: |
2 |
> > if you want to exaggerate a bit, we have roughly 500 ebuilds in |
3 |
> portage |
4 |
> > which are maintainer-needed and have only a few users and thats why |
5 |
> you |
6 |
> > want to keep popular packages out of the tree? |
7 |
> > |
8 |
> |
9 |
> Actually, where any of those ebuilds cause problems I'm fine with |
10 |
> getting rid of them. I'm certainly not arguing for inconsistency. |
11 |
> I'm |
12 |
> just suggesting that we shouldn't make the problem worse. |
13 |
|
14 |
I'm not suggesting to make the problem worse either. On the contrary. |
15 |
maintainer-needed packages that clearly are used to close by no-one or |
16 |
no-one (based on no-one reporting build bugs or version bump requests or |
17 |
whatever) should probably indeed be last-rited and removed from the |
18 |
tree, especially if there is no active upstream. |
19 |
This seems to be what the treecleaners project is about, and |
20 |
maintainer-wanted is not meant to have anything to do with that. It is |
21 |
about getting popular packages (based on various metrics) into the |
22 |
official tree for easy access and with known quality. |
23 |
|
24 |
> |
25 |
> If a package is popular then somebody should volunteer to maintain it |
26 |
> (whether by becoming a gentoo dev or by starting their own overlay). |
27 |
> If |
28 |
> that isn't happening than clearly the package isn't THAT important. |
29 |
> This is open source - if you have an itch, then scratch it! Don't |
30 |
> just |
31 |
> complain that nobody else is scratching YOUR itch (even if it is a |
32 |
> popular itch). |
33 |
|
34 |
I don't think we have all topics covered by active teams. When |
35 |
maintainer-wanted team packages something in-tree that would be suitable |
36 |
for a certain existing team, the categorization in the proposed listing |
37 |
of maintainer-wanted packages would imply that, so that once they are |
38 |
able to handle more they can take over if it is well suited for their |
39 |
set of packages. |
40 |
Until such a time this kind of packages would be available in great, |
41 |
good or acceptable quality to the users. |
42 |
> |
43 |
> In any case, my opinion is that for packages to be in portage they |
44 |
> should be of a certain level of quality, and a developer should be |
45 |
> accountable for the packages they commit. Anybody is welcome to grab |
46 |
> ebuilds out of CVS, screen them, and commit them. However, if they |
47 |
> cause havoc then the developer can't just say "but it was popular and |
48 |
> unmaintained, so I figured I'd just commit something without looking |
49 |
> at |
50 |
> it." If a developer is willing to commit an appropriate amount of |
51 |
> time |
52 |
> to QA then they essentially have become a maintainer and the package |
53 |
> is |
54 |
> no-longer maintainer-wanted. |
55 |
|
56 |
The maintainer-wanted team would effectively aggregate those people |
57 |
together, so that the end result would be better quality, quicker |
58 |
response times and so on. |
59 |
|
60 |
|
61 |
-- |
62 |
Mart Raudsepp |
63 |
Gentoo Developer |
64 |
Mail: leio@g.o |
65 |
Weblog: http://planet.gentoo.org/developers/leio |