{"action":"created","issue":{"url":"https://api.github.com/repos/pandegroup/openmm/issues/977","labels_url":"https://api.github.com/repos/pandegroup/openmm/issues/977/labels{/name}","comments_url":"https://api.github.com/repos/pandegroup/openmm/issues/977/comments","events_url":"https://api.github.com/repos/pandegroup/openmm/issues/977/events","html_url":"https://github.com/pandegroup/openmm/issues/977","id":89780946,"number":977,"title":"Proposal to make use of issue tagging","user":{"login":"jchodera","id":3656088,"avatar_url":"https://avatars.githubusercontent.com/u/3656088?v=3","gravatar_id":"","url":"https://api.github.com/users/jchodera","html_url":"https://github.com/jchodera","followers_url":"https://api.github.com/users/jchodera/followers","following_url":"https://api.github.com/users/jchodera/following{/other_user}","gists_url":"https://api.github.com/users/jchodera/gists{/gist_id}","starred_url":"https://api.github.com/users/jchodera/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jchodera/subscriptions","organizations_url":"https://api.github.com/users/jchodera/orgs","repos_url":"https://api.github.com/users/jchodera/repos","events_url":"https://api.github.com/users/jchodera/events{/privacy}","received_events_url":"https://api.github.com/users/jchodera/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-06-20T15:16:40Z","updated_at":"2015-06-20T15:30:26Z","closed_at":null,"body":"We're up to 127 issues here.  I propose we finally make use of GitHub's powerful issue tagging system.\r\n\r\nTo keep us from getting lost in a sea of issues, we can tag issues using a few basic tags, like:\r\n* bug report\r\n* feature request\r\n* question\r\n* documentation\r\n* request for comments\r\n* build issue\r\n\r\nThis would help us easily sort whether there are bugs remaining to be fixed, or identify all of the feature requests to separate them from other general usage questions.\r\n\r\nWe can also make use of the release planning system, where release targets could be enumerated (e.g. 6.4, 6.5, 7.0) and feature requests could be associated with release targets.  That way, the roadmap for features would be clear to everyone.\r\n\r\nI think this would really help streamline things."},"comment":{"url":"https://api.github.com/repos/pandegroup/openmm/issues/comments/113782390","html_url":"https://github.com/pandegroup/openmm/issues/977#issuecomment-113782390","issue_url":"https://api.github.com/repos/pandegroup/openmm/issues/977","id":113782390,"user":{"login":"VijayPande","id":2255932,"avatar_url":"https://avatars.githubusercontent.com/u/2255932?v=3","gravatar_id":"","url":"https://api.github.com/users/VijayPande","html_url":"https://github.com/VijayPande","followers_url":"https://api.github.com/users/VijayPande/followers","following_url":"https://api.github.com/users/VijayPande/following{/other_user}","gists_url":"https://api.github.com/users/VijayPande/gists{/gist_id}","starred_url":"https://api.github.com/users/VijayPande/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/VijayPande/subscriptions","organizations_url":"https://api.github.com/users/VijayPande/orgs","repos_url":"https://api.github.com/users/VijayPande/repos","events_url":"https://api.github.com/users/VijayPande/events{/privacy}","received_events_url":"https://api.github.com/users/VijayPande/received_events","type":"User","site_admin":false},"created_at":"2015-06-20T15:30:26Z","updated_at":"2015-06-20T15:30:26Z","body":"+1\n\n\n> On Jun 20, 2015, at 8:16 AM, John Chodera <notifications@github.com> wrote:\n> \n> We're up to 127 issues here. I propose we finally make use of GitHub's powerful issue tagging system.\n> \n> To keep us from getting lost in a sea of issues, we can tag issues using a few basic tags, like:\n> \n> bug report\n> feature request\n> question\n> documentation\n> request for comments\n> build issue\n> This would help us easily sort whether there are bugs remaining to be fixed, or identify all of the feature requests to separate them from other general usage questions.\n> \n> We can also make use of the release planning system, where release targets could be enumerated (e.g. 6.4, 6.5, 7.0) and feature requests could be associated with release targets. That way, the roadmap for features would be clear to everyone.\n> \n> I think this would really help streamline things.\n> \n> —\n> Reply to this email directly or view it on GitHub <https://github.com/pandegroup/openmm/issues/977>.\n> \n\n"}}