{"action":"created","issue":{"url":"https://api.github.com/repos/gvwilson/new-lesson-example/issues/3","repository_url":"https://api.github.com/repos/gvwilson/new-lesson-example","labels_url":"https://api.github.com/repos/gvwilson/new-lesson-example/issues/3/labels{/name}","comments_url":"https://api.github.com/repos/gvwilson/new-lesson-example/issues/3/comments","events_url":"https://api.github.com/repos/gvwilson/new-lesson-example/issues/3/events","html_url":"https://github.com/gvwilson/new-lesson-example/pull/3","id":150948144,"number":3,"title":"CONTRIBUTING: Split development notes into their own file","user":{"login":"wking","id":209920,"avatar_url":"https://avatars.githubusercontent.com/u/209920?v=3","gravatar_id":"","url":"https://api.github.com/users/wking","html_url":"https://github.com/wking","followers_url":"https://api.github.com/users/wking/followers","following_url":"https://api.github.com/users/wking/following{/other_user}","gists_url":"https://api.github.com/users/wking/gists{/gist_id}","starred_url":"https://api.github.com/users/wking/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/wking/subscriptions","organizations_url":"https://api.github.com/users/wking/orgs","repos_url":"https://api.github.com/users/wking/repos","events_url":"https://api.github.com/users/wking/events{/privacy}","received_events_url":"https://api.github.com/users/wking/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":4,"created_at":"2016-04-25T18:43:03Z","updated_at":"2016-04-26T03:51:01Z","closed_at":null,"pull_request":{"url":"https://api.github.com/repos/gvwilson/new-lesson-example/pulls/3","html_url":"https://github.com/gvwilson/new-lesson-example/pull/3","diff_url":"https://github.com/gvwilson/new-lesson-example/pull/3.diff","patch_url":"https://github.com/gvwilson/new-lesson-example/pull/3.patch"},"body":"The previous README contained notes for example-lesson developers\n(e.g. Git workflow notes) as well as notes for lesson consumers\n(e.g. _config_template.yml copying).  This commit splits the former\ninto [GitHub's preferred file][1].  That ensures the license\ninformation, code of conduct, and other development-critical notes are\nhighlighted and easily accessible to anyone filing and issue or\npull-request against this repository.\n\n[1]: https://github.com/blog/1184-contributing-guidelines"},"comment":{"url":"https://api.github.com/repos/gvwilson/new-lesson-example/issues/comments/214603635","html_url":"https://github.com/gvwilson/new-lesson-example/pull/3#issuecomment-214603635","issue_url":"https://api.github.com/repos/gvwilson/new-lesson-example/issues/3","id":214603635,"user":{"login":"wking","id":209920,"avatar_url":"https://avatars.githubusercontent.com/u/209920?v=3","gravatar_id":"","url":"https://api.github.com/users/wking","html_url":"https://github.com/wking","followers_url":"https://api.github.com/users/wking/followers","following_url":"https://api.github.com/users/wking/following{/other_user}","gists_url":"https://api.github.com/users/wking/gists{/gist_id}","starred_url":"https://api.github.com/users/wking/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/wking/subscriptions","organizations_url":"https://api.github.com/users/wking/orgs","repos_url":"https://api.github.com/users/wking/repos","events_url":"https://api.github.com/users/wking/events{/privacy}","received_events_url":"https://api.github.com/users/wking/received_events","type":"User","site_admin":false},"created_at":"2016-04-26T03:51:01Z","updated_at":"2016-04-26T03:51:01Z","body":"On Mon, Apr 25, 2016 at 05:41:40PM -0700, Greg Wilson wrote:\n> CONTRIBUTING.md will have the URL of the project repo (probably\n> several times - link to issues page, etc.), and I expect custom\n> content in some CONTRIBUTING pages as well (e.g., the R lesson), and\n> I want to keep repeated conflicts/merges to zero.\n\nI agree about downstream changes, but I don't see a need for us to be\nmessing with CONTRIBUTING.md upstream.  With the layout in my commit,\nit's likely that R-specific advice would go in the README (where the\nexample talks about ‘make’.\n\nLooking through the current lesson examples for some historical\ncontext [1]:\n\n* 2015-04-14 Remove list of maintainers, swcarpentry/lesson-example#2\n* 2015-04-04 References to the README and template,\n  swcarpentry/lesson-template@340f3e8\n* 2015-03-01 Fix reference to Pro Git,\n  swcarpentry/lesson-example@1edfd93\n* 2015-03-01 Add reference to the code of conduct,\n  swcarpentry/lesson-example@0aa41ed\n* 2015-02-13 Sync between core and gh-pages,\n  swcarpentry/lesson-example@7547e80\n* 2015-02-13 Add reference to SWC lessons, welcome issues & PRs,\n  swcarpentry/lesson-example@d1542fe\n* 2015-02-12 Remove trailing whitespace and YAML front-matter.  Link\n  to LICENSE.html instead of LICENSE.md,\n  swcarpentry/lesson-example@d487a51\n* 2015-02-11 Add CONTRIBUTING.md,\n  swcarpentry/lesson-example@4923b02\n\nSo anybody who got in after the first week has only seen four changes,\nand there have been no changes in the past year.\n\nSo zero is a difficult goal, but “around two changes a year” seems\neasily achievable.  And if we're switching template systems every two\nyears anyway, it's hard to do much better than that ;).\n\n[1]: https://github.com/swcarpentry/lesson-example/commits/gh-pages/CONTRIBUTING.md\n"}}