On 04/03/10 18:03, Alec Warner wrote:
> - date of last commit: Gentoo is fast moving and packages that
> haven't had commits since 200{4,5,6} are probably old, unmaintained
> and may not even compile or run.
> - date of last listed maintainer commit versus last commit:
> Basically if the maintainer hasn't touched the ebuild in a while but
> someone else (herd members?) have, the metadata.xml is probably out of
> date.
Have the result of that analysis collected somewhere?
> The above are all pretty easy to do with the data in the tree. Some
> other useful ideas might be:
> - compare open bugs for the package, when was the last bug for a
> package closed (bugs data kinda sucks for this)
Right, but we can get that working. I have a regex to get package
names from bug titles around that works well. All we need to do is fix
all bug titles ever to contain package names: Could take a whole bugday
or two :-)
> - for a given package in a herd, check the version in the tree
> against freshmeat or similar to see how far behind it is (I think
> someone wrote something for this already, exherbo?)
That's a larger project. GSOC ideas should contain such thing.
> - check imlate to see if keywording is behind (is the maintainer
> filing stablereqs?)
While you mention that: it's the first time I hear a maintainer should
do that. if so can you raise awareness of it and explain the what and
why in another thread on gentoo-dev?
Sebastian
