[TYPO3-team-core-v5] FLOW3 / Phoenix Planning Meeting -- Notes
Sebastian Kurfürst
sebastian at typo3.org
Wed Nov 23 14:31:27 CET 2011
Now, more nicely formatted hopefully:
*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 ;))
o make sure we send proper cache headers
o ESI support based on Fluid Widgets
o Caching mechanism should not be an ugly hack in bootstrap -> so
bootstrap will be refactored to be very thin
o --> new bootstrap concept
o MVC will also be refactored a little: "Web" and "CLI" in "Mvc"
will be moved away
o --> Robert will continue working on it as soon as Rasmus is gone
and he is not sick anymore
o Performance of AOP Proxy Building can also be improved; Robert
has some ideas about it
o Bastian tries some measures to improve performance on Windows
(different file system, ...)
* [FLOW3] Localization #11954 (Karsten working on it -- quite far
already)
o Label translation / Public API is being polished
o still missing: conventions for XLIFF label keys; concept for
translating command line output
* [FLOW3] Admin Toolbar #30890 (Christian thinking about it, no
implementation yet)
o Christian has some ideas about it, checked some other admin
tools for inspiration (f.e. Symfony); started with a wireframe
o Christian will update the issue
o Coding: in the next two weeks
o Idea of Robert: Generate a "Clover" file for AOP / Security
Policy Inspection --> this could be opened by IDE
o --> Christian
* [FLOW3] Documentation
o Robert: HTTP Kernel
o Karsten: Localization
o Bastian will document stateless widgets & some not yet mentioned
routing features
o 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
o Concept almost ready, can be implemented now
o nice, separate task with clear boundaries
o -> Rens will look into that
* [Phoenix] Management /Other Views: #31639 (!!! for next sprint release)
o Sebastian has created a basic prototype
o We should use subrequest for the management view (different
modules) since most of the management view would be plugins
o No javascript in the beginning, only replace the page reloads
with ajax
o CSS Framework: http://twitter.github.com/bootstrap/ - could be
used for layout of the management view (layout, forms, etc.)
+ Should consult with Berit
o http://html5boilerplate.com/ ?
o Create a system view (user/group management) - create new
backend user, modify users, delete etc.
o (later) Create/integrate a page tree
o -> Aske
* [Phoenix] Rendering Process Refactoring: #31638(Sebastian, Robert,
Christian) (!!! for next sprint release)
o 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?)
o -> Sebastian will continue with discussing this topic --> next
step: TypoScript syntax definition
* [Phoenix] Content Localization: #10515
o --> we'll postpone it to next year
* [Phoenix] Phoenix Sprint Release: #31644
o we want a "phoenix" website (done by Andi), where we can publish
the sprint release
o --> Andi
o Rens: just shout if you need help
* [Phoenix] Links inside text towards other content: #13534
o --> we'll postpone it to next year
* [Phoenix] make Image Size adjustable in UI #30099 (Rens) (!!! for
next sprint release)
o 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)
o --> Rens, next week
* [Phoenix] Refactoring FE / BE communication towards more REST #29987
o --> 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
o 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
o Enabling/disabling "Preview mode"
o 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.*
More information about the TYPO3-team-core-v5
mailing list