Regular Open Sprints

Get more done together in open source. In the TYPO3 community, we recommend working together in regular open sprints. This concept was introduced in 2019 by the TYPO3 Association. 

The idea behind "combined sprints"

In the past every team had its own (mostly invite-only) sprints. But for many projects, bringing teams to work together is more effective. For example to work on the typo3.org website: the design team, server team and the website team harmonize well. So that's why we encourage teams to organize combined sprints towards shared goals. And even when teams are working on different projects, being in the same space at the same time helps teams mingle, share ideas, and participants can meet new people. 

Stefan Busemann

Any qustions? Get in contact.

Contact

Goals

  1. Help teams to meet at one location and join forces. 
  2. Provide a location and accommodation for teams from the regular open sprint budget.
  3. Make it easier for interested community members to get involved - onboard them when they want to sneak into a team.

Teams can prepare collaborative agendas for regular open sprints, but they can also just share a sprint location. Even when they aren't directly working on the same project, they can get together and share the same space. It is always inspiring when people see what other teams are doing. It's a great way to get new ideas and creative solutions. And of course, these kind of sprints are also open for everyone who wants to contribute to the project. For example, to improve documentation, create content, create a patch, do a review, and to meet others in the community.

You’re Invited: Join Our Remote Sprint!

The Best Practices Team's inaugural remote sprint is happening on 7 May 2024. We'll meet on Slack for a day of general housework and working through our backlog.

While we may not complete all our goals, this sprint is an excellent opportunity to learn and collaborate. If you are a newcomer to TYPO3 development, come along to gain insights into teamwork, GitHub, bug resolution, and automated testing.

When

The sprint will take place on 7 May 2024. We’ll kick off at 9am (UTC) and we plan to finish at 3pm (UTC).

Where

The sprint is fully remote. We’ll meet in the TYPO3 Slack Channel, #best-practice-team

Come prepared, we have collected all preparation steps at our GitHub Wiki.

What

Daniel Siepmann will host the sprint. We’ll start with a quick check-in of participants, make sure everyone is set for success, then we’ll distribute the tasks among the attendees. If you’re a newcomer, there will be people to support you and answer questions.

We plan to work on these topics in the following order:

  1. Continue with the tasks that got started during the last sprint
  2. Finish the open runTests.sh tasks
  3. Work on 13.x support
  4. Do the other breaking changes

We probably won't complete all the goals, so the remaining tasks will be carried over to future work and sprints.

Your Benefits

Whether you are an experienced TYPO3 developer, or new to the CMS, there is always something to learn. Come along to this sprint and get real-world experience working with focus inside a team on an open published extension.

Participants of this sprint will learn-by-doing, in particular:

  • Using GitHub as a Git hosting and CI platform.
  • How to catch and fix bugs, covered by tests.
  • Best practices for extension development.
  • Fast end-to-end tests via TYPO3 testing framework functional tests.

You Can Meet:

  • Daniel Siepmann
  • Oliver Klee
  • Łukasz Uznański

Accommodation Düsseldorf

For our sprints in Düsseldorf we do have special rates in a hotel.

More

Note: You have to be logged in, to access that page.