{"action":"closed","issue":{"url":"https://api.github.com/repos/samtools/htsjdk-next-beta/issues/8","repository_url":"https://api.github.com/repos/samtools/htsjdk-next-beta","labels_url":"https://api.github.com/repos/samtools/htsjdk-next-beta/issues/8/labels{/name}","comments_url":"https://api.github.com/repos/samtools/htsjdk-next-beta/issues/8/comments","events_url":"https://api.github.com/repos/samtools/htsjdk-next-beta/issues/8/events","html_url":"https://github.com/samtools/htsjdk-next-beta/issues/8","id":338833126,"node_id":"MDU6SXNzdWUzMzg4MzMxMjY=","number":8,"title":"Setup sane labels for issue tracking (better backlog)","user":{"login":"magicDGS","id":7352559,"node_id":"MDQ6VXNlcjczNTI1NTk=","avatar_url":"https://avatars0.githubusercontent.com/u/7352559?v=4","gravatar_id":"","url":"https://api.github.com/users/magicDGS","html_url":"https://github.com/magicDGS","followers_url":"https://api.github.com/users/magicDGS/followers","following_url":"https://api.github.com/users/magicDGS/following{/other_user}","gists_url":"https://api.github.com/users/magicDGS/gists{/gist_id}","starred_url":"https://api.github.com/users/magicDGS/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/magicDGS/subscriptions","organizations_url":"https://api.github.com/users/magicDGS/orgs","repos_url":"https://api.github.com/users/magicDGS/repos","events_url":"https://api.github.com/users/magicDGS/events{/privacy}","received_events_url":"https://api.github.com/users/magicDGS/received_events","type":"User","site_admin":false},"labels":[{"id":992728057,"node_id":"MDU6TGFiZWw5OTI3MjgwNTc=","url":"https://api.github.com/repos/samtools/htsjdk-next-beta/labels/Module:None","name":"Module:None","color":"f0c7fc","default":false},{"id":992719638,"node_id":"MDU6TGFiZWw5OTI3MTk2Mzg=","url":"https://api.github.com/repos/samtools/htsjdk-next-beta/labels/Priority:Normal","name":"Priority:Normal","color":"ecef3b","default":false},{"id":992720983,"node_id":"MDU6TGFiZWw5OTI3MjA5ODM=","url":"https://api.github.com/repos/samtools/htsjdk-next-beta/labels/Type:Maintenance","name":"Type:Maintenance","color":"f9e740","default":false}],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":12,"created_at":"2018-07-06T07:24:29Z","updated_at":"2018-08-10T11:19:13Z","closed_at":"2018-08-10T11:19:13Z","author_association":"MEMBER","body":"I propose to have a labeling scheme using `Status`, `Type` and `Priority` tags for each issue and PR, similar to the scheme proposed in https://medium.com/@dave_lunny/sane-github-labels-c5d2e6004b63\r\nIn addition, we can have a backlog project (https://github.com/samtools/htsjdk-next-beta/projects) to track all the issues, with some automatization. \r\n\r\nI can setup this soon, and proposals are welcome for it. My idea about the labeling scheme is:\r\n* __Status__: `Abandoned` (discarded issues), `Blocked` (need some work or upstream changes), `In Progress` (someone took over the issue or there is already a PR), `Completed` (finished ones - may be still open to ask for feedback), `On Hold` (work in progress to take a decision or still not in a state for review if a PR), `Review Needed` (for PRs that does not have a review yet). Some optional ones that I have consider but I don't think that would be important are `Under Review` (already reviewed by some maintainer and waiting for the final decision/feedback from the PR author), `Available` (for issues that are available for implementation - they would be nice for contributors to pick issues to work on), `Pending` (for issues that needs some discussion to include in the backlog, either because they are controversial or breaking backwards compatibility).\r\n* __Type__: `Bug`, `Enhancement`, `API` (issues that are related with API changes), `Maintenance` (DevOps, code reafactor without change, cleanup), `Question` (for user/collaborators requested help), `Test` (related with increasing test coverage or adding edge test cases).\r\n* __Priority__:  `Critical` (to pinpoint quickly bugs, security concerns, wrong implementations; this might be redundant with `Type:Bug`, but upgrading a library might be critical and marked as `Type:Maintenance`), `High`, `Medium`, `Low`.\r\n\r\nAs we would implement a multi-module project, we have several options for tracking module-issues:\r\n* Project backlog per-module. That will be a `Core backlog`, `CRAM backlog`, etc. in the repo projects (https://github.com/samtools/htsjdk-next-beta/projects)\r\n* Add a third bidimensional label `Module`, to specify `Module:Core`, `Module:CRAM`, etc. This label could be an optional label or a required one (adding `Module:All` for things affecting all modules, such as DevOps).\r\n* Allow extra labels prefixed with `~` to appear at the end of the list of labels, and indicate that they are not required labels (e.g., `~cram` will identify issues related with CRAM, but it is not required that it is included)."}}
{"actor":{"display_login":"magicDGS"}}