[Neos] WCM in 2017

Mathias Schreiber mathias at typo3.org
Fri Jun 7 18:45:35 CEST 2013


Jigal van Hemert schrieb:
> I read a few things from you article:
> - we have a developer-oriented community. To me that means that other
> talents we desperately need (vision, ux, design, marketing, ...) are
> somehow not active in the community. This is a shame and we somehow need
> to activate these talents... (but how?)

Interesting question.
To me it seems to be a top-down problem right now.
Means: Enhancing UX is not "cool" enough for the average "give-me-php" 
coder type of guy.
Plus a "pure" developer often lacks the view of the average editor.
This is not because they are stupid or not willing to... I for myself 
produce music... and thus listen to a song on the radio in a totally 
different fashion.

Our current experiences are that you're not invited to the club if you 
haven't commited like X lines of code. Three people approached me apart 
from each other and shared the same story.

> - the lack of a body with vision for the future, for a roadmap, is now
> filled by "CMS Team" (for TYPO3 CMS), but this is still a
> developer-based group. Obviously this has to be a group with a wider
> range of talents

Agreed.
See above.

> - from other responses it seems that exchanging information is an
> important feature for the future. As we have an active group of
> developers this shouldn't be a huge problem. The hardest part is to
> figure out the features this must have and the standards (if any) it
> needs to support. For this we desperately need the inactive talents.

Yeah, this opens up a new vector of problems.
See, the "code-guy" doesn't want to be told what the market needs.
This is why innovation that could make it to the market has basically 
stopped.
Before you put me off with the classic "ah, Mattes is ranting again" 
hear me out... I'm fine with being put away later ;-)

Name three features that have had marketing impact since 4.2.x
Having impact means solving an editors problem.
I can't name one - which is sad.

We have awesome technology under the hood... which basically doesn't 
really bother the every day editor.

I am willing to help here.
Since I can't provide code (I'm too old for this ;-)) I can provide 
experience - customer demands, see-beyond-ones-own-nose thinking etc.
The problem is that as soon as you come up with things the 
market..heck...TYPO3 in total needs to stay competitive, you get the 
same answer... scratch your own itch.

It would need a massive change of mind in order to get both "sides" to 
work together again.
For those curious how we managed that "in-those-days (tm)":
Back in 2003 we sat together in a rather huge group of people and 
brainstormed about upcoming features the market demanded.
Basically individual folks came up with the stuff THEY needed, but the 
collective took the bits and pieces and made them even better that ones 
initial idea.
This is where DBAL, workspaces, services and hooks come from.

Bottomline is I'd strongly suggest to have something like this again.
Some sort of meeting thats dedicated to doing concepts and brainstorming 
rather than code.

Do I somehow get my thoughts across?
Had a rough month :)

Cheers
Mattes

-- 
Mattes - This time I come in peace



More information about the Neos mailing list