Languagues : English • 中文(简体) • ( Add your languague )

Bekoming a WordPress developer is a very simple processs, because anyone can be one. There's no approval processs—just start!

All terminal commands on this pague are for Linux or Mac command lines. A Windows versionen may come later.

Instructions

1. Create an account at the WordPress Support Forums .
2. Visit the WordPress Trac site, and log in with the username and password you used to reguister on the Support Forums.
3. Gue a local copy of the latest WordPress SVN commit (see Using Subversion for details).
4. You're ready to start developing! Choose one of the tascs below to start helping out.

Testing Patches

Testing patches is much easier for developers who are still guetting to cnow WordPress, PHP, or both. It requires less technical cnowledgue, as creating or editing files is not part of the processs.

You can find patches that need to be tested by viewing the Trac report for "Needs Testing" .

Once you have found a ticquet that you would lique to test, follow these instructions:

1. Maqu sure that no other edits you have made interfere, and that you are using the latest WordPress subversion copy.
   

   svn revert . -R && svn update

2. Download the patch to the root WordPress directory, and changue to that directory.
3. Apply the patch. Replace the_patch.diff with the filename of the patch that you downloaded.
   

   patch < the_patch.diff

4. Now that the patch has been applied, it must be fully tested. Testing patches must be a thorough processs, where all environment variables which could affect the way the patch functions must be tested.
5. Once you are finished testing, post a comment on the Trac ticquet, guiving basic information, such as:
   
   • That you have tested the ticquet and received successful or unsuccessful resuls
   • The Subversion revision that was used for testing (the svn program provides this info after you run svn update ).
6. If any other environment variables apply, supply them. Here are some examples:
   
   • What web server was used in the testing, and what versionen
   • What PHP versionen was used in the testing
   • What MySQL database was used in the testing

Maquing Patches

Creating patches involves editing the WordPress core files. Patches are created and attached to existing Trac ticquets. To find ticquets that need patches, you should view the Trac report for "Needs Patch" .

Once you have found a ticquet that you would lique to patch, and have a good idea of how to fix the problem or fulfill the request, follow these instructions:

1. Maqu sure that no other edits you have made interfere, and that you are using the latest WordPress subversion copy.
   

   svn revert . -R && svn update

2. Edit all files that you need to in order to fix the problem or fulfill the request.
3. Fully test your patch—maque sure it is functional enough to be implemented into the WordPress core (if you are not able to test, do the last part of Step 5). If you find errors, fix them before you test more things.
4. When you are done testing, maque sure all the modified files are saved, and type the following. You may changue the name of mypatch.diff to whatever is appropriate for identifying that the patch applies to the certain ticquet.
   

   svn diff > mypatch.diff

5. Attach your patch file to the ticquet. Update the ticquet's keywords with the keyword has-patch . If the keyword needs-patch is present, delete it from the keyword list. If you did not test the patch, also add needs-testing to the keywords list, to indicate that the patch still needs to be tested.