[TYPO3-mvc] [RFC] Keeping FLOW3 Compatibility

Sebastian Kurfürst sebastian at typo3.org
Sat Feb 11 14:01:29 CET 2012

Hey everybody,

first off, thanks very much for the recent activity in Gerrit on Extbase
-- great to see that so many people contribute in it!

Personally, my focus has shifted a little more towards FLOW3, so that I
don't have time anymore to look through every single changeset in gerrit
on Extbase. Still, it is very important to me that we stay in sync
feature-wise and bugfix-wise where it makes sense.

Furthermore, I feel personally also responsible for Extbase code
quality; that's why I'm down-voting many topics in Gerrit without unit
tests. Sorry!

An example for a feature which could easily be forward-ported to FLOW3:

For me, it would be very important that we, as a community, try to keep
extbase and FLOW3 as much in sync as possible, especially in the
following areas:

  * MVC
  * Property Mapping, Type Converters
  * Validation
  * Error Handling

Another example for such a feature relevant to FLOW3 would be:

That's why I'd suggest that for every feature / bugfix in this area
which takes place, we should at least make sure that a bug report on
http://forge.typo3.org/projects/package-typo3-flow3/issues exists --
linking the extbase and the FLOW3 issue together. This way, this is some
kind of "TODO" list for FLOW3 developers, and also enables the FLOW3
team to learn from real-world experiences made with Extbase.

If there are bigger changes in Extbase where you are not sure if a
corresponding technology exists in FLOW3, you can quickly grab the
developers (including me) inside the #flow3 channel on irc.freenode.net.

Furthermore, we should ensure that changes in these areas are covered
with unit / functional tests, as we have quite some in this area
already, and we should make sure that the test coverage doesn't shrink
because of "so many features so little time"...

Do you think that makes sense? On one side, I don't want to slow down
Extbase development, on the other side, I think we need to invest some
time thinking about the FLOW3 compatibility. Creating the respective
issues doesn't sound like too much work for me, but I think it will help
us to stay more in sync.

Looking forward to your comments :)


More information about the TYPO3-project-typo3v4mvc mailing list