{"action":"reopened","issue":{"url":"https://api.github.com/repos/jakeloggins/crouton-new/issues/5","repository_url":"https://api.github.com/repos/jakeloggins/crouton-new","labels_url":"https://api.github.com/repos/jakeloggins/crouton-new/issues/5/labels{/name}","comments_url":"https://api.github.com/repos/jakeloggins/crouton-new/issues/5/comments","events_url":"https://api.github.com/repos/jakeloggins/crouton-new/issues/5/events","html_url":"https://github.com/jakeloggins/crouton-new/issues/5","id":149208916,"number":5,"title":"crouton-new vs fork","user":{"login":"wickwire","id":2642389,"avatar_url":"https://avatars.githubusercontent.com/u/2642389?v=3","gravatar_id":"","url":"https://api.github.com/users/wickwire","html_url":"https://github.com/wickwire","followers_url":"https://api.github.com/users/wickwire/followers","following_url":"https://api.github.com/users/wickwire/following{/other_user}","gists_url":"https://api.github.com/users/wickwire/gists{/gist_id}","starred_url":"https://api.github.com/users/wickwire/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/wickwire/subscriptions","organizations_url":"https://api.github.com/users/wickwire/orgs","repos_url":"https://api.github.com/users/wickwire/repos","events_url":"https://api.github.com/users/wickwire/events{/privacy}","received_events_url":"https://api.github.com/users/wickwire/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2016-04-18T16:52:42Z","updated_at":"2016-04-20T15:34:39Z","closed_at":null,"body":"Hi,\r\n\r\nWhy the need for a **crouton-new** project, as opposed to forking the original project by **edfungus**? Wouldn't it be easier to incorporate the scheduler feature in your fork, later submitting (or not) your updates via pull request, to the main project?\r\n\r\nYour added work is valuable in my opinion, but in terms of project organization it would probably make more sense to add to the existing main project, rather than start a new one, for each new feature that each user thinks of.\r\n\r\nPlease consider forks and pull requests on your future community development, it makes your work more visible and better contributes to the overall project growth.\r\n\r\nIn any case, thank you for your effort!"}}