Welcome to the hub for squad members

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, GitHub

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

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, Keybase, Discord
• In other code forges: sourcehut, Jetbrains Space, GitHub
• Squad Wiki (internal version - use your Internal SSO account to access)
• Community Code of Conduct and other policies: https://policies.recaptime.eu.org

How to mention the crew?

Note

: These also apply to anyone outside Recap Time Squad.

• Remember that tagging @recaptime-dev/squad will trigger email notifications to ALL users under the subgroup, which might overwelm things on the backend easily.² 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

---

1. This will actually forward your email to everybody at the team, excluding any community vounteers unless opted in. ↩︎

2. 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. ↩︎