On Fri, August 12, 2005 10:49 pm, Chris Pressey said: > If lots of users use Foo, then lots of patches to get Foo working will > come in, and Foo will be well-maintained. If no users use Bar, then no > patches for Bar will come in, and Bar will rot. Problem solved - the > packages that are well-maintained are exactly the ones that are in > demand. What need is there for a list? How is it not just another, > unnecessary level of organization on top of something that already > organizes itself automatically?
We can, given our currently smaller user base, end up in a scenario where we have a number of users for a given package Foo, but nobody with the time or skill to fix. I think Hiten's looking to distribute our relatively limited resources where they would do the most good. A voting system will skew away from reality, I daresay, and requires more work. However, if we could track, say, package download quantity (from fireflybsd.com, if that's where pkgsrc binary builds end up), that would give us a good estimate, without having to put much effort into it.
