Welcome! This is our internal repo we use for running Hack Club, warts and all. We're excited to have you involved.

Links:

• GitHub Teams - How we manage our GitHub teams
• Protocols
  • Hiring
  • Club leader onboarding
  • Staff onboarding
• Styleguides
  • Markdown
  • English
  • CSS
• Other directories
  • Applications
  • Contracts
  • Fundraising
  • Ideas
  • Labs
  • Logos
  • Meeting notes
  • Positions
  • Scripts
  • Updates
  • The Hack Series

Vision: A future where everyone is a hacker.

Mission: To provide access to a community that embodies the hacker ethos to every student through coding clubs.

See GOALS.md.

These are the people who are officially part of the organization, but we want you involved as well!

We use ZenHub with GitHub Issues to manage our team workflow.

Our board has the following columns:

• New Issues - Issues that have not been categorized into a column yet. This is the default location for new issues.
• Ideas - Issues that we're not actively working on as a team, but may decide to prioritize in the future.
• Backlog - Issues that we're actively planning on addressing, but aren't currently high priority.
• Todo - Issues that are in our immediate team queue.
• In Progress - Issues that are currently being worked on by a member of the team. When a team member begins working on an issue, they should drag it into In Progress.
• Review - The deliverable for the task has been submitted and is currently being reviewed by another member of the team. This is usually in the form of a pull request.

*Pull requests should be put next to their corresponding issue on the board. If there is not a corresponding issue, they should flow through the board like an issue.

If you'd like to reach all of us, please send an email to [email protected] :-).

In the LICENSE file (MIT, tl;dr).