Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Post Dutch Referee quizzes #102

Closed
pmonks opened this issue Sep 9, 2020 · 2 comments
Closed

Post Dutch Referee quizzes #102

pmonks opened this issue Sep 9, 2020 · 2 comments
Labels
feature New feature, functionality or request functional Functional (i.e. user-visible) work should MoSCoW - this SHOULD be implemented

Comments

@pmonks
Copy link
Owner

pmonks commented Sep 9, 2020

Description of Problem:

When the Dutch Referee Blog posts a new quiz, I want a link to the quiz to be posted to the #training-and-resources channel, so that the community knows a new quiz has been posted and can participate in it.

Furthermore, I want the bot to add reactions to that link, representing the question #s that folks got wrong. That way anyone can see which question(s) caused widespread trouble, and we can have a prioritised discussion about them.

Potential Solutions:

The blog offers an RSS feed which is likely to be the most computer-readable source for this information. Note however that it includes all of the Dutch Referee Blog Posts, not just quizzes, so some filtering will need to be done (e.g. looking for the word "quiz" in each post's title).

To (continue to) avoid the need for the bot to store persistent state, the bot should check the feed once a day (since it gets restarted by Heroku every day), and look for a new quiz blog post in the feed in the last 24 hours. It should only perform this processing via a timed job at a specific time each day, to ensure it doesn't post a quiz more than once.

@pmonks pmonks added feature New feature, functionality or request functional Functional (i.e. user-visible) work should MoSCoW - this SHOULD be implemented labels Sep 9, 2020
@pmonks
Copy link
Owner Author

pmonks commented Sep 10, 2020

First cut of implementation of this in rev 34087e5.

@pmonks
Copy link
Owner Author

pmonks commented Sep 11, 2020

Fixed in PR #103.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature, functionality or request functional Functional (i.e. user-visible) work should MoSCoW - this SHOULD be implemented
Projects
None yet
Development

No branches or pull requests

1 participant