GitHub Issue Moderators, or “issue mods”, are volunteers who have the ability to close issues and accept or deny pull requests.
Navigate to Becoming an Issue Mod if you are interested in becoming an Issue Moderator on GitHub.
Issue Mods have two primary responsibilities:
Free Code Camp is an active open source project. We get many tens of issues a day, all of which need to be triaged and labeled.
There are several general classes of Issues:
If it’s a simple change to an existing challenge, flag as
help wanted and, optionally, as
first-timers-only. Use other tags as appropriate.
If the issue is more significant, flag as
If there is a question as to the proper course of action on an issue, feel free to tag @FreeCodeCamp/issue-moderators to give an opinion. Flag as
Pull Requests (PRs) are how contributors to Free Code Camp submit changes to the repository for consideration. It is important that these PRs are properly formatted and undergo thorough Quality Assurance Testing prior to being merged.
PRs must meet the following requirements:
closes #XXXXfor each issue number closed
If the issue does not meet one or more of these requirements, note the deficiencies in a comment and/or highlight lines. New Contributors may be referred to the HelpContributors Chat room. At at the Mod’s discretion the issue may be closed.
Assuming that the basic requirements for the PR are met, all PRs should undergo some level of Quality Assurance testing. The most basic QA is to simply checkout the PR on a local copy of the site and test the changed functionality. Be sure to read through the code changes and understand what the potential side effects are. Exercise code and corner cases. Be sure to try both negative and positive test cases.
If there is any doubt about the functionality, ask for the @FreeCodeCamp/issue-moderators to also take look.
For larger PRs, tag in @BerkeleyTrue. In some cases it may make sense to test on the beta site.
PRs which change the underlying function of the site or make non-trivial changes to the UI or UX of the site should be approved by @BerkeleyTrue or @QuincyLarson. If you have any doubt, tag them in a comment and/or draw their attention to the PR via Gitter Chat.
Though you will have write access to Free Code Camp’s repository, you should never write directly to the Free Code Camp repository. All code should enter Free Code Camp’s codebase in the form of a pull request.
Note: although you will have write access to the main repository, you should not accept your own PRs should you make one. They will still need to be QA-ed by another issue mod just like any other PR.
In order to become an issue mod, you must first prove your helpfulness by leaving useful comments on outstanding issues, and submitting pull requests of your own to fix these issues.
If you’ve been doing these things, and want the additional power/responsibility that comes with helping Free Code Camp as an issue mod, please contact @BerkeleyTrue in Gitter.
If you are approved, we will add you to a GitHub Team, Issue mods.
The number of issue moderators will always remain small due to the nature of Github permissions.
Please note that we will frequently remove issue mods whom we think are inactive. If you are removed, please do not take this personally - we can add you back to the team, just message us and let us know you’re still active.