1 |
Hi, |
2 |
|
3 |
December 20, 2017 5:46 PM, "Michał Górny" <mgorny@g.o> wrote: |
4 |
|
5 |
> E. Some of the unmaintained packages are dependencies of other |
6 |
> maintained packages in Gentoo. However, developers usually don't want |
7 |
> to take them, even if their package is the only revdep. |
8 |
> |
9 |
> F. We are usually treecleaning packages as they become severely outdated |
10 |
> and broken. However, that takes serious amount of work too and usually |
11 |
> results in a lot of hostility from other developers (who don't want to |
12 |
> maintain the package in question) and users. |
13 |
> |
14 |
> G. In the past, I've attempted to evaluate the status of projects and to |
15 |
> clean some dead up. However, it's a lot of manual labor and it meets |
16 |
> with hostility from some of the Gentoo developers. |
17 |
> |
18 |
> H. For most things related to determining developer inactivity, we have |
19 |
> little to no automation. It's easy to tell when a developer stops |
20 |
> committing altogether but we have no special help in e.g. determining |
21 |
> that some packages are effectively unmaintained (and that would of |
22 |
> course meet with hostility). |
23 |
|
24 |
I believe there was some work in progress about automating check for new upstream version (via |
25 |
repology api I think). |
26 |
Couldn't this be used to check for maintainer abandon? Some bugs can't always be solved easily, so |
27 |
you can't take that into account to check for inactivity, but not adding new versions is, IMO, a |
28 |
sign that the maintainer doesn’t check often enough for updates. |
29 |
We could also send automatic mail a month (arbitrary choice) after a new version has been released |
30 |
upstream to the maintainer for the related ebuild with such a system, so that maintainers don't |
31 |
have to bother about that part anymore. |
32 |
|
33 |
I can't remember what was called the project but what's its current status? |
34 |
I don't know if a solution like that would change much to the situation, but I believe it should |
35 |
give us better insights about the state of the tree. |
36 |
|
37 |
Best regards, |
38 |
-- |
39 |
Corentin “Nado” Pazdera |