{"action":"closed","issue":{"url":"https://api.github.com/repos/LightTable/LightTable/issues/2255","repository_url":"https://api.github.com/repos/LightTable/LightTable","labels_url":"https://api.github.com/repos/LightTable/LightTable/issues/2255/labels{/name}","comments_url":"https://api.github.com/repos/LightTable/LightTable/issues/2255/comments","events_url":"https://api.github.com/repos/LightTable/LightTable/issues/2255/events","html_url":"https://github.com/LightTable/LightTable/issues/2255","id":175144811,"number":2255,"title":"Update label scheme","user":{"login":"sbauer322","id":2945386,"avatar_url":"https://avatars.githubusercontent.com/u/2945386?v=3","gravatar_id":"","url":"https://api.github.com/users/sbauer322","html_url":"https://github.com/sbauer322","followers_url":"https://api.github.com/users/sbauer322/followers","following_url":"https://api.github.com/users/sbauer322/following{/other_user}","gists_url":"https://api.github.com/users/sbauer322/gists{/gist_id}","starred_url":"https://api.github.com/users/sbauer322/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sbauer322/subscriptions","organizations_url":"https://api.github.com/users/sbauer322/orgs","repos_url":"https://api.github.com/users/sbauer322/repos","events_url":"https://api.github.com/users/sbauer322/events{/privacy}","received_events_url":"https://api.github.com/users/sbauer322/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/LightTable/LightTable/labels/maintenance","name":"maintenance","color":"fbca04"}],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":4,"created_at":"2016-09-06T01:48:04Z","updated_at":"2016-09-16T05:11:32Z","closed_at":"2016-09-16T05:11:31Z","body":"@kenny-evitt, as requested, here is summary of the initial desired label changes. There is nothing too crazy... probably the most significant is appending types to various labels. For instance `status: ` to statuslabels such as `status: blocked`. Since there are multiple changes, I want to get at least one other LT member's okay as a sanity check.\r\n\r\nTo better aid contributors, users, and visitors, I am suggesting we modify our labeling scheme. We are currently at 30 unique labels and it can be burdensome to sift through. Additionally, even with this number of labels we still have vague areas that don't have labels to adequately categorize some issues.\r\n\r\nIn keeping with Github label best practices the following changes are proposed:\r\n\r\n#### General\r\n\r\n- Revise label definitions found in [For Contributors](https://github.com/LightTable/LightTable/wiki/For-Contributors) wiki page. A label's name should be meaningful and clear enough that there is minimal need for elaboration.\r\n- Group types of labels by color. For instance, labels relating to bugs should all be the same or similar colors. Each group of labels should have a distinct color from other groups.\r\n\r\n#### New Labels\r\n\r\n- `parity` labels for a select number of IDEs we feel we should attempt to stay up to speed with feature-wise. (e.g., sublime, atom)\r\n\r\n#### Rename\r\n\r\n- Rename `task` label to `maintenance`. This label should cover all behind-the-scene issues including upgrades.\r\n- Rename `feature` label to make it more significant and distinct from `enhancement`. Current working name `status: accepted`.\r\n\r\nBy prepending the following, related labels will be grouped for easier selection, visibility, and meaning.\r\n\r\n- Prepend `platform: ` to all current platform label names. (Current labels: windows, linux, mac)\r\n- Prepend `status: ` to all current status label names. (Current labels: blocked, in progress)\r\n- Prepend `resolution: ` to all current resolution label names (Current labels: cannot reproduce, duplicate, triaged)\r\n\r\n#### Remove\r\n\r\n- Remove `experience` label and relabel its 2 issues.\r\n- Remove `fixed-on-master` and `fixed-upstream` - they have 0 issues and have not been used since Nov 2015. \r\n- Remove `python` label as we have a python plugin where the issues should be sent.\r\n\r\nAs it always comes down to a question of who or time, I am happy to volunteer to implement the label changes.\r\n\r\nRelevant links:\r\n\r\n- https://robinpowered.com/blog/best-practice-system-for-organizing-and-tagging-github-issues/\r\n- https://docs.saltstack.com/en/latest/topics/development/labels.html\r\n- https://medium.com/@dave_lunny/sane-github-labels-c5d2e6004b63#.rr8537ijk\r\n"}}
{"actor":{"display_login":"sbauer322"}}