{"action":"created","issue":{"url":"https://api.github.com/repos/meteor/blaze/issues/127","repository_url":"https://api.github.com/repos/meteor/blaze","labels_url":"https://api.github.com/repos/meteor/blaze/issues/127/labels{/name}","comments_url":"https://api.github.com/repos/meteor/blaze/issues/127/comments","events_url":"https://api.github.com/repos/meteor/blaze/issues/127/events","html_url":"https://github.com/meteor/blaze/issues/127","id":180072611,"number":127,"title":"Organizing discussions around Blaze ","user":{"login":"msavin","id":2031235,"avatar_url":"https://avatars.githubusercontent.com/u/2031235?v=3","gravatar_id":"","url":"https://api.github.com/users/msavin","html_url":"https://github.com/msavin","followers_url":"https://api.github.com/users/msavin/followers","following_url":"https://api.github.com/users/msavin/following{/other_user}","gists_url":"https://api.github.com/users/msavin/gists{/gist_id}","starred_url":"https://api.github.com/users/msavin/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/msavin/subscriptions","organizations_url":"https://api.github.com/users/msavin/orgs","repos_url":"https://api.github.com/users/msavin/repos","events_url":"https://api.github.com/users/msavin/events{/privacy}","received_events_url":"https://api.github.com/users/msavin/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/meteor/blaze/labels/discussion","name":"discussion","color":"bfd4f2"}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":16,"created_at":"2016-09-29T14:55:11Z","updated_at":"2016-09-30T05:31:51Z","closed_at":null,"body":"One thing I think many of us are struggling with is figuring out what the state of Blaze is, what is being proposed, what has been discussed, etc.\r\n\r\nThat usually leads to a \"read issue X\" response - which I think may discourage people from participating because they don't want to repeat something that might have been was said.\r\n\r\nThe other option is to read all the posts, but that's not enticing as many of them are old, and the discussions are not structured well. It's worse than reading a college textbook.\r\n\r\nMaybe the real solution is to start a Trello board, similar to what Meteor had back in the good old days:\r\nhttps://trello.com/b/hjBDflxp/old-meteor-roadmap-new-roadmap-at-https-github-com-meteor-meteor-blob-devel-roadmap-md\r\n\r\nWe can have sections like [Completed, In Progress, Planned, Ideas]. The first three sections could be locked down, and the fourth one (Ideas) can allow anyone to add a card and develop a discussion around it."},"comment":{"url":"https://api.github.com/repos/meteor/blaze/issues/comments/250662216","html_url":"https://github.com/meteor/blaze/issues/127#issuecomment-250662216","issue_url":"https://api.github.com/repos/meteor/blaze/issues/127","id":250662216,"user":{"login":"mitar","id":585279,"avatar_url":"https://avatars.githubusercontent.com/u/585279?v=3","gravatar_id":"","url":"https://api.github.com/users/mitar","html_url":"https://github.com/mitar","followers_url":"https://api.github.com/users/mitar/followers","following_url":"https://api.github.com/users/mitar/following{/other_user}","gists_url":"https://api.github.com/users/mitar/gists{/gist_id}","starred_url":"https://api.github.com/users/mitar/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mitar/subscriptions","organizations_url":"https://api.github.com/users/mitar/orgs","repos_url":"https://api.github.com/users/mitar/repos","events_url":"https://api.github.com/users/mitar/events{/privacy}","received_events_url":"https://api.github.com/users/mitar/received_events","type":"User","site_admin":false},"created_at":"2016-09-30T05:31:51Z","updated_at":"2016-09-30T05:31:51Z","body":"I made one iteration at projects and categorized all current open issues into [them](https://github.com/meteor/blaze/projects). I hope this makes things clearer, but one still has to read issues to understand what some cryptic titles mean. :-)\r\n\r\nHow does it look? Is this what you had in mind? Feedback welcome.\r\n\r\nThe idea is that only open issues are in projects. So that people can see what is planned and can decide to contribute. For done issues, one should just consult [history](https://github.com/meteor/blaze/blob/master/HISTORY.md), or milestones.\r\n\r\nWe will then use milestones only to group immediate next work, so that people can see what we are focusing on. There are `Being worked on` columns in each project, but they do not group things across projects well. It is also easier to link directly to a milestone and say \"can you help here\". Maybe we can deprecate milestones in the future, if we see that history is enough.\r\n\r\n@aadamsx, thank you for volunteering. I added you and I think you should have enough permissions to manage issues. I agree that for now we should just try to see how it works if we manage them manually. So please if you see any new issue, consider adding it to one of the projects first column. If you see that any issue has been worked on, move it to the last column. And if you see that anything was closed, move it out of the project."}}
{"actor":{"display_login":"mitar"}}