Skip to main content

Join Us and Contribute!

In the last blog post we described how our infrastructure and setup works and what we wanted to achieve with it. Now you can experience it yourself! 

We just opened our infrastructure to allow public contributions - for example to the blog extension. Here's how it works:

Sign up!

Sign up for an account at - just click the sign up link on the login form. Choose an email address (ideally the one that you will use for git, too) and fill in your name. After registration you should be logged into JIRA (where you can create issues and keep track of them). 

Our main contribution hub a.k.a. repository management is bitbucket, so head over there now.

Conquer bitbucket!

If you're not automatically logged in to bitbucket just login again with your JIRA credentials as single sign-on for all our atlassian applications is enabled. 

First of all you should browse to your account page and setup your SSH keys - and your avatar :).

Then head over to and have a look at our open source projects. Choose the one you want to contribute to - for example the blog extension.

Give us all your code!

We are using feature branches and pull requests for our work. If you are not familiar with that workflow you can read up on it in Atlassian's documentation.

Mainly this means that for every story/task/bugfix we create a corresponding feature branch where we commit our work. After finishing a feature we push the feature branch to the remote bitbucket. Did you know, that JIRA can do that for you? Just go to the ticket you want to solve, and look for the 'create branch' link. It will suggest to branch from our develop branch and even gives you a name for your feature branch.

Use this newly created branch, put all your code into it, and make sure you mention the ticket number somewhere in the commit message. Then PUSH :D. The response of the push (and then contains a link to create a pull request for that feature against develop. 

After creating the pull request the feature has to be reviewed by at least one TYPO3 GmbH member as well as having at least one successful build on our continuous integration server ( You can significantly increase the chance of acceptance for your patch by adding unit tests to your feature. 

After the pull request has been accepted a team member will merge it to the develop branch. Please note, the feature will only be available in the next release after its' merge - so after tagging and publishing a new master version, which is done by a TYPO3 GmbH member.

We are looking forward to all your contributions!

Find answers to frequently asked technical questions

You'll find answers to other frequently asked technical questions, instructional clips and all sorts of helpful videos on our TYPO3 YouTube channel. Come along and join us there. If you find this useful, please share the link on your network.


No Comments

Write comment

* These fields are required