The past year has been one of the greatest years for TYPO3. 14 months ago, a lot of people thought TYPO3 would be dead more sooner than later, seeing Drupal, Joomla and others taking the fast lane and leaving TYPO3 with what was pretended to be “that German legacy system”. After the successful release of 7LTS, which is in many regards a piece of CMS that is very different from previous versions, I think we owe the world to show that we are not only back for good, but capable of really making it to the top. Here is how I think this can work. Remember, this is my personal blog and I am just sharing my very personal view on things. So take it or leave it.
(Reads: 4 minutes – for obvious reasons available in english only)
Vision
I have a simple long-term vision for TYPO3: Imagine a global community 10 times as big as it is now. Not centered in Europe, not exclusively tied to CMS but to software technology in general. A movement, in charge of Inspiring People to Share. Share information, friendship, or more broadly the good life. A role model when it comes to Open Source. A peer to peer production and open collaboration. A global group of people that naturally suck in new talent. An environment of fun. Based on humanism.
I know it sounds a bit corny, but this is what drives me. Since I joined this community, I see this vision in front of my inner eye. And this is the reason why I did not leave like so many others did when things really got stupid 2 years ago.
Stage One
I think this vision describes the potential we have as a group. And I am usually measuring achievements towards the potential that things hold within. In the past, I did not make a lot of friends by doing this because, basically, it means that when the majority of people is grateful and happy about an achievement, I need to go like “Ok, we can do better”. Great things develop out of good things when someone stands up to ask on how to do things even better.
That’s why I was happy to see that Mathes, who we have to be thankful for a lot of the cool stuff that happened in the past months, was somewhat missing the release party but started to prepare work for the upcoming days. “We are still here” feels like the beginning of something really great.
“Abusing Business to empower our cause: The TYPO3 Inc.”
Most of you know that I am working on the TYPO Inc. project. And frankly, I struggled at first. I underestimated, as usual, almost every aspect. And while I was involved in quite some Start-Ups, I realized this is very different to what I encountered before. There are big questions that we need to find solutions for and the more we dig into things, it turns out it’s really going to be the classical, bumpy start-up ride. This makes it a lot harder to find people who are able to take on the challenge.
On the other hand, we realized it is not so easy to get government funding. One could mean that especially the EU got a valid interest in seeing TYPO3 grow, but the whole process is so heavily overregulated that it simply needs more time than we have assumed respectively planned for in the process of preparation. And when talking to classical VC’s, most of them state they would love to be in, but would certainly be in for the money. That’s clearly not what we wanted.
The best funding is the one coming out of our own community. That’s why Adrian and Robert set up a survey, asking the members of the association whether they would be in for doing a one-time payment in 2016. With this money we could boot a small core organization and grow things organically. What looks elegant comes with the downside that it also adds a lot of risk to the whole venture. We could simply run out of money before we could organize new funds and, more importantly, make the business model work out in favor of the whole community.
For now, it’s clear we should go in phases rather than going for a big bang start. I am going to formalize all options and will publish all the findings along with a recommendation. And then it is up for discussion.
Going truly international
One thing I consider particularly important is that we are going international. We really need to come out of the DACH corner. And this does not mean that we should solely go for markets like Sweden, France, Spain and UK etc.. It means the US. The US, AND Sweden, France, Spain, UK and others. If we figure things out in the US, the rest is so much easier. It’s as simple as this.
This is where we start
I toured the agency meetups this year, saying there is a great future ahead. And I really mean it. So where we are now – and this is a team achievement – is a starting point for our trip toward an even greater TYPO3 universe. As long as we have that spirit, we can just go anywhere we want to.
An insane effort
It all sounds like an insane effort. And it probably is. But then again, there are so many people involved in TYPO3. If we can get two third of them going and just make him/her contributing what is possible for them, we can generate immense power. I am in on this more than ever. And I hope you are as well, although you might not agree with all the stuff I wrote here.
As said before, this is just my personal, private thinking and I am kind of abusing the reach that blog developed to get it shipped to you J. If you have a different vision, you disagree, I am happy to post your text and ideas on TYPO3 here as well. Just send it over, it’s a free speech world.
Artikel auf Social Media teilen:
14 Antworten auf „TYPO3 is still here! Now what?“
Could you not just leave TYPO3 to die in some old repo and start over?
TYPO3 7 is basically hell to use, as most systems are being updated to it and everybody that has done an update from TYPO3 4.7 or 6.whatever to 7 knows that it is way to time consuming.
Where are the great features that came in other CMS around 2012-2014. Like why has TYPO3 not got a REST API or something like that? Why the hell is one supposed to deal with Fluid or Static content? Why doesn’t it have a URL Router? I mean seriously – why?
Also caching framework is so broken, leaving it off is actually a viable solution.
TYPO3 is so great I made a WordPress blog to tell about it.
I think it’s not of much use to start a comparison between Neos and TYPO3 here. However, I’d like to rectify what Mattes wrote in one of his comments.
Mattes joined the Neos project for a couple of sprints and we appreciated that he contributed to the communication side of the project, specifically the website. Technically he wasn’t part of the Neos team though. As far as I remember, he lost interest because he didn’t see a way to roll out Neos in his own company and was more interested in short-term gains, like speed. That’s completely fine, but didn’t match the feature goals we had at that time for Neos.
Contributing to Neos has never been as easy as today. We put a lot of effort into lowering barriers of all kinds, and even though the Neos Team was happy enough with Gerrit, moved to Github due to the feedback we got from the Neos community (for example https://twitter.com/nottulner/status/628595325637406721). We mentor new contributors and each of the three Neos teams takes their turn each week to browse through Github pull requests, answering questions and help with onboarding new volunteers.
As for where TYPO3 or Neos or any other software is a good product, you need to ask yourself, continuously: if I wouldn’t have any experience with the product already, wouldn’t run a company tailored to that single product, would I choose it again today? Since we don’t have cohort analyses at hand, it’s just guesswork.
Everyone has her needs and preferences, and I wish the TYPO3 all the best with finding a product vision and identity.
And as for the project itself, I see the advantages (for the people being involved) of creating a company. But I don’t see the legitimation to do so, out of an existing Open Source project with a long history, and I wonder what it does to the original vision, inspiring people to share.
I think the transformation to a TYPO3 inc must be really well considered and done right. One of the really outstanding matters of TYPO3 is the awesome community and self organized nature. Of course this also has some week points, where the wish for a TYPO3 inc gets it’s food.
To me one of the things to consider would be an open economic entity like a coop/genossenschaft. This entity is meant to act economically for the benefit of it’s members. Sounds like a perfect match to the problems we are facing.
Relying on external venture capital will bring in a huge change which I personally dont like at all.
Untill today nobody could tell me yet why to stick with TYPO3 CMS when there is Neos already in a quite good status. Why do the core-developers still hang on the legacy-core instead of combining the power and get Flow/Neos ahead even faster.
I am a TYPO3-developer for over 10 years now and the best thing by far that got into TYPO3 was extbase. Since that point I was waiting for the day when Neos (it was still called TYPO3 5 that time, later Phoenix) will replace TYPO3 CMS.
We all know it ends in a community-split and I think the negative outcome of that will be seen in the future.
For me, after touching extbase I fall in love with DDD and the MVC approach. Same goes for all the coworkers that I had in my career. Really nobody of us understands why TYPO3 7… was developed and people still stick to it instead of using the much much better technology that is so near.
How do you make extbase scale with 10s of thousands of records?
Honest question.
Lazy loading is one approach, implementing CQRS another that scales better for more complex cases.
Good example was shown by
Henrik Møller Rasmussen at the Inspiring Conference 2014. Slides are here: http://de.slideshare.net/heinodk/cqrs-is-not-event-sourcing-32931373
Seems like we need to be more clear about the current technical progress we make in TYPO3.
To be honest: Why did Neos not take off? Its all a matter of trust. Trust works in two directions: past and future. I leave it to you to make the conclusion.
You mean the core-developers did not have enough trust in the ideas of TYPO3 5 and that’s why there were not enough people helped to create Flow/Neos and sticked to TYPO3?
Or is it about trust in the team that started Flow/Neos?
Really would like to get more of your thoughts about that.
I am speaking customers here, not developers. Trust in the product is what matters. Innovation can only create trust if there is a clear roadmap, commitment and delivery. Additionally market share is another factor that has influence on adoption. But I am sure you are aware of this.
Thanks for explaining. And I understand that point.
I see the products mainly with the eyes of a developer. Marketing and stuff like that is another story.
In my first comment I asked, why the core-developers did not switch and contribute to the new technology. If the reasons are not technology-based it’s out of the range of my understanding as I love writing code and I love the tools that help me to do it in a good, fast and flexible way. And for that reasons I always waited for Neos to be the next TYPO3 (with still the brand in front of the name). Sadly it did not happen.
The question of customer trust is a task for the people responsible for marketing, sales, …. We (the developers) can hand over lots of reasons why the new technology benefits the customer.
I hope nobody gets me wrong here, I don’t want to start bashing here, I want to understand the guys who still work on the TYPO3 CMS core why they decide so and don’t contribute to Flow/Neos.
I earn my salary by (still) developing projects with TYPO3 CMS. I just see what I could do with the power-tool that is out there, maybe I am blind to what is wrong with Flow/Neos (on a technical level!). I just see advantages.
I can only speak from personal experience, but I had an incredibly hard time contributing to Flow/Neos (and I was part of the team for quite some time).
Here’s the thing:
In Open Source in general you cannot force contribution.
People will work on what they think *is* in line with their state of mind – not what you tell them what should be in their minds.
You need a couple of things:
a) A motivating atmosphere
b) You need to get stuff on the road instead of day-dreaming.
Rule of thumb:
80% today is better than 110% in 5 years.
c) A solid funding to enable people that cannot spend the necessary money themselves.
This goes hand in hand with d).
Since I like real world examples:
I want to sell you a car.
So please give me the money to do so, but I won’t promise you that you will actually get the car…. ever.
I can send you my bank account number via private mail, if you like :)
d) Deliver what you promised.
If you fail ANY of the above, you’re going to have a hard time finding people (or stay niche).
Thank you a lot for the input. Did not know that it was so hard to contribute.
My point of view agrees mostly with you, Alain. There is only one thing, I disagree.That’s the US-Stuff.
Yes, to survive as as future CMS, TYPO3 has to go international. But I think, there are different ways, to reach this aspect. The deep multilanguage-features in TYPO3 are one of the real unique selling propositions (usp’s) of TYPO3 CMS. I don’t think, that the US-Market realy needs this feature, but we European need this.
This is our biggest chance to spread over the world.
Maybe, we think about Sweden, France, Spain and UK. Also, we have to think of the Eastern Europe countries like Poland, Czechoslovakia, Hungary, Romania, etc. There is a huge developer community as seen at T3EE these days. We have to activate developers there. With these people, TYPO3 will grow and reach an international level.
Europe is multilingual and Europe is very strong.
I like to read your blog-posts. I always get great thoughtless suggestion. Many thanks, Alain.