[TYPO3-english] TYPO3 Customer Feedback Initiative

[JoH asenau]

> Honestly I have problems understanding the goal of this page, and why a
> development frameworks should speak to end users, which will never use
> directly the framework.
>
> My customers do not care if I use TYPO3 or WordPress or whatever CMS.
> Important for them is if I understand their needs and provide a good
> solution. Which CMS I use is not important for them.
>
> And again, an end customer can say things like 'I need an easy way to
> make forms', which is different from 'I need a flexible form constructor
> package, to be integrated with kickstarter or callable as library, with
> mysql constraints and transaction management', which can be asked by a
> developer which spoke with his end customers.

Well - it depends on the definition of "end customer".
In your case this is an "ordinary" user, who still might have some needs 
you don't know of - so this is what Søren meant.

But there a re lots of other scenarios beside this scope especially when 
it comes to those "enterprise clients" TYPO3 CMS officially aims at.

Currently for example I am working as external consultant for a project 
of German Telekom.
There is no agency or integrator in between and most of the decision 
makers are working in several IT-departments.

These people have certain criteria that makes them decide in favor or 
against a CMS framework. If we don't meet these criteria due to a lack 
of communication between those decision makers and the developers 
creating the solutions provided by TYPO3, we might lose some important 
customers. At the same time this means losing a lot of budget for 
development that might have been contributed later on, as this was the 
case for example with the current version of Grid Elements.

Still these decision makers are "end customers" as well.

IMHO the goal of Patricks approach is to have developers - especially 
core developers but other developers as well - listening for the needs 
of any kind of customer before they start to define the requirements 
they want to provide solutions for. Otherwise TYPO3 CMS might become a 
developer oriented tool, which is certainly not the goal of a CMS. 
Actually this would be a job for TYPO3 FLOW.

Cheers

Joey

--
Wenn man keine Ahnung hat: Einfach mal Fresse halten!
(If you have no clues: simply shut your gob sometimes!)
Dieter Nuhr, German comedian
Xing: http://contact.cybercraft.de
Twitter: http://twitter.com/bunnyfield
TYPO3 cookbook (2nd edition): http://www.typo3experts.com