[TYPO3-dev] TER, typo3.org, everything went FUBAR!!! :))

[Daniel Hinderink [TYPO3]]

in article mailman.1.1141422113.16858.typo3-dev at lists.netfielders.de,
Michael Scharkow at mscharkow at gmx.net wrote on 03.03.2006 22:41 Uhr:

> Daniel Hinderink [TYPO3] wrote:
> 
>> Well, not exactly. Your message and it's follow-ups prove that you at least
>> expect the same service from an Open Source project then from anything else.
>> I leave it up to you, to judge if it is the fault of the people active in
>> this project or if F/OSS in general is bound to disappoint you.
> 
> Could we please stop the "It's Open Source, so don't expect things to
> work" arguments NOW.

I did not write that. Regardless of that, it's an interesting question which
deserves more than a dogmatic answer.

What my mail was about is that this project is as good as we, the community,
make it. In this case, this community has neglected beta testing and very
few people got on the project to help create TER2 in the first place. Now we
have problems and a bottleneck - surprise?

> I cannot see any general demanding attitude in
> Dimitri's post, and I think you should be aware as much as anyone here
> that TYPO3 itself is very high quality, so why not have the same for the
> website and for TER?

As long as you (meaning anyone) expect yourself to make it high quality, I
think there is a chance that it will happen. For those that are here to
socialize on the mailing lists, they can only hope someone else does it for
them. What they certainly have no right to, is to complain.
 
> I did write a mail similar to Dimitri's on relaunch day, and I was told
> to just sit and wait. Nothing much has happened since, and I don't blame
> Robert for having to earn his living rather than spending another week
> hacking TER. But a lot of professional TYPO3 users have been screwed for
> some time now (not me ;)) because typo3.org and TER is a essentially
> one-man-project, which is strange enough considering the core team has
> more active members than ever.

My impression is that Robert has almost no help to speak of.

But as discussions go on and on on this list, time ticks by that could be
put into working for TYPO3. I will return to that now.

Cheers

Daniel