Welcome to the MetaMetaMeta 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. Team!
The Meta team is responsible for maintaining and managing WordPress.orgWordPress.orgThe 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/ websites. Our work is mostly done on the meta trac. If you see a bug, file a ticket!
If you need changes made to the WordPress GitHubGitHubGitHub 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 be the repository owner. https://github.com/ organization, please create a ticket on Meta Trac.
When new projects start up, or existing projects move from their external GitHub organization to the WordPress org, some repository administration is required.
When moving repositories from a different organization to WordPress, you will need to be an owner of that organization, as well as the WordPress organization. When moving repositories from GitHub user accounts, they will need to transfer the repository to your account, then you can transfer it to the WordPress Organization.
Once the repository is under the WordPress organization, you should create a new team, or give an existing team write access. Project leads should have Maintainer permission on the team, allowing them to add other users to that team.
Before a user can be added to a team, they need to be a member of the WordPress organization. Users can only be added to the organization by owners.
Every project will likely have ways they prefer to manage when users are added to their team (for example, Gutenberg). You should generally only need to add a user to the WordPress organization when requested by a project lead.
Apps should be evaluated and added sparingly, on a case-by-case basis. They often require access to private repositories, so the app developer should be highly trustworthy.
Additionally, app behavior should be be evaluated for a project with the scale, scope and reach of WordPress. Apps that may work for small projects may be overly spammy or complex for WordPress.