I started to work on something like this a week or two ago (after seeing a post of yours). I started from scratch and in Rust with the following goals:
- Nice minimal design
- Once deployed, minimal maintenance
- Users should be able to add repositories to the watchlist easily
- Use a special label name (like
rust-starters) that can be used across the community
- Limit spam repos by checking for issues with the label before adding to the watchlist
- Possible support for alternative git hosting services (e.g. GitLab)
So what I had in mind is creating a webapp with iron and have a db managed with diesel. The db would have 2 tables, one containing repos to watch and the other would contain the issues associated with a repo from the first table.
On the front-end we would allow various ways of sorting and browsing the issues as well as add new repositories to the watchlist. This would be as easy as entering the hosting platform (e.g. Github) followed by the repository namespace. To avoid spam, the repo would only be added to the watchlist if there is actually and issue tagged with the pre-defined label.
I think the advantage of having a db instead of static site is that new repositories can be added by the community without needing the intervention of a maintainer through a PR or something, reducing the maintenance cost.
As for the actual implementation, I have not yet pushed anything online because I have run into some trouble with serde and diesel not agreeing on the nightly version to use (see this issue).