Regardless of your expertise, there are many ways that you can contribute to the WebM Project. You don't have to be a codec expert, and some tasks don't even involve writing code.
If you specifically want to work on improving libvpx performance, the Contributor's Guide should be your first stop. It includes overview information on setting-up, and test scripts for evaluating the effects of your code changes before submitting.
The Contributor's Guide is a public project in its own right. Feel free to submit additions and improvements.
The WebM project is young, and the more help we can get from developers like you, the faster we can improve video on the web. This is a great opportunity to get your code running on millions of computers! See our guides on patch submissions, code reviews, and coding conventions.
Developers with a long history of submitting high-quality patches, exercising good technical judgement, and who have made significant technical contributions may be invited to become an approver. Approvers decide whether to include or exclude a change during the code-review process.
Something not working right? Can we do better? The easiest contribution you can make is to let us know. Our preference is that you report the bug first to webm-discuss so that the community can provide some initial support for common issues.
We track reported issues in our issue tracker. One way you can help is by trying to reproduce new bugs, verifying that old bugs still exist, and providing additional details on issues that affect you. Update the issues as you go, so everyone can share in what you've learned.
Share your experiences with the producing and deploying VP8 video on the webm-discuss mailing list. Getting the best video quality can be complicated, and we're working hard to change that. Share your tips and best practices on webm-discuss, regardless of what tool you're using. This is also the list for support for the tools we provide.
Want to improve the VP8 codec itself? See the codec-devel list.
The WebM project is in its infancy and is largely comprised of people who have been working with the code privately for years. As such, we've internalized a lot of knowledge about that code, and one of the challenges to growing our community is sharing that knowledge. Write an article on what you learn, and we'll put it on the website.
We're committed to WebM being an open and helpful environment, and part of that is making it easy to learn and get involved. We could use more tutorials for working with our tools and code, and we'll also want to codify some of the things that grow organically in our fledgling community. Get involved, and help us set the tone!