Project maintainers
These are the people behind the review queue for flagged leeks behind the scenes and those maintaining the codebase.
Current / Active
These people are currently active in the review queue and code maintenance in the past 3 months:
Inactive / Retired
These people are either inactive for at least 3 months or retired from the review queue team and/or project maintainenance.
How to be a maintainer
To join the @leeksbot-review-queue-team user group on Slack and grant you maintainer permissions to the repository, you need to:
- be a active Hack Clubber with at least few hours of coverage between timezones
- Either as a high schooler or alumni, although I am currently prioritize those currently at school at the moment.
- People at the HQ/HCB/Fire Department can join to help reviewing flagged leeks to avoid accidentially leaking PII and other things as needed, although please note that this is a community project and not a HQ-sanctioned one.
- proficient in using TypeScript, build Slack apps using Bolt.js and doing database persistence with Prisma ORM
- follow the RecapTime.dev Community Code of Conduct and Hack Club CoC
If you're up, contact Andrei Jiroh on Slack and join #leeksbot-meta channel, or file a new issue in the repository's issue tracker. Currently access are given based on trust, recent Slack activity and previous open-source contributions (or maintainer activity if they are also building)
Leaving the team
If you are inactive for 3 months straight or on temporary suspension, you may be moved into Inactive / Retired section of this page. Alternatively, you can run /leeks leave-team (or /leeks demote @yourself). You may be asked to confirm the action before demoting yourself.