{"action":"created","issue":{"url":"https://api.github.com/repos/ayojs/ayo/issues/36","repository_url":"https://api.github.com/repos/ayojs/ayo","labels_url":"https://api.github.com/repos/ayojs/ayo/issues/36/labels{/name}","comments_url":"https://api.github.com/repos/ayojs/ayo/issues/36/comments","events_url":"https://api.github.com/repos/ayojs/ayo/issues/36/events","html_url":"https://github.com/ayojs/ayo/issues/36","id":254443741,"number":36,"title":"Request for disclosure of details behind decision to fork","user":{"login":"lekoder","id":1224527,"avatar_url":"https://avatars2.githubusercontent.com/u/1224527?v=4","gravatar_id":"","url":"https://api.github.com/users/lekoder","html_url":"https://github.com/lekoder","followers_url":"https://api.github.com/users/lekoder/followers","following_url":"https://api.github.com/users/lekoder/following{/other_user}","gists_url":"https://api.github.com/users/lekoder/gists{/gist_id}","starred_url":"https://api.github.com/users/lekoder/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/lekoder/subscriptions","organizations_url":"https://api.github.com/users/lekoder/orgs","repos_url":"https://api.github.com/users/lekoder/repos","events_url":"https://api.github.com/users/lekoder/events{/privacy}","received_events_url":"https://api.github.com/users/lekoder/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":3,"created_at":"2017-08-31T19:32:33Z","updated_at":"2017-09-01T09:23:46Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"I understand that your decision to fork node was caused by claim of [numerous violations of Code of Conduct of node.js](https://github.com/nodejs/TSC/issues/310) by @rvagg, and TSC's vote on the issue - this is public knowledge at this point.\r\n\r\nWhile breach of CoC is a legitimate concern, there seems to be no details available to the public about exact nature of these violations. Secrecy of this process makes it impossible for me, and probably many other contributors and users of node.js, to judge decision about validity of your action, and therefore making informed choice of supporting either ayo.js, node.js or both.\r\n\r\nIn spirit of maintaining transparency of this issue I would like to request, assuming that Rod, as immediately interested party will grant permission to do so, disclosure exact nature of claims of violations of CoC, which led to this crisis."},"comment":{"url":"https://api.github.com/repos/ayojs/ayo/issues/comments/326533976","html_url":"https://github.com/ayojs/ayo/issues/36#issuecomment-326533976","issue_url":"https://api.github.com/repos/ayojs/ayo/issues/36","id":326533976,"user":{"login":"benjamingr","id":1315533,"avatar_url":"https://avatars2.githubusercontent.com/u/1315533?v=4","gravatar_id":"","url":"https://api.github.com/users/benjamingr","html_url":"https://github.com/benjamingr","followers_url":"https://api.github.com/users/benjamingr/followers","following_url":"https://api.github.com/users/benjamingr/following{/other_user}","gists_url":"https://api.github.com/users/benjamingr/gists{/gist_id}","starred_url":"https://api.github.com/users/benjamingr/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/benjamingr/subscriptions","organizations_url":"https://api.github.com/users/benjamingr/orgs","repos_url":"https://api.github.com/users/benjamingr/repos","events_url":"https://api.github.com/users/benjamingr/events{/privacy}","received_events_url":"https://api.github.com/users/benjamingr/received_events","type":"User","site_admin":false},"created_at":"2017-09-01T09:23:46Z","updated_at":"2017-09-01T09:23:46Z","author_association":"COLLABORATOR","body":"> In fact \"inclusive\" hardly maps to \"software project\" in my mindset \r\n\r\nI think that in general the project has done a very good job in keeping its contributors outside of that and provided a safe environment for them. I do think there were several cases of non-inclusive behavior and while I'm not familiar with any that force a fork - I think forks are a good thing (tm) and more diversity in the ecosystem is good.\r\n\r\nThat said - I definitely think the following holds:\r\n\r\n - Node.js is a big project that needs a lot of collaborators to evolve effectively.\r\n - A lot of the Node.js collaborators are _not_ from a \"traditional\" contributors background.\r\n - A lot of those \"non traditional\" collaborators are doing amazing technical work.\r\n - The project is benefiting from diversity in a directly technical way.\r\n\r\nI think the people who forked Ayo are trying to put a emphasis on the \"human\" side of being an open source collaborator. Often times people open issues that take a long time and a lot of debate to land and I think that the belief is that focusing on a supportive environment is a driving factor for Ayo too.\r\n\r\nQuoting [the VALUES document](https://github.com/ayojs/ayo/blob/master/VALUES.md):\r\n\r\n> Technical discussions are difficult, especially in large communities with members with all sorts of perspectives. Contributors are bound to find themselves in situations with no clear consensus, with new concerns being brought up on a regular basis, and things that might seem insignificant in other contexts suddenly exploding.\r\n\r\nI can share from personal experience that this has been the case _many times_ over the years.\r\n\r\n> The Ayo.js project’s perspective is that when such things happen, it often takes a toll on the well-being of the members participating, at times preventing repeated contributions or precluding new contributors outright. It also recognizes that the difference between individual choices is less important than the ability to come to an appropriate technical decision.\r\n\r\nI can also share from personal experience that this is very frustrating and several \"high profile\" people in web development have also shared this experience with me.\r\n\r\n---\r\n\r\nAyo doesn't seem to be picking on or excluding any existing contributors. This is not about one person. I'm not picking sides and I'm not even sure if there is a 'better' side - we'll just have to see how this model works compared to Node.js's - definitely a positive thing for the web.\r\n "}}
{"actor":{"display_login":"benjamingr"}}