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
While this is a great approach to not forget about them for long periods of time, there is still the risk of missing to open them in time to be prioritized. They also consists of a bunch of repetitive tasks that we need to do on the Engineering board, after their creation to make them ready to be worked on.
We should consider automating this efforts:
The content you are editing has changed. Please copy your edits and refresh the page.
Scheduling recurring tasks is something that was thinking about in https://github.com/2i2c-org/meta/issues/1498 . While the overall procedure is out of scope for this epic, there are some GitHub issue scheduling subtasks that I think fit in this epic.
We have at least two types of recurrent tasks that we know when we need to do and we know hot to do them
Currently they are tracked by @yuvipanda I believe in this calendar
Proposal
While this is a great approach to not forget about them for long periods of time, there is still the risk of missing to open them in time to be prioritized. They also consists of a bunch of repetitive tasks that we need to do on the Engineering board, after their creation to make them ready to be worked on.
We should consider automating this efforts:
Tasks
The text was updated successfully, but these errors were encountered: