You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For a long period of time, the Discord bots have either not been working, or not had the right features. An attempt was made to update one of the existing bots and add a new tipping bot here #4, however it is both old and also there are issues in implementation and feature set.
Proposal
I am here introducing three distinct and explicit requirements for each of the bots we see a role for in the Discord at this time. The purpose of this initiative is to level set on exactly what each bot should do, and how implementation, review and deployment should work.
Notification bot requirements: WIP, unclear if worth it - given that Pioneer notifications will soon work, and it can easily backfire if it gets noisy, as it often has.
These have been ordered in terms of desdending ROI, so executing in order is probably a good idea. These bots should be in separate codebases, but one repo, and PRs should be updating one at a time if at all possible. If there is some generic code that needs to be shared, put that in some new common util/commons folder.
IMPORTANTLY: we are starting from scratch here, the current bots have all sorts of legacy behaviors which should not carry over.
The text was updated successfully, but these errors were encountered:
Background
For a long period of time, the Discord bots have either not been working, or not had the right features. An attempt was made to update one of the existing bots and add a new tipping bot here #4, however it is both old and also there are issues in implementation and feature set.
Proposal
I am here introducing three distinct and explicit requirements for each of the bots we see a role for in the Discord at this time. The purpose of this initiative is to level set on exactly what each bot should do, and how implementation, review and deployment should work.
These have been ordered in terms of desdending ROI, so executing in order is probably a good idea. These bots should be in separate codebases, but one repo, and PRs should be updating one at a time if at all possible. If there is some generic code that needs to be shared, put that in some new common util/commons folder.
IMPORTANTLY: we are starting from scratch here, the current bots have all sorts of legacy behaviors which should not carry over.
The text was updated successfully, but these errors were encountered: