diff options
| -rw-r--r-- | guide/src/SUMMARY.md | 2 | ||||
| -rw-r--r-- | guide/src/code_of_conduct.md | 84 | ||||
| -rw-r--r-- | guide/src/policies.md | 44 | ||||
| -rw-r--r-- | guide/src/privacy_policy.md | 35 | ||||
| -rw-r--r-- | guide/src/welcome.md | 4 |
5 files changed, 127 insertions, 42 deletions
diff --git a/guide/src/SUMMARY.md b/guide/src/SUMMARY.md index 2a986dcb..4b7d326f 100644 --- a/guide/src/SUMMARY.md +++ b/guide/src/SUMMARY.md @@ -23,6 +23,8 @@ - [Cookbook](./cookbook.md) - [Software Contributions](./sw_contribute.md) - [Policies](./policies.md) + - [Code of Conduct](./code_of_conduct.md) + - [Privacy](./privacy_policy.md) [Bibliography](./bibliography.md) diff --git a/guide/src/code_of_conduct.md b/guide/src/code_of_conduct.md new file mode 100644 index 00000000..37816ea8 --- /dev/null +++ b/guide/src/code_of_conduct.md @@ -0,0 +1,84 @@ + +# Fatcat Code of Conduct + +In this early stage of the project, this document is a work in progress. In +particular there is no moderation team or policy for responding to concerns in +online discussions. However, it is important to clarify norms and expectations +as early as possible. + +To contact the Internet Archive privately about conduct concerns or to report +unacceptable behavior, you can email <ethics@archive.org>. + +## Overview + +- We are committed to providing a friendly, safe and welcoming environment for + all, regardless of level of experience, gender identity and expression, + sexual orientation, disability, personal appearance, body size, race, + ethnicity, age, religion, nationality, or other similar characteristic. + +- Please avoid using overtly sexual aliases or other nicknames that might + detract from a friendly, safe and welcoming environment for all. + +- Please be kind and courteous. There’s no need to be mean or rude. + +- Respect that people have differences of opinion and that every design or + implementation choice carries a trade-off and numerous costs. There is seldom + a right answer. + +- Please keep unstructured critique to a minimum. If you have solid ideas you + want to experiment with, make a fork and see how it works. + +- This Code of Conduct applies to all online project spaces (including the + catalog itself, code repositories, mailing lists, chat rooms, forums, and + comment threads), as well as any physical spaces such as conference + gatherings or meetups. + +- All participants are expected to respect this code, irregardless of their + position or record of contributions to the project. + +## Unacceptable behavior + +The following types of behavior are unacceptable in the Fatcat project, both +online and in-person, and constitute code of conduct violations. + +### Abusive behavior + +- **Harassment:** including offensive verbal comments related to gender, sexual + orientation, disability, physical appearance, body size, race, or religion, + as well as sexual images in public spaces, deliberate intimidation, stalking, + following, harassing photography or recording, inappropriate physical + contact, and unwelcome sexual or romantic attention. + +- **Threats:** threatening someone physically or verbally. For example, + threatening to publicize sensitive information about someone’s personal life. + +### Unwelcoming behavior + +- **Blatant-isms:** saying things that are explicitly racist, sexist, + homophobic, etc. For example, arguing that some people are less intelligent + because of their gender, race or religion. Subtle -isms and small mistakes + made in conversation are not code of conduct violations. However, repeating + something after it has been pointed out to you that you broke a social rule, + or antagonizing or arguing with someone who has pointed out your subtle -ism + is considered unwelcoming behavior, and is not allowed in the project. + +- **Maliciousness towards other participants:** deliberately attempting to make + others feel bad, name-calling, singling out others for derision or exclusion. + For example, telling someone they’re not a real programmer or that they don’t + belong in the project. + +- **Being especially unpleasant:** for example, if we’ve received reports from + multiple Recursers or faculty of annoying, rude, or especially distracting + behavior. + +- Spamming, trolling, flaming, baiting or other attention-stealing behavior is + not welcome. + +## About This Document + +The Fatcat Code of Conduct is inspired by, and derived from: + +- [Recurse Center Code of Conduct](https://www.recurse.com/code-of-conduct) +- [Rust Language Code of Conduct](https://www.rust-lang.org/policies/code-of-conduct) +- [18f Code of Conduct](https://18f.gsa.gov/code-of-conduct/) + diff --git a/guide/src/policies.md b/guide/src/policies.md index 3816f876..e51594b6 100644 --- a/guide/src/policies.md +++ b/guide/src/policies.md @@ -5,10 +5,8 @@ of contributors to the project grows. It is important to have some policies as a starting point, but also important not to set these policies in stone until they have been reviewed. -## Social Norms and Conduct - -Contributors (editors and software developers) are expected to treat each other -excellently, to assume good intentions, and to participate constructively. +See also the [Code of Conduct](./code_of_conduct.html) and +[Privacy Policy](./privacy_policy.html). ## Metadata Licensing @@ -60,43 +58,9 @@ Attribution license. ## Software Licensing -The Fatcat software project licensing policy is to adopt strong copyleft +The Fatcat software project licensing policy is to adopt *strong copyleft* licenses for server software (where the majority of software development takes -place), and permissive licenses for client library and bot framework software, +place), *permissive* licenses for client library and bot framework software, and CC-0 (public grant) licensing for declarative interface specifications (such as SQL schemas and REST API specifications). -## Privacy Policy - -*It is important to note that this section is currently aspirational: the -servers hosting early deployments of Fatcat are largely in a defaults -configuration and have not been audited to ensure that these guidelines are -being followed.* - -It is a goal for Fatcat to conduct as little surveillance of reader and editor -behavior and activities as possible. In practical terms, this means minimizing -the overall amount of logging and collection of identifying information. This -is in contrast to *submitted edit content*, which is captured, preserved, and -republished as widely as possible. - -The general intention is to: - -- not use third-party tracking (via extract browser-side requests or - javascript) -- collect aggregate *metrics* (overall hit numbers), but not *log* individual - interactions ("this IP visited this page at this time") - -Exceptions will likely be made: - -- temporary caching of IP addresses may be necessary to implement rate-limiting - and debug traffic spikes -- exception logging, abuse detection, and other exceptional - -Some uncertain areas of privacy include: - -- should third-party authentication identities be linked to editor ids? what - about the specific case of ORCID if used for login? -- what about discussion and comments on edits? should conversations be included - in full history dumps? should editors be allowed to update or remove - comments? - diff --git a/guide/src/privacy_policy.md b/guide/src/privacy_policy.md new file mode 100644 index 00000000..05136f97 --- /dev/null +++ b/guide/src/privacy_policy.md @@ -0,0 +1,35 @@ + +## Privacy Policy + +*It is important to note that this section is currently aspirational: the +servers hosting early deployments of Fatcat are largely in a defaults +configuration and have not been audited to ensure that these guidelines are +being followed.* + +It is a goal for Fatcat to conduct as little surveillance of reader and editor +behavior and activities as possible. In practical terms, this means minimizing +the overall amount of logging and collection of identifying information. This +is in contrast to *submitted edit content*, which is captured, preserved, and +republished as widely as possible. + +The general intention is to: + +- not use third-party tracking (via extract browser-side requests or + javascript) +- collect aggregate *metrics* (overall hit numbers), but not *log* individual + interactions ("this IP visited this page at this time") + +Exceptions will likely be made: + +- temporary caching of IP addresses may be necessary to implement rate-limiting + and debug traffic spikes +- exception logging, abuse detection, and other exceptional + +Some uncertain areas of privacy include: + +- should third-party authentication identities be linked to editor ids? what + about the specific case of ORCID if used for login? +- what about discussion and comments on edits? should conversations be included + in full history dumps? should editors be allowed to update or remove + comments? + diff --git a/guide/src/welcome.md b/guide/src/welcome.md index c3c736da..6ddcfd8a 100644 --- a/guide/src/welcome.md +++ b/guide/src/welcome.md @@ -1,6 +1,6 @@ -# Welcome, Welcome, Welcome! +# Welcome! -This guide you are reading contains: +The guide you are reading contains: - a **[high-level introduction](./overview.md)** to the Fatcat catalog and software |