> Most developers think of MX (My Experience), not UX. Yes, yes and yes. I don't know how long you've been around, but in the (earlier) days of open source, th

> Most developers think of MX (My Experience), not UX. Yes, yes and yes. I don't know how long you've been around, but in the (earlier) days of open source, this was very explicit: Open source authors are writing to solve their problem, not their users' problems. If they go out of their way to solve other people's problems, that's certainly nice, but not to be expected. This was very explicit, and well understood. We're not arguing with you that having a well curated list is a bad idea from a user's perspective. We're pointing out that doing it well is work, and doing it poorly does make things worse. We don't want people burnt out, so we don't want to push for this. > Or, you could write a database query that finds the top 5 reads in 5 genres that runs once a week for the homepage. This is the opposite of a well curated list. In my experience, such lists based on raw numbers leads to a poorer experience. There's a reason HN doesn't follow this approach. > Except in LibriVox's case, it's a repo that everyone else spent hours of their life contributing to. Just make the dang README. Promote a few volunteer contributions. Talk is cheap. Do you want to spend the time making a curated list? If so, go forth and volunteer!