The WordPress coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. development team builds WordPress! Follow this site for general updates, status reports, and the occasional code debate. There’s lots of ways to contribute:
Found a bugbugA bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority.?Create a ticket in our bug tracker.
We use Slack for real-time communication. Contributors live all over the world, so there are discussions happening at all hours of the day.
Our core development meetings are every Wednesday at 05:00 UTC and 20:00 UTC in the #core channel on Slack. Anyone can join and participate or listen in!
Welcome to being a committercommitterA developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component.! Here are some things you should know:
Make sure you have a strong password: it should be long, random, and stored in the password manager of your choice.
Make sure you have two-factor auth enabled for GitHubGitHubGitHub is a website that offers online implementation of git repositories that can 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/, SlackSlackSlack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/., and the email account associated with your w.org account. It’s also a very good idea to enable it for any service you use, since hackers will often leverage access to a low priority account to gain access to a high priority account.
Join the #coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress.-committers channel on Slack. This channel is for onboarding and questions from committers about the act of committing, tips and tricks for SVNSVNSubversion, the popular version control system (VCS) by the Apache project, used by WordPress to manage changes to its codebase., etc. You’re welcome and encouraged to ask here whenever you have a question about committing (e.g., SVN syntax, backports, etc). Anything that is relevant to non-committers (e.g., whether or not a patchpatchA special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. is ready for commit, project philosophy, proposals, etc) should still take place in #core to avoid excluding other contributors.
Please add [email protected] (e.g.[email protected]) to your GitHub account: https://github.com/settings/emails . This will allow the new GitHub mirror (https://github.com/WordPress/wordpress-develop) to correctly attribute your commits. GitHub will try to send a verification email, but it won’t be delivered. There’s no need to verify this email address for commit attribution purposes.
Please ask a relevant committer to peer-review your first few prospective patches and commit messages before you commit them. This serves as a safety check to make sure you know what to look out for before you actually commit. It also gives you a chance to ask any questions you have about process, standards, norms, etc.
It can also be a good idea to ask for peer-review from another committer whenever you have any doubts about a patch, especially if you’re committing outside an area that you normally work on.
Tasks to add a committer
Ensure the committer has completed the above steps.
On a 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/ Sandbox, add them to the following lists:
/home/svn/etc/develop.svn.wordpress.org in DeployDeployLaunching code from a local development environment to the production web server, so that it's available to visitors. SVN
$committers in .config/capes.php
wpTracContributorLabels in the Trac SVN file templates/core/site-specific.html