If you've become familiar with the project and feel confident and interested in the participating in it, then read the following guidelines.

Joining the phpDays team

• leave your request to join the team as a comment on the Discussions page or send it to project support group
• in your message state a role you would like to take on (php developer, web designer, documentation translator, typesetter, JavaScript developer) and include your Gmail address (your Gmail username is enough)
• after some consideration you'll receive an email with our decision about including you in the project (if you don't get the response in three days, send your request again)
• if everything goes well, you'll become a member of the project and will be able to do more than a non-member can (you'll be able to change the project's code, documentation and tasks)
• also you will be added to the project's member list (don't forget to add this link to your resume)

General Information about the Site

• Downloads - Download page, where the project's working copies are available, intended for the end user
• Wiki - project's documentation
• Issues - list of issues and tasks
• Source - information about the project's SVN repository and change log history

Uploading the Project's working copy

• download and install an SVN client to work with the project's files
• download a project's working copy (for more information see Checkout)
• if you haven't worked with Subversion before, take your time to learn it

Guidelines for Applying Changes (SVN commit)

For comments follow the format listed below

• Fix #1234: The name of the bug - for a fix of the error number 1234. If the bug is not in the Issues, then you should add the issue first and only then make a SVN commit
• write each bug/issue in a separate line. Put a dot at the end of line.

Test Yourself

Set up PHPUnit. This will allow you to create unit tests to ensure that a new fix in code will not break something else. Only after this should you run SVN commit.

Write Better Code

Read about the coding style adopted in our project. Following uniform style allows all developers to communicate in a single, comprehensible language.