Skip to content

HCEP Maintainers

About

HCEP Maintainers are the people who maintain the HCEP repo and manage the #hceps Slack channel. All of the HCEP Maintainers are Hack Clubbers, either current or alumni (this include HQ/HCB staff in the list).

Responsibilities

  • Create and manage tracking issues (and possibly their corresponding discussion threads in either #meta/#hceps Slack channel or at GitHub Discussions) for each HCEP submitted.
  • Review HCEP submissions and merge them into the main branch for archival and tracking proposes.
  • Manage the #hceps Slack channel, including welcoming new members, answering questions, and enforcing the Hack Club Code of Conduct outside the Slack.
  • Review HCEP maintainer applications received through the GitHub/GitLab flow (as documented in HCEP submission flows doc) alongside inviting additional HCEP maintainers based on their activity in the #meta Slack channel.

How to add yourself here

  1. Open a PR to add yourself to this list, alongside your contact details. We recommend linking to your Hack Club Slack profile, GitHub or GitLab.com handle and email address as a minimum.
  2. Another maintainer will review your PR to check for activity within the Hack Club community as well as for Code of Conduct compliance.
  3. Once your PR is approved and merged, you will be invited into the repository as a collaborator with maintainer permission level and granted channel management permissions at the Slack channel. Admin permissions will be only given to either Hack Club HQ/HCB staff or a trusted community member (i.e. Moderation community subteam, aka Fire Department and Fraud Squad).

Retiring from being a Maintainer

If you wish to retire from your maintainer role voluntarily, please send a PR removing yourself from this list. Once merged, your maintainer permissions will be removed shortly afterwards, alongside the Channel Manager role.

We also consider you to be automatically retired if you have been inactive in the community for over six months or in case of a permanent community ban due to a major Code of Conduct violation. For inactivity, we may reach out over both Slack DMs and emails to confirm your status before proceeding with removal.

Maintainer contact details formatting/template

* Your Name Here (any project affiliations within Hack Club community or role name if HQ/HCB staff)
    * email at `user@domain.tld`
    * `@screen-name` on [Hack Club Slack](https://hackclub.enterprise.slack.com/team/UABCDE12345), `@separate-username` on [GitHub](https://github.com/username) and [GitLab.com](https://gitlab.com/username)
    * `@handle@host.domain.tld` in the Fediverse, `@user.domain.tld` in the Atmosphere

HCEP Maintainers

  • Andrei Jiroh Halili (Alumni Society Maintainer, Hack Club Community GitLab.com namespace owner)
    • email at andreijiroh@alumni.hackclub.community (Hack Club Community specific email via Alumni Society), ajhalili2006@crew.recaptime.dev (Recap Time Squad HQ specific work email address) or ajhalili2006@andreijiroh.dev (personal email address)
    • @ajhalili2006 on Hack Club Slack, GItHub, GitLab.com, sourcehut and Codeberg
    • @ajhalili2006@tilde.zone in the Fediverse or @andreijiroh.dev in the Atmosphere
    • @ajhalili2006 on most socials (i.e. Facebook/Instagram/Threads, Telegram, Discord, Twitter, Tumblr, Substack), @ajhalili2006.23 on Signal
    • andreijiroh.dev on the web
  • Evan Streams (Community Manager at Hack Club) - proposed by Andrei Jiroh Halili, pending repo invite

Former maintainers

None so far.