Would be cool! Listen to Wikipedia with Quality and things.
Description
Related Objects
- Mentioned Here
- T143743: Set up the foundation for the ReviewStream feed
Event Timeline
This would be a better alternative than bots hitting ORES API for recent scores. We ought to discourage that. Something like RSS feed and/or JSON that shows scores for the latest revisions would do the trick. This would also reduce multiple requests of same revids as I am aware that is a problem for parallel/distributed computing.
Also this would be easier for bot operators to implement RC bots if they forgo reading the RC feed and would get what they care about, the actual scores.
@Krinkle, is this something you think that we should be looking at right now, or should we wait to see what the Collaboration-Team-Triage wants to do re. ERI?
I think this should be merged into T143743: Set up the foundation for the ReviewStream feed, which includes the ORES scores.
A good first task is a self-contained, non-controversial task with a clear approach. It should be well-described with pointers to help a completely new contributor. Given the current short task description I'm removing the good first task tag. Please add details what exactly has to happen where and how for a new contributor, and then add back the good first task project tag. Thanks a lot in advance!