{"action":"closed","issue":{"url":"https://api.github.com/repos/nodejs/inclusivity/issues/9","labels_url":"https://api.github.com/repos/nodejs/inclusivity/issues/9/labels{/name}","comments_url":"https://api.github.com/repos/nodejs/inclusivity/issues/9/comments","events_url":"https://api.github.com/repos/nodejs/inclusivity/issues/9/events","html_url":"https://github.com/nodejs/inclusivity/issues/9","id":116188636,"number":9,"title":"How to avoid using problematic language?","user":{"login":"isaacs","id":9287,"avatar_url":"https://avatars.githubusercontent.com/u/9287?v=3","gravatar_id":"","url":"https://api.github.com/users/isaacs","html_url":"https://github.com/isaacs","followers_url":"https://api.github.com/users/isaacs/followers","following_url":"https://api.github.com/users/isaacs/following{/other_user}","gists_url":"https://api.github.com/users/isaacs/gists{/gist_id}","starred_url":"https://api.github.com/users/isaacs/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/isaacs/subscriptions","organizations_url":"https://api.github.com/users/isaacs/orgs","repos_url":"https://api.github.com/users/isaacs/repos","events_url":"https://api.github.com/users/isaacs/events{/privacy}","received_events_url":"https://api.github.com/users/isaacs/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/nodejs/inclusivity/labels/question","name":"question","color":"cc317c"}],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":130,"created_at":"2015-11-10T19:54:19Z","updated_at":"2015-11-18T23:40:03Z","closed_at":"2015-11-18T23:40:03Z","body":"Node.js is a very popular project with a huge international audience.  While the API terminology is primarily in English, like most open source software projects, we accept a lot of contributions (including user-facing API design) from people of many different linguistic backgrounds.\r\n\r\nI think it's safe to assume positive intent in most cases; ie, if someone sends a PR full of inappropriate language, ok, they're a troll, and the correct action is to ban them.  But there are cases where a word choice seems perfectly reasonable to one person, but is very difficult for many others to stumble across in the codebase.  Changing these word choices after the fact is probably the right course of action, but comes at a cost of disrupting existing users of that API.\r\n\r\nAre there any processes that can be put in place to avoid situations where a word choice can be problematic/distracting/triggering/offensive to users?"}}