{"action":"closed","issue":{"url":"https://api.github.com/repos/iojs/io.js/issues/231","labels_url":"https://api.github.com/repos/iojs/io.js/issues/231/labels{/name}","comments_url":"https://api.github.com/repos/iojs/io.js/issues/231/comments","events_url":"https://api.github.com/repos/iojs/io.js/issues/231/events","html_url":"https://github.com/iojs/io.js/issues/231","id":53236919,"number":231,"title":"Roadmap development","user":{"login":"rvagg","id":495647,"avatar_url":"https://avatars.githubusercontent.com/u/495647?v=3","gravatar_id":"","url":"https://api.github.com/users/rvagg","html_url":"https://github.com/rvagg","followers_url":"https://api.github.com/users/rvagg/followers","following_url":"https://api.github.com/users/rvagg/following{/other_user}","gists_url":"https://api.github.com/users/rvagg/gists{/gist_id}","starred_url":"https://api.github.com/users/rvagg/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rvagg/subscriptions","organizations_url":"https://api.github.com/users/rvagg/orgs","repos_url":"https://api.github.com/users/rvagg/repos","events_url":"https://api.github.com/users/rvagg/events{/privacy}","received_events_url":"https://api.github.com/users/rvagg/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":7,"created_at":"2015-01-02T04:17:59Z","updated_at":"2015-01-24T22:34:34Z","closed_at":"2015-01-24T22:34:34Z","body":"As part of the [2014-12-17 TC meeting](https://github.com/iojs/io.js/blob/v1.x/doc/tc-meetings/2014-12-17.md#dealing-with-feature-requests), there's a desire to start pulling together a roadmap of sorts to guide the direction of the project.\r\n\r\nThe first step is to seek input from the community and this has been happening somewhat in the [roadmap](https://github.com/iojs/roadmap) repo but it's become a little too bunched up in the \"pain points\" issue so it's hard to pull apart.\r\n\r\n_Somebody_, at some stage, will start to pull together a roadmap proposal to take to the TC for discussion and possible acceptance, but first it needs ideas enumerated as issues in the roadmap issue.\r\n\r\n**How to contribute**\r\n\r\nCreate an issue for each discrete _idea_ or roadmap _item_ in the [roadmaps repo](https://github.com/iojs/roadmap/issues) with the intent to start discussion and get greater feedback. Please be aware that proposing something doesn't guarantee acceptance or even any sort of discussion beyond yourself so be prepared for that.\r\n\r\nSomebody needs to start pulling together roadmap-suitable items from the repo that are practical and don't conflict with the broader goals of the project into a roadmap document. What form this takes and the timeframes involved is intentionally vague and open to interpretation; and indeed the \"goals\" are not clearly defined beyond a stated desire to remain compatible with Node.js releases. Ideally the person would already be a committer or a TC member and be fully aware of the practicalities and goals and not likely to propose something too far from what the TC is likely to accept. This would also be a good case for collaboration amongst multiple people, e.g. propose a skeleton via PR and allow discussion to shape it. At some point I'll probably step in and start this process if nobody else does. I'll probably step in at some point and make a start on this if nobody else does."}}