[TYPO3-team-core-v5] FLOW3 / Phoenix Planning Meeting -- Notes

[Sebastian Kurfürst]

Hey everybody,

thanks for this very productive planning meeting.

I updated the overview wiki page to reflect the current state, and
created issues for the newly discussed tasks:

http://forge.typo3.org/projects/typo3-v5-distribution-base/wiki/Wiki

Below follows the meeting protocol.

Greets,
Sebastian



*TYPO3 Phoenix Planning Meeting - 23.11.2011*


Agenda

shortly go through list
on http://forge.typo3.org/projects/typo3-v5-distribution-base/wiki/Wiki,
try to quickly discuss things (who does what, ...)

  * [FLOW3] Improve FLOW3 performance (Robert currently working on it,
    until christmas ;))

  * make sure we send proper cache headers

  * ESI support based on Fluid Widgets

  * Caching mechanism should not be an ugly hack in bootstrap -> so
    bootstrap will be refactored to be very thin

  * --> new bootstrap concept

  * MVC will also be refactored a little: "Web" and "CLI" in "Mvc" will
    be moved away

  * --> Robert will continue working on it as soon as Rasmus is gone and
    he is not sick anymore

  * Performance of AOP Proxy Building can also be improved; Robert has
    some ideas about it

  * Bastian tries some measures to improve performance on Windows
    (different file system, ...)


  * [FLOW3] Localization #11954 (Karsten working on it -- quite far already)

  * Label translation / Public API is being polished

  * still missing: conventions for XLIFF label keys; concept for
    translating command line output


  * [FLOW3] Admin Toolbar #30890 (Christian thinking about it, no
    implementation yet)

  * Christian has some ideas about it, checked some other admin tools
    for inspiration (f.e. Symfony); started with a wireframe

  * Christian will update the issue

  * Coding: in the next two weeks

  * Idea of Robert: Generate a "Clover" file for AOP / Security Policy
    Inspection --> this could be opened by IDE

  * --> Christian


  * [FLOW3] Documentation

  * Robert: HTTP Kernel

  * Karsten: Localization

  * Bastian will document stateless widgets & some not yet mentioned
    routing features

  * Rens: might be able to some doc if needed, just assign an issue with
    a part needing attention which is not too complex :) (command line
    chapter? )


  * [FLOW3] Concept for package Management -> currently open


  * [FLOW3] PHP Port of JSON schema #31277

  * Concept almost ready, can be implemented now

  * nice, separate task with clear boundaries

  * -> Rens will look into that


  * [Phoenix] Management /Other Views: #31639 (!!! for next sprint release)

  * Sebastian has created a basic prototype

  * We should use subrequest for the management view (different modules)
    since most of the management view would be plugins

  * No javascript in the beginning, only replace the page reloads with ajax

  * CSS Framework: http://twitter.github.com/bootstrap/ - could be used
    for layout of the management view (layout, forms, etc.)

  * Should consult with Berit

  * http://html5boilerplate.com/ ?

  * Create a system view (user/group management) - create new backend
    user, modify users, delete etc.

  * (later) Create/integrate a page tree

  * -> Aske


  * [Phoenix] Rendering Process Refactoring: #31638(Sebastian, Robert,
    Christian) (!!! for next sprint release)

  * First ideas:

  * Prototype based inheritance

  * Strategy pattern to find current node & node can be explicitly defined

  * Selector syntax to target (sub-)collections (CSS selector syntax?)

  * -> Sebastian will continue with discussing this topic --> next step:
    TypoScript syntax definition


  * [Phoenix] Content Localization: #10515

  * --> we'll postpone it to next year


  * [Phoenix] Phoenix Sprint Release: #31644

  * we want a "phoenix" website (done by Andi), where we can publish the
    sprint release

  * --> Andi

  * Rens: just shout if you need help


  * [Phoenix] Links inside text towards other content: #13534

  * --> we'll postpone it to next year


  * [Phoenix] make Image Size adjustable in UI #30099 (Rens) (!!! for
    next sprint release)

  * there still is a recursion error, but basically it works (TODO
    Sebastian --> have a look at the error)


  * [Phoenix] Configurable access rights on nodes in UI #13545 (!!! for
    next sprint release)

  * --> Rens, next week


  * [Phoenix] Refactoring FE / BE communication towards more REST #29987

  * --> we'll postpone it, as it also interacts with Robert's HTTP
    refactorings


  * TODO Sebastian -> update Phoenix wiki start page


Who has how much time in the next weeks (for Phoenix // for FLOW3)

  * Robert: ~1 day/w Phoenix, 3 days/w FLOW3

  * Rens: ~1 day/w for both (could be more)

  * Markus  1day/w Phoenix

  * Aske: 1 day/w Phoenix

  * Sebastian: 1 day/w both, maybe more in the week before christmas

  * Bastian: 1 day/w both

  * Christian: ~ 1 day/w both more possible nearer to christmas


Can we find more smaller, easier tasks?

  * Pagetree bugfixing ( https://review.typo3.org/#change,6625 ),
    and http://forge.typo3.org/issues/31716 --> Markus

  * FLOW3 org  website -- try to edit it

  * the CSS styling for the containers are not
    correct http://forge.typo3.org/issues/32031

  * Get rid of javascript animation -> should be done by css
    transitions http://forge.typo3.org/issues/32032

  * Enabling/disabling "Preview mode"

  * Toolbar toggling (slidedown/up)

  * Error handling for "Publish Page"
    button http://forge.typo3.org/issues/32033

  * Page tree should be expanded not only towards the first level, but 2
    or 3 levels http://forge.typo3.org/issues/32034

  * Smaller :p not easy:  Remove FIXME's in FLOW3? LOL

  * http://forge.typo3.org/issues/30584 should be easy and small

  * review: https://review.typo3.org/#change,6681 



*Date of Next meeting: next meeting in around two weeks (5. - 11.
December), use doodle to find exact date.*