Hey TYPO3 community!
As you might have seen, I’m running for the Association Board. My focus is on strengthening TYPO3’s role in a connected digital world — by improving interoperability, multilingual content handling, and making TYPO3 more visible beyond our bubble.
But I want to hear from you! What are the biggest challenges and opportunities you see for TYPO3? Let’s discuss and make TYPO3 even better — together!
Hi,
I’d like to ask you some questions about things I find important for the TYPO3 Association and the TYPO3 community. (By the way, all of these questions have a story behind them.)
I’ll ask all candidates for the Board the same questions in order to allow the voters to make a more informed decision, and to help get the best people voted into the Board. So answering these questions would be a chance to shine and to show what’s different about you. 
I’d really appreciate if you took the time to answer these questions (or some of them, depending on which topics you find important). Thanks!
1 reply
Hi, Oliver.
Thank you for compiling this extensive list of questions. I see the effort and intention behind it, and I recognize the importance of discussing leadership, accountability, and the future direction of the TYPO3 Association.
However, I’ve chosen not to respond to each question individually. The format and tone reflect a very specific mindset — one that feels more focused on control and evaluation than mutual understanding. I don’t believe that kind of framing leads to meaningful dialogue.
Enforcing the Code of Conduct is not optional. It’s the foundation of any healthy community. When manipulative or dominating behavior is tolerated — especially when it hides behind intellectual justifications or moral superiority — it does more damage than any technical disagreement ever could. If elected, I will take a clear stance: Boundaries must be respected and consequences must follow — no matter how clever, experienced, or entitled anyone thinks they are.
Nonviolent Communication (NVC) is a valuable concept — but only if it is based on empathy and humility and applied in real life conversations. Without that foundation, it can be turned into a weapon: Used to pressure others, silence disagreements, or hide personal dysfunction behind moral language. That’s not communication — it’s control disguised as care.
To restore lasting trust, I will advocate for a truly independent ombudsperson — outside all boards, teams, and paid roles. Elected by the entire community, not appointed by internal politics or the mere formation of a team. Because neutrality can’t be claimed — it has to be earned.
This is the kind of leadership I stand for: principled, protective, and focused on people — not on dogma.
Contributing to the TYPO3 Board is a significant responsibility, demanding an average of 0.5 to 1 day per week. This involves (list is not complete and not sorted by amount of work):
Do you have the ressources to fullfill this?
1 reply
Hi Ingo,
Thanks for asking such a practical and relevant question — it’s important to be honest about the time and energy this role actually requires.
Yes, I do have the resources to contribute reliably. My wife Petra was a board member and vice president of the TYPO3 Association for several years, so I’ve seen up close what kind of workload and responsibility comes with being on the Board. I’m not walking into this with illusions.
Professionally, I’m in a flexible setup: I work with two companies, both of which actively support my TYPO3 involvement. I work fully remote, have no fixed on-site obligations, and my schedule is built in a way that gives me strategic freedom. Our kids are grown up, and I’m already attending TYPO3 events regularly — not just to be present, but to stay in touch with the community.
If elected, I won’t treat this as a side gig or a nice-to-have. I’ll treat it as a role of real responsibility — including the often invisible parts that keep everything running in the background.
So yes: I’m ready. Not because I happen to have spare time, but because I want to do this — and I’ve built the right environment to make it work.