update coc (#2090)

* update coc

* improve wording

* point to coc doc in contributing doc

* swap-out ancap for capitalist

* fix git relative path

* ACTUALLY fix the relative link

* fix spelling of abhorrent
This commit is contained in:
kim 2023-08-09 14:47:03 +01:00 committed by GitHub
parent e5c7501850
commit 31a215849e
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 6 additions and 4 deletions

View file

@ -4,6 +4,8 @@ This document is currently a stub.
In lieu of a fuller code of conduct, here are a few ground rules.
1. We *DO NOT ACCEPT* PRs from right-wingers, Nazis, transphobes, homophobes, racists, harassers, abusers, white-supremacists, misogynists, tech-bros of questionable ethics. If that's you, politely fuck off somewhere else.
2. Any PR that moves GoToSocial in the direction of surveillance capitalism or other bad fediverse behavior will be rejected.
3. Don't spam the general chat too hard.
1. We are not interested in input from right-wingers, nazis, fascists, transphobes, homophobes, racists, harassers, abusers, white-supremacists, misogynists or capitalists. This list is NOT exhaustive. Input includes PRs, issues, and any other communication. Be gone!
2. We will not accept changes (code or otherwise) created with the aid of "AI" tooling. "AI" models are trained at the expense of underpaid workers filtering inputs of abhorrent content, and does not respect the owners of input content. Ethically, it sucks.
3. We will not accept changes (code or otherwise) that move GoToSocial toward enterprise / surveillance / other toxic capitalist pursuits.
4. We will not accept changes (code or otherwise) that encourage toxic behaviour on social media. This is obviously subject to debate, as humanity as a whole is still figuring out how to safely engage in social media.
5. No spam!

View file

@ -61,7 +61,7 @@ We tend to prioritize feature requests related to accessibility, fedi interopera
We welcome pull requests from new and existing contributors, with the following provisos:
- You have read and agree to our Code of Conduct.
- You have read and agree to our [Code of Conduct](./CODE_OF_CONDUCT.md).
- The pull request addresses an existing issue or bug (please link to the relevant issue in your pull request), or is related to documentation.
- If your pull request introduces significant new code paths, you are willing to do some maintenance work on those code paths, and address bugs. We do not appreciate drive-by pull requests that introduce a significant maintenance burden!
- The pull request is of decent quality. We are a small team and unfortunately we don't have a lot of time to help shepherd pull requests, or help with basic coding questions. If you're unsure, don't bite off more than you can chew: start with a small feature or bugfix for your first PR, and work your way up.