-
Notifications
You must be signed in to change notification settings - Fork 5
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
Alerts for when flair apps pile up #74
Comments
This could be tricky because we would need to give Porygon-Bot privileged access to the FlairHQ database or API, which it doesn't have at the moment. |
Should the goal be eventually a line that encompasses both this and #67? Or should this be a different notification? I feel like a line that says 'X number of reports & X number of flair apps' would be most efficient and reduce notification clutter. |
I would prefer to keep it separate. One more line doesn't hurt anyone, and it'd probably be more legible that way. Plus, frequency would be different. We discussed doing notifications for flair apps every 1-2 hours, but maybe once every 3-4 hours would be better. Also, while I'm here... Based on IRC discussion, we'd want notifications for both the number of flair apps, and for flair apps being open for too long, and there would only be notifications when we reach a certain threshold. For the actual threshold, maybe 5-10? 5 is low enough that it's easy for one person to knock out without much difficulty, but may be a bit low and result in us being notified of apps more often than we'd want. I'm not sure how often they come in. Also, since our flair guide says we'll get to apps within "a few days", we should probably start doing notifications for outstanding apps at the 2 day mark. If there are just too many apps, the actual notification could look something like this:
If there are apps open for too long:
|
Would it be okay to create a new page (maybe https://hq.porygon.co/flair/apps/queue) that is public so that the bot can grab it? We could remove all the unnecessary info (basically just listing out the creation dates). That way we can grab the date of the oldest app as well as the number of apps. I think this is what was proposed before as an alternative to giving porygon-bot more access. |
No description provided.
The text was updated successfully, but these errors were encountered: