This does not restrict you from being able to contribute. See "Process for Implementing Changes to the Code" below for instructions on volunteering. With enough dedication, you can earn a seat on the core team as well!
Process for Implementing Changes to the Code
Here's the process that we'd like for you to follow. This process is in place mainly to encourage everyone to communicate openly. This gives us the opportunity to have a great peer-review process, which will result in quality. Who doesn't like quality?
Open an issue in the issue tracker, outlining the changes or additions that you would like to make.
A member of the core team will review your submission and leave feedback if necessary.
Once the core team member is satisfied with the scope of the issue, they will indicate so in a comment to the issue. This is your green light to start working. Get to coding, grasshopper!
Need help or running across any issues while coding? Run it by the Google Group. They all have opinions and love to let you know all about them.
When you submit a question on Google Group about one of these guides, please put the name of the guide as part of the subject.
When you have implemented your enhancement or change, use your Git repository to create a pull request with your changes.
You should annotate your commits with the issue number as #55 if the code issue is 55
A core team will review it and post any necessary feedback in the issue tracker.
Once everything is resolved, a core team member will pull your commit into the Git repository.
If needed, open an issue in the issue tracker to have the additions and changes in your revision documented. You may claim the issue if you'd like to do this, but it's entirely your choice.