[Neos] RFC: Suggestion for March Sprint Topic

[Christopher Hlubek]

Hi Sebastian,

I fully agree. We experienced that Neos is not up to it's promise because of various instabilities, lots of performance issues (when editing) and robustness of the content repository. While the general concepts turn out to work nice most of the time - and I can see we can deliver more for less in a project - it's not of much use if editors can't use it reliably.

So I don't want to sound negative here and I'm really all in for making Neos a great product, but there's a ton of work ahead and we built up a vast pile of technical debt during the process that we need to find some ideas how to proceed here. I'm feeling sometimes a little overwhelmed by the amount of complexity we are dealing with when we're developing just a simple website that people can edit easily (of course you could do so much more with Neos and Flow, but sometimes it's just that).

So yes, editing and backend stability (with various browsers), content repository robustness, red carpet and installation are important. But I don't see getting there without reducing some of our complexities and tackling the technical debt we produced.

Greetings,

Christopher

Am 12.02.2015 um 13:50 schrieb Sebastian Kurfürst <sebastian at typo3.org>:

> Hey my fellow friends and developers,
> 
> [I've been a little absent doing core work recently; but I actually used
> Neos in some projects now in real life which was also very enlightening.]
> 
> recently, I've been talking to a few different companies and tried to
> help them using Neos. Furthermore, we internally expanded our use of
> Neos quite a bit.
> 
> While doing so, the end-users I have coached have stumbled over various
> bugs in the Neos editing which are quite annoying... I tried to fix the
> ones I was able to reproduce; I also know that we greatly improved the
> product in terms of bugfixes and usability annoyances from 1.0 up to now.
> 
> So I believe we're maybe 90% on the way to a really stable and
> well-working content editing platform; but during daily work, the last
> 10% are annoying enough for people to get frustrated.
> 
> Examples:
> 
> - Link Insertion is sometimes broken
> - Switching the Headline Style does not work reliably
> - From time to time, the "Content-has-Changed" Modal dialog pops up,
> although nothing has changed.
> 
> Furthermore, I've heard from various people that installing Neos is
> still quite difficult.
> 
> 
> So, I'd propose that for the *March Sprint* in front of the Inspiring
> Con, we'll use "Editing Bugfixes and Red Carpet" as the main topics; not
> working on major big features but instead on these kinds of annoyances :-)
> 
> 
> And, ideally, we'd have a prioritized list in Jira before the sprint so
> we know what to work on. I can take care of that in about 2 weeks (after
> my holidays), if wanted.
> 
> 
> What do you think about that?
> 
> 
> BTW: I am looking soo much forward to meeting all of you again in
> Rosenheim -- for me personally, it was a long time since we have last met!
> 
> See you soon,
> Sebastian
> _______________________________________________
> Neos mailing list
> Neos at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/neos