Hey Shawn,
First off, thank you so much for taking the time for the detailed feedback. All of your ideas are really detailed and well-thought-out, and I would love to see how we can integrate them into awesome-dot while being fair to all teams.
I completely agree on the challenges we’re facing in the awesome-dot repo. The exhaustive nature gets overwhelming for new users who are trying to dip their toes. Maintaining a list to keep everything high quality is an ongoing effort, though.
As I said, these ideas are really great, and I’d like to address them one by one:
- Project Liveness Bot
Regularly verifying if a project’s repository has been updated recently can be done with a bot that fetches all the data for any GitHub repo in the list. @kianenigma raised an issue here around checking all links and making sure none of them are dead, so this becomes a logical extension of this idea.
- Project Association Bot
I’ve been reading up on all the discussions that are happening around this topic on the Polkadot forum here and on GitHub here, but I am still waiting for some concrete instructions to come out of them before we can start thinking about it.
- Metrics Bot
This probably builds upon the Project Liveness Bot by extracting more info when GitHub info is collected, like stars or npm downloads, etc., but it might get tricky when we look at other sources like app stores or web analytics.
- Decentralized Personalized Lists
This is where it becomes non-trivial. I’ve been thinking about this, but I don’t have anything that can solve this intuitively. One of the solutions I’ve been considering is to build a frontend (web/app) that connects your wallet and uses awesome-dot data underneath, letting you store, bookmark, or rate resources. A lot of thinking needs to be done here.
I am definitely eager to start implementing some of these ideas in the repo, starting with the Project Liveness Bot and then diving into exploring metrics integration. In the meantime, if the ecosystem aligns on some common theme of the text for projects to include on their websites, we can dive into implementing the association.
If you’re interested, I’d love to collaborate further to refine these ideas and implement them effectively. Again, thank you for your thoughtful feedback and for initiating this important discussion. I hope we can enhance the awesome-dot repository to better serve both newcomers and existing members of the Polkadot community.