[Typo3-dev] The future of the TYPO3 platform

[Kasper Skårhøj]

Hi Martin.

Thanks for writing us!

I don't know much other OS projects in details, but generally I hear
that TYPO3 has a high quality of such a project. I think this is due to
some of the characteristics that are also our problems - for instance
that it has traditionally been tightly controlled by me.

So just so you understand generally: We also have some unique qualities
that can be lost if we do not care. 

Maybe others have more competent insights - after all I'm just a coder.


> That said, the community should come up with a better way to manage the 
> project as a whole. Things that come to mind:
> 
> - AFAIK there is no bugtracking system (like e.g. bugzilla)

Did you have a problem with a bug you couldn't find a person to submit
to? "bugs at typo3.com"? Anyways, we actually do have a bug-tracker
(Mantis)

> - AFAIK there are only a handfull of core developers (besides Kasper)

True. It turns out to be hard to recruit people into this since there
are extremely high expectations to the quality of their contributions.
We are doing our best extend the team - but not at the cost of our
"unique" quality/stability!

> - There should be a better management for the available manpower (people 
> managing e.g. CVS, release maintainers, feature plans, plugin 
> coordinators, website updates (maybe blog?), documentation, i18n)

Did you look at the project/teams page. What is wrong with this? There
are plenty of ways for people to engage themselves.

Did you take your part of the work?

I want to point out another thing which you do not credit here:
Extensions.
The concept of extensions in the context of TYPO3 is VERY POWERFUL and
build to allow individuals or groups to supply truely significant
functionality to the system. It would not be fair to overlook this fact
since extensions is a highly available form of contribution! 
In the light of this your examples seem to provide LESS freedom than
already exists for people!

> managing e.g. CVS

Andreas Otto does this quite well. No problems.

> release maintainers

I think Michael Stucki and Ingmar has done marvellous jobs. Just notice
how certain fixes has been added to 3.5.0 by them on their own!

> feature plans

Need a feature? Start the Extension Kickstarter and go...
We don't need plans, people can start today!
(I know this is simplifyed... :-)

> plugin coordinators

We have tried to start up "Extension Mentors" which would be kind of
manageing the Extension repository. TRuely some action needs to be
taken.

> website updates (maybe blog?)

yes, we should have some news going.

> documentation

No volunteers. I have to do it myself.

> i18n

Team members are working on this. Do you see any problems? And for
translation of the system we have a kick-ass system!


> - Version and release cycle PLANS

I think many wants this.
Daniel Hinderink is a great promotor of more structure like this. If
anyone can create that and actually follow it, that is fine with me. 
Personally, I'm not able to follow a stiff document point by point. Just
doesn't work for me, so I'm excepted. I go with the flow and if you want
some insight into my effectiveness, maybe that is one of the keys.

> 
> I have been using TYPO3 since v. 3.5.0-rc1. What will happen to the 
> 3.5.0 release anyway? Will there be bugfixes and/or backports for the 
> 3.5.x branch?

Of course there will be no backports. 
One of our (apparently) unique features is that (unless otherwise
stated) you upgrade to the next version with full backwards
compatibility and only some 4-5 buttons to press to synchronize things.
And why wouldn't you? To avoid having the copyright notice of 3.5.0
shown in the login screen?

Martin K. suggested to add branches / tags in CVS for future releases. I
think that is a good idea though.

> 
> I am comparing this to say the linux kernel project, the KDE project or 
> for example the gentoo project. I am quite happy on how the information 
> level for users, geeks, and developers is shared at different levels. I 
> realize the these projects are far more sophisticated but TYPO3 
> definitely has the potential.

Since we don't have time to analyse all these projects or experience
their communities first-hand, maybe you can give some actual suggestions
to what can be done with TYPO3's community?
I'm actually pretty sure that if you really want to shape TYPO3s
community to the better we are ready to allow you a shot at it.

> 
> Conclusion: Things just seem a little unstuctured. I believe Kasper 
> should concentrate on what he does best: code :-)

Thats what I do all the time.
Oh no, not true. I do actually write a lot in manuals! Guess why? Seems
to be the *least* interesting job to do for other volunteers! Hence I
*have to*!

> 
> Well happy posting and maybe we can build on this.

Absolutely, with some more practical suggestions.
I would also love to hear Daniel Hinderink and Christian Jul Jensen and
other "insiders" on this. Since I *am* clear about my role as a
programmer the implementation of these things are mainly in the hands of
someone else than me anyways.

- kasper