{"action":"created","issue":{"url":"https://api.github.com/repos/beakerbrowser/beaker/issues/1053","repository_url":"https://api.github.com/repos/beakerbrowser/beaker","labels_url":"https://api.github.com/repos/beakerbrowser/beaker/issues/1053/labels{/name}","comments_url":"https://api.github.com/repos/beakerbrowser/beaker/issues/1053/comments","events_url":"https://api.github.com/repos/beakerbrowser/beaker/issues/1053/events","html_url":"https://github.com/beakerbrowser/beaker/issues/1053","id":335007523,"node_id":"MDU6SXNzdWUzMzUwMDc1MjM=","number":1053,"title":"Code of Conduct","user":{"login":"xtianjohns","id":2087279,"node_id":"MDQ6VXNlcjIwODcyNzk=","avatar_url":"https://avatars3.githubusercontent.com/u/2087279?v=4","gravatar_id":"","url":"https://api.github.com/users/xtianjohns","html_url":"https://github.com/xtianjohns","followers_url":"https://api.github.com/users/xtianjohns/followers","following_url":"https://api.github.com/users/xtianjohns/following{/other_user}","gists_url":"https://api.github.com/users/xtianjohns/gists{/gist_id}","starred_url":"https://api.github.com/users/xtianjohns/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/xtianjohns/subscriptions","organizations_url":"https://api.github.com/users/xtianjohns/orgs","repos_url":"https://api.github.com/users/xtianjohns/repos","events_url":"https://api.github.com/users/xtianjohns/events{/privacy}","received_events_url":"https://api.github.com/users/xtianjohns/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2018-06-22T20:22:38Z","updated_at":"2018-06-25T16:42:14Z","closed_at":null,"author_association":"NONE","body":"Let's add a code of conduct to the Beaker repo! The P2P web community is a big tent, I'm not saying we need to circumscribe acceptable behavior when _using_ Beaker. But a least on engaging in issues, pull requests, events, livestreams, meet ups, etc., I think it makes sense for the community to thoughtfully consider its standards of acceptable behavior.\r\n\r\nI'm happy to work on a PR, but perhaps it's better to start a conversation first about what is worth including and in particular what is important to @pfrazee and @taravancil on these questions.\r\n\r\nThe community already seems great, let's make sure we keep it that way!\r\n\r\nOperation System: *\r\nBeaker version: *\r\n"},"comment":{"url":"https://api.github.com/repos/beakerbrowser/beaker/issues/comments/400017604","html_url":"https://github.com/beakerbrowser/beaker/issues/1053#issuecomment-400017604","issue_url":"https://api.github.com/repos/beakerbrowser/beaker/issues/1053","id":400017604,"node_id":"MDEyOklzc3VlQ29tbWVudDQwMDAxNzYwNA==","user":{"login":"xtianjohns","id":2087279,"node_id":"MDQ6VXNlcjIwODcyNzk=","avatar_url":"https://avatars3.githubusercontent.com/u/2087279?v=4","gravatar_id":"","url":"https://api.github.com/users/xtianjohns","html_url":"https://github.com/xtianjohns","followers_url":"https://api.github.com/users/xtianjohns/followers","following_url":"https://api.github.com/users/xtianjohns/following{/other_user}","gists_url":"https://api.github.com/users/xtianjohns/gists{/gist_id}","starred_url":"https://api.github.com/users/xtianjohns/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/xtianjohns/subscriptions","organizations_url":"https://api.github.com/users/xtianjohns/orgs","repos_url":"https://api.github.com/users/xtianjohns/repos","events_url":"https://api.github.com/users/xtianjohns/events{/privacy}","received_events_url":"https://api.github.com/users/xtianjohns/received_events","type":"User","site_admin":false},"created_at":"2018-06-25T16:42:14Z","updated_at":"2018-06-25T16:42:14Z","author_association":"NONE","body":"Github's CoC template comes from [The Contributor Covenant](https://www.contributor-covenant.org/version/1/4/code-of-conduct). I think it is worth looking at because it is an opportunity to borrow language from a template/standard that many folks on Github would be familiar.\r\n\r\nI also checked out CoCs from other browser projects (like [Chromium](https://chromium.googlesource.com/chromium/src/+/master/CODE_OF_CONDUCT.md)), but found that there was lots of language specific to the project or domain. That's probably a good thing, but makes it harder to use them as templates/guides.\r\n\r\nFWIW I find a lot to like in Rust's CoC. It is\r\n\r\n1. **Explicit.** Using specific language when describing harassment and enforcement helps prevent situations where people feel that the code of conduct is open to interpretation. If the CoC is ambiguous, it can make any maintainers appear to be arbitrary, showing favoritism, or that it insufficiently protects members of socially marginalized groups.\r\n\r\n> _We will exclude you from interaction if you insult, demean or harass anyone._\r\n\r\n> _We interpret the term “harassment” as...._\r\n\r\n> _Private harassment is also unacceptable._\r\n\r\n2. **Affirmative.** It is not just a list of what not to do, or a list of punishments for various offenses. It affirms what values are important to the community. This provides a positive statement of values, from which specific statements about harassment or exclusionary behavior can be made.\r\n\r\n> _We are committed to providing a friendly, safe and welcoming environment for all...._\r\n\r\n> _Whether you’re a regular contributor or a newcomer, we care about making this community a safe place for you and we’ve got your back._\r\n\r\n> _In the Rust community we strive to go the extra step to look out for each other._"}}
{"actor":{"display_login":"xtianjohns"}}