diff options
Diffstat (limited to 'guide/src/policies.md')
| -rw-r--r-- | guide/src/policies.md | 44 |
1 files changed, 4 insertions, 40 deletions
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? - |