Add some more policies, including contributing guidelines

CODEOWNERS

@@ -1,6 +1,6 @@
+# defaults to the crew for review
+* @recaptime-dev/squad
+
 # team bios
 # add yours using the following template: team/your-username-here.md @username
 team/ajhalili2006.md @ajhalili2006
-
-# everything else
-* @recaptime-dev/squad

CODE_OF_CONDUCT.md

@@ -0,0 +1,146 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, caste, color, religion, or sexual
+identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall
+  community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or advances of
+  any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address,
+  without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+<abuse@recaptime.eu.org> or <modteam@recaptime.eu.org>.
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of
+actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or permanent
+ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the
+community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.1, available at
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at
+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
+[https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations
+
+## Appendix
+
+### The `abuse@` and `modteam@` aliases
+
+While you can email CCoC violations to our abuse email alias, the scope of the abuse email alias covers more than CCoC violations and content needs moderator review and it's our legal team that review them.
+
+Please note that email to the `modteam@recaptime.eu.org` alias will be forwarded to all of our community moderation team, alongside the leadership team (also known as `@recaptime-dev/squad-leads`) for assistance in case of large backlog.
+
+### Violations affecting other communities (or coming from other communities)
+
+If we receive a violation report that either affects or comes from other communities, we have limited moderation powers over what's happening outside our spaces, either public or within internal channels.
+
+If that's the case, a member from our moderation team will simply forward you case on your behalf if our bandwidth allows.

CONTRIBUTING.md

@@ -0,0 +1,38 @@
+# Contributing guidelines for team profiles
+
+## Linux DCO
+
+By contributing patches, you agree to the [Linux DCO](https://developercertificate.org/) and sign-off your commits (`git commit -s` or `git commit --signoff`).
+
+**For community contributors**: We do not require to sign our CLA in most projects (like this), although if you did, we'll assume your CLA signature will make your agreement to DCO legally binding.
+
+## Updating/adding team profiles
+
+> **Note**: You should add your team profile in this repo and not in [`gh:recaptime-dev/website-next`](https://github.com/recaptime-dev/website-next), due to how we setup CI for one-way synchorization.
+
+For new members during onboarding, create your own team profile by [copying the template file] and fill in with your own.
+
+```shell
+# branch off if you have direct push access to the repo or fork to personal namespace
+gh repo clone recaptime-dev/squad # with GitHub CLI
+glab repo clone https://mau.dev/recaptime-dev/squad/gitlab-profile # with GitLab CLI
+# option A: branch off (you can also branch off on your fork to keep things seperate
+# from your own main branch)
+git switch -c your-username/add-team-profile
+# option B: fork via existing copy
+gh repo fork recaptime-dev/squad --default-branch-only --remote
+glab repo fork recaptime-dev/squad --remote
+
+# first copy the template file into an new markdown file
+cp team/template.md team/<your-github-username-in-lowercase>.md
+
+# edit with your own details
+$EDITOR team/<your-github-username-in-lowercase>.md
+
+# make sure to protect your team profile file via CODEOWNERS
+$EDITOR CODEOWNERS
+
+# stage, sign-off and send a patch
+git commit --signoff team/<your-github-username-in-lowercase>.md
+git push origin your-username/add-team-profile
+```

README.md

@@ -16,14 +16,16 @@ _Last updated as of 2023-06-28_
 * **Currently active**: @ajhalili2006
 * **On break/vacation**: N/A
 * **Currently/recently offboarded**: N/A
-* **Email**: `squad [at] crew dot recaptime dot eu dot org`
+* **Email**: `squad [at] crew dot recaptime dot eu dot org` [^2]
+
+[^2]: This will actually forward your email to everybody at the team, excluding any community vounteers unless opted in.
 
 ## Quick links
 
-* **Chat**: [Matrix space](https://go.recaptime.eu.org/matrix/staff), [Keybase]()
-* **In other code forges**: [sourcehut](https://sr.ht/~recaptime-dev), [Jetbrains Space](https://recaptime.jetbrains.space)
+* **Chat**: [Matrix space](https://matrix.to/#/#community.recaptime.dev:envs.net), [Keybase](https://keybase.io/recaptimedev), [Discord]( https://discord.gg/5dURUcM)
+* **In other code forges**: [sourcehut](https://sr.ht/~recaptime-dev), [Jetbrains Space](https://recaptime.jetbrains.space), [GitHub](https://github.com/recaptime-dev)
 * [**Squad Wiki**](https://squad.lorebooks.eu.org) ([internal version - use your Internal SSO account to access](https://internal.squad.lorebooks.eu.org))
-* Community Code of Conduct and other policies
+* **Community Code of Conduct and other policies**: <https://policies.recaptime.eu.org>
 
 ## How to mention the crew?
 

SECURITY.md

@@ -0,0 +1,9 @@
+# Security Policy
+
+For more information about our security policy across Recap Time Squad and our affliated organizations, please see <https://recaptime.eu.org/security> for details.
+
+Contact details can be found at <https://recaptime.eu.org/.well-known/security.txt>. The rest of this security policy details about our guidelines within this project.
+
+## Specifics to this project
+
+We do not have an security policy specific to team profiles like this within the organization, so the regular security policies for squad members apply.