recaptime-dev/meta
2
0
Fork 0
mirror of https://gitlab.com/recaptime-dev/squad/meta.git synced 2025-06-05 04:29:30 +00:00
Code Issues Releases Packages Activity

Add team bios and some reply templates

Browse source 
Details: https://github.com/recaptime-dev/squad/pulls/1

Signed-off-by: multifandom hellscapes <multifandom-multiverse@andreijiroh.eu.org>
Reviewed-by: @ajhalili2006 <ajhalili2006@crew.recaptime.eu.org>
This commit is contained in:
multifandom hellscapes 2023-08-12 01:26:20 +08:00 • committed by GitHub
parent c31a12dbf0
commit 7fda32a739
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
6 changed files with 80 additions and 13 deletions
Download patch file Download diff file Expand all files Collapse all files

30
README.md
View file

@ -1,33 +1,37 @@
# 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.
Most of the squad members have developer to maintainer access (depending on the department they're currently in)
to most of the repositories in both Mauiunm GitLab instance (here) and GitLab SaaS, alongside GitHub.
**Mirrors**: [canonical repo at mau.dev](https://mau.dev/recaptime-dev/squad/gitlab-readme), [GitHub](https://github.com/recaptime-dev/squad)
**Issue tracker**: <https://mau.dev/recaptime-dev/squad/issue-tracker/issues> or <https://todo.sr.ht/~recaptime-dev/squad-suggestion-box> (note that Issues are disabled on mirrors)
## Roaster / details
* **Squad Leads (Executive Team)** (@RecapTime/squad-leads): @ajhalili2006
_Last updated as of 2023-06-28_
* **Squad Leads (Executive Team)** (@recaptime-dev/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`
## 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)
* [**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
## 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.
* Remember that tagging `@recaptime-dev/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.