-
Notifications
You must be signed in to change notification settings - Fork 229
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
Optimize the use of GitHib tickets #1909
Labels
Comments
Two that we agreed on:
|
Suggest all tickets adopt "SMART" project management criteria:
|
from discussion during #1917 going to see if @programminghistorian/technical-team can help with producing analytics like this one which shows how long an issue is open on the Jekyll Repository (this one was created by me). |
6 tasks
10 tasks
I don't think this ticket has a clear action. I propose closing at #2019 meeting |
9 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As we discussed in the meeting, we open several tickets in GitHub and they are not always as effective. The question is: which types of issues require always opening a ticket and which one can be discussed via email/slack?
The text was updated successfully, but these errors were encountered: