Markos Chandras wrote: > > A per-ebuild bug metric would be cool. A kind of health indicator > > for individual ebuilds, alerting users when some of our installed > > ebuilds go yellow, so that we have perhaps on the order of six > > months before the package goes red, at which point it would be > > fine to mask at will. Does that make sense? (Obviously how many > > months yellow is depends on what else happens in the tree. It's a > > ballpark figure.) > > No we don't have the human resources to do that.
Ah, no, it must be automated. Of course the metric would be accordingly "stupid" but it would still be way more informative than no metric at all. I think a GSOC project is a good fit, unless of course a developer likes to run with the idea. In any case, yes, people are needed to do development, but working out an idea is a good start. //Peter
