Got time, a computer and a brain? Here is how you can help:

A complex system like ours needs a lot of documentation. And despite the complexity that documentation should be easy and fun to read. Right?

Tasks: Proof reading existing documentation, writing new documentation, translations (at a later stage)
Skills needed: Writing skills and very good english are a must, experience with DocBook XML would help
How: Check out the documentation from SVN, modify the DocBook files (e.g. with XMLmind), open an issue and attach the patch or modified files

We don't code bugs, at least not on purpose. But if you find one, report it in our issue tracker. But please help us to solve it by attaching a detailed description of how to reproduce the issue. If you can provide a unit test that shows the bug, this rocks big time.

Tasks: Find bugs, describe them, reproduce them in a unit test
Skills needed: Attention to detail, knowledge about PHP and PHPUnit is a plus

You found a bug? Have an idea for a missing feature? Found clever solution to an open task? Just write the code and submit it to us for inclusion. Do it on a regular basis and become famous. So they say.

Tasks: Write clean and useful code
Skills needed: good to expert PHP knowledge, good understanding for OOP, knowledge about patterns and "enterprise architecture" is a plus

None of the above fits your schedule? But you have some money to spare? Maybe it's just the feeling we are doing something valuable? Just let your support show up on our bank accounts. We have families and need to feed 'em, too...

If you want to ensure long-term prosperity of projects funded (partly) by the TYPO3 Association your best bet is to become a supporting member of the TYPO3 Association. Head over to association.typo3.org/membership/membership/ to get started!