[TYPO3-hci] inspiring people to slave, WAS: 4.1 =menubar/iconbar/dashboard; lets go!

[JoH asenau]

Well -since this discussion will lead to nowhere I just want to clarify this
point:

> JoH, it's kind of tiring you don't get it, the whole motivation
> thing. Can't you just plainly explain why us core developers have a
> special obligation to solve your problems? Are we your employees? Are
> we morally obliged you think?

None of the core developers has a special obligation to solve _my_ problem.
And of course you are not my employees (although it's an interesting idea to
have a team of such highly gifted people available).

But I think a core developer has a much higher responsibility for the
product TYPO3 than a simple contributor or extension author. There are
umpteenthousands of people using your product, there are hundreds of
agencies that founded their business based on TYPO3. And of course these
people have a lot of expectations which is just comprehensible.They believe
in the project and its leaders and they expect you to set the course in a
way that will make this product a competitive one.

And on the other hand there are people like Elmar or myself, who's
motivation never was to "scratch their personal itches" but to give
something back to the people who gave them such an incredible product for
free. If I want to make money, I can create a website or write another book
(and I don't even need TYPO3 for that). My contribution to the project and
especially my support on the different lists was almost unselfish and
because I find it motivating to help other people.

If you tell us now that the core developers have to be motivated to realise
the "usability-dictate" of the HCI team, I must ask you, why you actually
set up this team.
Maybe I just got the whole concept of the HCI team wrong, but I thought
there is a demand to improve the overall usability of TYPO3 that the core
developers already agreed on and that the HCI team's goal is to get more
input from usability experts and similar people. If this is not the case and
we have to convince the core developers first, that there is a necessity for
usability improvements, to have them realise what we invented, we can simply
stop our efforts because it's just a waste of time then.

And just a last one regarding patches that are not accepted or sometimes not
even recognized or discussed: There were lots of different bugs in the
bugtracker where people attached their patch that would have solved the
problems, but the bugs are still open (or closed now, after the
"T3DD-bug-closing-session") even though some of them date from over a year
ago. Since there is nobody else than the few core developers who is
authorised to implement those patches, I don't think they should be extra
motivated to just do what they are supposed to do. If they prefer to scratch
their personal itches instead, I think it's time to restock the team with
people who will take more responsibility.

Have a nice evening ...

Joey

-- 
Wenn man keine Ahnung hat: Einfach mal Fresse halten!
(If you have no clues: simply shut your knob sometimes!)
Dieter Nuhr, German comedian
openBC: http://www.cybercraft.de
T3 cookbook: http://www.typo3experts.com