T3CON Recap - How to Fail Your Agile Transformation Successfully
This T3CON24 recap explores why Agile transformations fail and how to fix them. Learn to focus on purpose, vision, and knowledge sharing for real…
It is now nearly a tradition that our team meets after the TYPO3camp Rhein-Ruhr. Our sprint started right after the camp ended. 82 tickets and 76 merge requests were done.
Common Infrastructure
Speed: Leverage browser caching
Common Layout:
typo3.org:
my.typo3.org:
Participants of the sprint:
Thomas Löffler, Stefan Busemann, Harry Glatz, Boris Schauer, Mathias Bolt Lesniak, Andreas Nedbal, Valentin Süß, Sebastian Kotte, Dominik Dörr
The biggest goal was reached already in April: typo3.org was relaunched and my.typo3.org was started. This was end of our relaunch project, which was started end of 2016. We are very proud that we were able to achieve this goal completely through the efforts of our community.
Our team did not fall into a deep sleep. We managed to have six sprints during the whole year.
We like to say thank you to our 27 contributors and to the companies, which donated the time:
Thomas Löffler (SpoonerWeb), Stefan Busemann (in2code GmbH), Harry Glatz (analog digitalagentur), Boris Schauer (analog digitalagentur), Mathias Bolt Lesniak (Pixelant), Miro Olma (Medienagenten Stange & Ziegler oHG), Christian Knauf (analog digitalagentur), Yaroslav Trach (Pixelant), Tanya Nosenko (Pixelant), Myroslav Lutsiv (Pixelant), Olena Bulat (Pixelant), Tomas Norre Mikkelsen (AOE GmbH), Marco Seiler (Marco Seiler - Internetprojekte), Axel Müller (Axel Müller IT-Services), Michel Löw (Punkt.de), Andrii Pozdieiev, Rostyslav Matviyiv, Sanjay Chuahan (Nitsan), Keval Pandya (Nitsan), Marcus Schwemer (in2code GmbH), Sebastian Stein (in2code GmbH), Andreas Nedbal (in2code GmbH), Felix Ranesberger (in2code GmbH), Valentin Süß (Browserwerk GmbH), Sebastian Kotte (Browserwerk GmbH), Dominik Dörr (KEMWEB GmbH & Co. KG), Jo Hasenau (Cybercraft GmbH).
All accommodation, food, and travel costs were covered by the TYPO3 Association.
For this year we will introduce additional sites, based on our template framework.
The rest of the year it is planned to improve self service options for members and community.
Find more about our plans at https://typo3.org/community/teams/typo3org/team-roadmap/.
Join our team at the #t3o-development channel in https://typo3.slack.com and get in touch to join our next sprint.
This T3CON24 recap explores why Agile transformations fail and how to fix them. Learn to focus on purpose, vision, and knowledge sharing for real…
The versions 13.4.8 and 12.4.28 of the TYPO3 Enterprise Content Management System have just been released.
The voting for TYPO3 Association Board and Business Control Committee (BCC) has started. All members have received voting links by email. Due to an…
The first Monday of the month at 11:00 — this is the time to mark in your calendar if you want to help shape best practices for code in TYPO3…
The TYPO3 Board Elections are coming up! In this special episode, we introduce you to this year’s candidates and give them the stage to share their…
Learn the features and capabilities that make TYPO3 the best CMS for Higher Education and why universities worldwide use it for their content…