mirror of
https://gitlab.com/recaptime-dev/squad/meta.git
synced 2025-06-05 04:29:30 +00:00
33 lines
1.6 KiB
Markdown
33 lines
1.6 KiB
Markdown
# Welcome to the hub for squad members
|
|
|
|
Most of the squad members have maintainer access to most of the repositories in both Mauiunm GitLab instance (here) and GitLab SaaS, alongside GitHub.
|
|
|
|
## Roaster / details
|
|
|
|
* **Squad Leads (Executive Team)** (@RecapTime/squad-leads): @ajhalili2006
|
|
* **Recently onboarded crew**: N/A
|
|
* **Currently active**: @ajhalili2006
|
|
* **On break/vacation**: N/A
|
|
* **Currently/recently offboarded**: N/A
|
|
* **Email**: `squad [at] crew dot recaptime dot eu dot org`
|
|
|
|
## How to mention the crew?
|
|
|
|
> **Note**: These also apply to anyone outside Recap Time Squad.
|
|
|
|
* Remember that tagging `@RecapTime/squad` will trigger email notifications to ALL users under the subgroup, which might overwelm things on the backend easily.[^1] We recommend directly mentioning the individual members themselves.
|
|
* Only tag everyone in case of:
|
|
* emergency async meetings, especially as required by @RecapTime/legal team.
|
|
* important org-wide announcements that might affect the operations of the organization
|
|
|
|
## Quick links
|
|
|
|
* **Chat**: [Matrix space](https://go.recaptime.eu.org/matrix/staff)
|
|
* **In other code forges**: [sourcehut](https://sr.ht/~recaptime-dev), [Jetbrains Space](https://recaptime.jetbrains.space)
|
|
|
|
## Basics
|
|
|
|
* [**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
|
|
|
|
[^1]: That mistake was happened in GitLab SaaS at <https://gitlab.com/gitlab-org/gitlab/-/merge_requests/19861#note_242645866>, but @ajhalili2006 might forgot what issue is it for that within GitLab team's namespace.
|