recaptime-dev/meta
2
0
Fork 0
mirror of https://gitlab.com/recaptime-dev/squad/meta.git synced 2025-06-01 18:49:30 +00:00
Code Issues Releases Packages Activity
The meta repo and issue tracker for Recap Time Squad Crew and the organization. https://gitlab.com/recaptime-dev/squad/meta/-/issues
3 commits 1 branch 0 tags 1.2 MiB
Find a file
multifandom hellscapes 7fda32a739
Add team bios and some reply templates 
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>
2023-08-12 01:26:20 +08:00
team Add team bios and some reply templates 2023-08-12 01:26:20 +08:00
templates/replies Add team bios and some reply templates 2023-08-12 01:26:20 +08:00
CODEOWNERS Add team bios and some reply templates 2023-08-12 01:26:20 +08:00
README.md Add team bios and some reply templates 2023-08-12 01:26:20 +08:00

README.md

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

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.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

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