MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. commit access lets you commit to the repositories behind WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ and deployDeploy Launching code from a local development environment to the production web server, so that it’s available to visitors. those changes yourself. It is granted to contributors with a track record on Meta, and it is granted per-area rather than all at once.
What you get
| Access | What it is for |
|---|---|
RW to meta.svn | Committing to the WordPress.org sites and their plugins and themes |
RW to dotorg.svn (sub-path as required) | Committing to WordPress.org itself |
| WordPress.org Meta Team on GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged by the repository owner. https://github.com/ | Write access to the relevant GitHub repositories, so you can merge PRs |
| Meta committer channels on SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/ | Where deploys and breakage get coordinated |
| A sandbox, if you do not have one | Testing and deployingDeploy Launching code from a local development environment to the production web server, so that it’s available to visitors. |
Super-admin on the WordPress.org network is optional and is not granted by default.
How to ask
There is no application form. Commit access follows from contribution: work on Meta tickets and pull requests, be around in #meta on Make WordPress Slack, and raise it there or with an existing Meta committer when the work you are doing is being held up by not having it.
For access to a specific area, ask an existing Meta committer directly. For anything outside SVNSVN Apache Subversion (often abbreviated SVN, after its command name svn) is a software versioning and revision control system. Software developers use Subversion to maintain current and historical versions of files such as source code, web pages, and documentation. Its goal is to be a mostly compatible successor to the widely used Concurrent Versions System (CVS). WordPress core and the wordpress.org released code are all centrally managed through SVN. https://subversion.apache.org/. and GitHub — server access, tooling, infrastructure — ask the Systems team.
What is expected of you
- Two-factor authentication on your WordPress.org account. This is required, not encouraged. See Configuring Two-Factor Authentication.
- An SVN-specific password, generated from your profile rather than reusing your account password. See Subversion Access.
- Prefer pull requests for repositories on GitHub, even when you are able to merge your own. Merging your own PR is fine when the change is small or urgent.
- Be available after you deploy. A deploy ships everyone’s changes, not only yours — see Deploying WordPress.org.
A useful setup step
SVN commits are attributed to your wordpress.org commit identity, which GitHub does not recognise by default. Adding <your-username>@git.wordpress.org to your GitHub email list makes GitHub attribute synced meta.svn commits to your account.
When access is removed
When someone steps back from Meta, their SVN access, GitHub team membership, and committer channel membership are all removed. This is routine, not a judgement, and access can be restored if they return.
