open-bus icon indicating copy to clipboard operation
open-bus copied to clipboard

Published 20 hours ago • verified publisher icon hasadna

Organize github Issues

Open cjer opened this issue 5 years ago • 2 comments

  1. Close old/irrelevant issues. Link them to newer/relevant issues if exists.
  2. Come up with an initial labeling scheme, to match new task management methods. Add it to CONTRIBUTING.md file.
  3. Go over all remaining issues and label them correctly.

Any opinions about good and helpful labels for issues?

cjer avatar Apr 21 '19 20:04 cjer

We need to change our labeling system as I tried to go over the issues that are opened, and it was very difficult to understand the status and the type of the issue

Types can be

Design Question Discussion Bug Code Documentation

and then we can use lifecycle of

Working Review Backlog Ready\Closed

to be able to monitor the tasks (especially code, bug, and documentation)

https://github.com/dotnet/roslyn/wiki/Labels-used-for-issues

ronlik26 avatar Apr 22 '19 10:04 ronlik26

I think that each issue should have label of:

  1. Type Question Discussion Bug Documentation Epic - Issue that represent big story that will implemented by more than one task
    Task - suppose to take 2-3 days

  2. for each epic we will define new label that start with Epic: xyz and all the issues of that epic will have that reference. In this way we could see all the tasks that belongs to epic.

  3. Domain GTFS SIRI data-science etc.

AvivSela avatar Apr 22 '19 21:04 AvivSela