I don’t think that your idea is controversial, but the devil is in the details with something like this. For instance, imagine if you spent time writing an application and then @mark just went in and deleted the code from the repo, or took it down without notice.
Here is some of the work that I would think needs to be done to accomplish your objective (ostensibly “improve the quality of the app store”):
- There needs to be a feedback loop in which users can review/report bugs on apps.
- Apps with low ratings/scores can be flagged for review by the Tidbyt team; or using GitHub Actions, an action could trigger to create an issue, assigned to that application’s developer to review app feedback, and/or fix relevant bugs.
- If no action is taken within X {insert logical but arbitrary limit here} time period from the developer, the app can be delisted from the app store. If no action is taken within Y subsequent time period, the code is removed from the tidbyt community codebase.
That’s how a formalized process may be successful. In lieu of that (not insubstantial) work being done, the community could (should) create GitHub issues and assign them to the related developers . And Matt and others could review whether or not there has been sufficient action/notification for the developer.