[Typo3-documentation] Quit talking and start chalking!

[JoH]

OK, folks!

I guess it's time to kick some asses.
Or as my parents always said:
"Put them all together in a sack and beat it!
You will always hit one who deserves it!"

Everybody in here is talking about "better documentation", "usability",
"accessability" and all those other nice terms.
But this is what it is by now: Just nice terms!

We have over 500(!) posts in this newsgroup against a few docs on
wiki.typo3.org that deserve the name "documentation" (i.e.: tt_news, typo3
installation basics).
Most of the other stuff is about rules, how to do documentations the right
way, how to use a wiki and all the rest of it.

And it's sad but true: Most of the original documentation is far better than
anything on wiki.typo3.org!

IMHO this has two main reasons:

1. A wiki is the worst thing I have ever seen when it comes to create
something like "better documentation" since everbody is allowed to write
what he likes wherever he likes in the style he likes and as often as he
likes. This is more than just counterproductive - it's a waste of time and
resources.

2. Platoons of wisenheimers are fighting a trench warfare while discussing
completely unimportant things to death.

I have been asked to contribute to the documentations when it comes to
TypoScript Tips & Tricks. But as long as things are going on the way they
did I surely have something better to waste my spare time with.

Some questions (no answers needed, just something to think about):

What is the reason for this wiki-crap?
Something that needs to be documented before you can use it to create a
documentation is IMHO no option.
And IMHO you can add as many stylesheets as you like, the usability of such
a wiki will stay what it is - crappy!

Why not use Typo3 itself to create those docs?
It's well structured.
You have nice looking and working tutorial extensions that show how to do
it.
You have a system of usergroups and restricted rights that makes it possible
to have writers, editors, editors in charge.
If you need something else than Typo3 to create simple documentations this
says very much about Typo3 itself and this is why IMHO you are forced to use
it instead of any other tool.

Why is there no real project-manager or team leader?
Too many cooks spoil the broth.
Most of the people need someone to show them the ropes.
Someone who coordinates things and simply MAKES the rules instead of
discussing them.
This is why democracy is such a slow and sedate system. Often it takes years
to just find out that you won't come to a decision.
But when it comes to Typo3 documentations it's not about democracy it's
about business. (Yes, I know we are talking about an open source tool, but
this doesn't necessarily mean that it's not about business)
I don't know any company where work is done the way it is done in this team.
And if there is one you can be sure it will go bankrupt in the near future.

Well, guys'n'gals!
Stop talking and start chalking the cues to pocket the some balls.

And please: DON'T discuss what I wrote! Accept it as an incitement ...

Joey