[Typo3-dev] The Right Crew

[Stig Nørgaard Færch]

Kasper Skårhøj wrote:
> Hi Guys,
> 
> Thoughts kept buzzing around in my head this night and finally forced me to 
> get out of bed early :-(
> 
> CONCERN:
> A true concern I have is this; How do we channel all the great resources from 
> the TYPO3 community into a unified effort on the development of TYPO3 which 
> does not compromise the quality or impose great levels of overhead.
> 
> BACKGROUND:
> As the initiator and chief developer of TYPO3 I think I possess at least three 
> key criteria that were necessary for this role:
> 
> 1: Vision
> 2: Pragmatism
> 3: Stamina
> 
> How, people. I'm sure you all have great intensions and plans for version 5 of 
> TYPO3 and I'm all excited about discussing them. But how on Earth can we make 
> sure that such a discussion is not just another play with verbal buzz-muscles 
> that wastes time that could have been fruitfully used on practical coding? 
> 
> How can we make sure there is a crew to make it happen at all?

Okay, I'll try to contribute. As I have not been a part of the core 
Typo3 development(other than a couple of hook patches), I don't know if 
my comments are useful. At least I don't have the same insight as other 
hardcore Typo3-devs.

1) So is the problem how to get from discussions to decisions?
2) Or is it how to get from decisions to results(programming)?
Or both?

First one. Only the people with the complete insight of Typo3 
architecture can make the arcitectural decisions. So that must narrow 
down the base of people who has this competence. You know what is 
possible, and know great ideas from bad ideas.
Anyway, ideas may not be easy to organize through mailinglists. Maybe it 
would be an idea to use other tools as well (Mind Maps - collaboration 
tools?). Of course this should be public to the people.

Second one. Even if I was qualified as an programmer for the core, I 
would think again before giving myself to the project. Because as in all 
other voluntary work, I would be afraid of how much time I will _have_ 
to spend.
If you need people to program, then I guess it would be an idea to give 
the people an idea what they are going in to. Also maybe publicly show 
what tasks are availble.

Also I'm in favor of splitting Typo3 up as much is possible. This way 
you will not have to say yes to developing the whole Typo3 project, but 
only say yes for a specific part of the project. This might seem like a 
less heavy job.

/Stig