Github issues cleanup

[rdeltour]

Go through all issues in all repos and

• check whether the issue is actually (still) an issue
  • if the issue has been fixed or not relevant anymore, close it
  • if you're not sure, try to reproduce with the latest version, open the discussion again, ask more info from the creator, etc.
  • if you don't acknowledge there is an issue, close it
  • if you reject the issue, e.g. because it is an unreasonable request, add the label wontfix and close
  • if PR: check if it was merged already and if so, close
• if PR and not assigned for review yet, assign someone
• if PR may be merged, merge
• mark duplicates (with label duplicate)
• mention related issues
• possibly move issues to other repos
• label issues (not PRs)
  • bug, enhancement, feature, refactoring, documentation, usability, idea, question, waiting for feedback, etc.
  • optional: time estimation
    • : Extra small (1 hour - 2 hours)
    • : Small (2 hours - 1 day)
    • : Medium (1 day - 2 days)
    • : Large (2 days - 1 week)
    • : Extra large (1 week - 2 weeks)
    • : Extra extra large (2 weeks - 1 month)
  • optional: easyhack
  • optional: Huboard labels to indicate progress/prioritization:
    • 0 - Backlog
    • 1 - Next
    • 2 - In progress
    • 3 - Review
    • 4 - Done
    • 5 - Testing
  • optional: priority
    • prio:1 (highest)
    • prio:2
    • prio:3
• possibly set milestone
  • 1.12.0: planned for a certain release
  • Hot: Tasks that should be worked-on ASAP. Top priorities or ongoing work.
  • Next: Tasks that should be tackled next (say, in the next 2 months). High priorities. That would typically contain the backlog for the next release.
  • After: Tasks that we foresee will be tackled after the high priorities (i.e. after the Hot and Next milestones).
  • Evergreen
• for daisy/pipeline repository, set labels pipeline-scripts, pipeline-gui, etc. to indicate to which subrepos the issue belongs
• when all the above has been done and the issue is still open, add the label accepted

If a label or milestone doesn't exist, ask me (Bert) and I'll create it in all repositories at the same time with a script.

See the following links to get an overview of the issues and pull requests in all repos:

• open
• open, not accepted
• open, accepted, no milestone
• open, accepted, no priority
• open, accepted, not assigned
• open, accepted, assigned to Bert
• open, accepted, assigned to you
• open, accepted, no time estimation
• open, accepted, backlog
• open, accepted, to do next
• open, accepted, in progress
• open, accepted, under review
• open, accepted, done
• open, accepted, under test

[bertfrees]

Removing the milestone because this is an ongoing issue.

[bertfrees]

See #72 (comment). Moving all issues to the "pipeline" repository could simplify the searching. On the other hand moving issues from the "pipeline" repository to the right sub-repositories would also make sense.

[bertfrees]

Maybe we should wait until you can batch transfer issues though.