TYPO3 Core Team

"Jointly Innovate Excellent Free Software Enabling People to Communicate." – The TYPO3 Project's mission

: TYPO3 Core Team June 2010 Elmshorn

The TYPO3 Core Team is dedicated to develop and maintain the central parts of our favorite CMS. Check further down our mission statement. Additionally there are sub teams for each of the major branches (v4 and v5) and project teams working on major features for specific versions.

These pages contain information about the current and future development as well as helpful resources and guidelines.

Contributing Patches

You don't need to be a core team member in order to contribute code to TYPO3. For the version 4 branch please follow the instructions given in the Core Mailinglist Rules. For version 5 you need to sign a Contributor License Agreement before submitting contributions. As soon as you did that, you can push your contribution to review.typo3.org (read more about this on the forge wiki).

Be a Friendly Ghost!

With more than 30 members it's not always easy to find a consensus. Especially when passionate developers start arguing about their favorite features and techniques it can get a little rough.

The number one motivation for most of us is the mere fun of contributing to something great and indulge our passion for fine PHP code. So let's not forget about that and be a friendly ghost. And as a little help we have written down a few communication guidelines.

Mission statement

The TYPO3 Core Team endeavors to make TYPO3 the best of its breed. To achieve this mission it pursues the following goals:

maintain and enhance the TYPO3 core
ensure TYPO3 source code quality
be a pillar of the community

This translates into the following tasks:

package and publish new releases according to the release and maintenance policies
review patches both before and after commits
care for the central development infrastructure (version control system, bug tracker)
participate in the mailing lists and in community events, in particular the TYPO3 Developer Days (T3DD)
ensure its own continuity by educating and inspiring community members to participate in the development and maintenance of the core

Notes

Not all members take up all the tasks, but the whole team is responsible for that.
Members must keep an open mindset to new ideas from both inside and outside of the team.