{"action":"created","issue":{"url":"https://api.github.com/repos/redstone-dart/redstone/issues/100","labels_url":"https://api.github.com/repos/redstone-dart/redstone/issues/100/labels{/name}","comments_url":"https://api.github.com/repos/redstone-dart/redstone/issues/100/comments","events_url":"https://api.github.com/repos/redstone-dart/redstone/issues/100/events","html_url":"https://github.com/redstone-dart/redstone/issues/100","id":67868567,"number":100,"title":"Roadmap","user":{"login":"cgarciae","id":5862228,"avatar_url":"https://avatars.githubusercontent.com/u/5862228?v=3","gravatar_id":"","url":"https://api.github.com/users/cgarciae","html_url":"https://github.com/cgarciae","followers_url":"https://api.github.com/users/cgarciae/followers","following_url":"https://api.github.com/users/cgarciae/following{/other_user}","gists_url":"https://api.github.com/users/cgarciae/gists{/gist_id}","starred_url":"https://api.github.com/users/cgarciae/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/cgarciae/subscriptions","organizations_url":"https://api.github.com/users/cgarciae/orgs","repos_url":"https://api.github.com/users/cgarciae/repos","events_url":"https://api.github.com/users/cgarciae/events{/privacy}","received_events_url":"https://api.github.com/users/cgarciae/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/redstone-dart/redstone/labels/meta","name":"meta","color":"fbca04"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-04-12T04:06:40Z","updated_at":"2015-04-12T05:12:45Z","closed_at":null,"body":"Really happy with the new (social) direction Redstone has taken.\r\n\r\nIn #98 @kaendfinger proposed the creation of a roadmap and I proposed a (TDD) development model based on defining features first, then creating broken features and broken tests, and leaving the implementation to the community (us).\r\n\r\nWhere shall we create this roadmap? Shall we call it release and use the Milestone? @luizmineo should really tell us where Redstone is headed, what is missing, etc.\r\nWhat do you think of my proposal for development? Does anybody know how to use a continuous integration system like travis with Dart?"},"comment":{"url":"https://api.github.com/repos/redstone-dart/redstone/issues/comments/91993725","html_url":"https://github.com/redstone-dart/redstone/issues/100#issuecomment-91993725","issue_url":"https://api.github.com/repos/redstone-dart/redstone/issues/100","id":91993725,"user":{"login":"cgarciae","id":5862228,"avatar_url":"https://avatars.githubusercontent.com/u/5862228?v=3","gravatar_id":"","url":"https://api.github.com/users/cgarciae","html_url":"https://github.com/cgarciae","followers_url":"https://api.github.com/users/cgarciae/followers","following_url":"https://api.github.com/users/cgarciae/following{/other_user}","gists_url":"https://api.github.com/users/cgarciae/gists{/gist_id}","starred_url":"https://api.github.com/users/cgarciae/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/cgarciae/subscriptions","organizations_url":"https://api.github.com/users/cgarciae/orgs","repos_url":"https://api.github.com/users/cgarciae/repos","events_url":"https://api.github.com/users/cgarciae/events{/privacy}","received_events_url":"https://api.github.com/users/cgarciae/received_events","type":"User","site_admin":false},"created_at":"2015-04-12T05:12:45Z","updated_at":"2015-04-12T05:12:45Z","body":"@redstone-dart/owners\r\nThe roadmap has been created under `roadmaps/v0.6.md`. Here is the place to design/document the expected features for the `v0.6` release, get updated on what is missing, discussion on the content could be done through issues. @kaendfinger @austincummings I think changes to this document should always be reviewed.\r\n\r\nAs for the development model, the proposal is this:\r\n*  Should be release/milestone based\r\n*  Features for each release/milestone should be defined in the roadmap\r\n*  Each feature should be implement **broken** first. Might be in the form of a new class with empty methods, new empty methods on an existing class, or an empty branch of code on an existing method. Example\r\n```dart\r\nclass SomeClass\r\n{\r\n    C newMethod(A a, B b)\r\n    {\r\n        throw new UnimplmentedError ();\r\n    }\r\n\r\n    D existingMethod (F f, H h, X newParam)\r\n    {\r\n        //Existing code\r\n        ...\r\n        //New Code\r\n        if (someCondition)\r\n        {\r\n            throw new UnimplmentedError ();\r\n        }\r\n        ...\r\n    }\r\n}\r\n```\r\n*  **Empty** test for each feature should be written along with the broken implementation. Example\r\n```dart\r\ngroup (\"New Feature X\", ()\r\n{\r\n    test (\"some test\", ()\r\n    {\r\n        throw new UnimplementedError ();\r\n    });\r\n});\r\n```\r\n*  Tests should be checked by Travis or equivalent system. (Although I don't if there will be problems with Github since technically at least 1 test should fail until the very end)."}}