[TYPO3-team-core-v5] TYPO3 Phoenix Weekly Meeting Notes - 27.07.2011

Bastian Waidelich bastian at typo3.org
Thu Jul 28 11:54:50 CEST 2011


TYPO3 Phoenix Weekly Meeting Notes - 27.07.2011, 14:30 - 16:00 CEST

Participants: Robert, Rens, Christian, Sebastian, Christopher, Bastian

Agenda
======

The route to FLOW3 Beta1 // what do we need for this?
=====================================================

BLOCKERS
* Updated documentation http://git.typo3.org/FLOW3/Documentation.git
  If you want to help, please read 
http://git.typo3.org/FLOW3/Documentation.git?a=blob;f=README.txt
  -> Quickstart Tutorial (will be finished by Robert at end of week)
  -> Reference Documentation (convert to ReST, make sure it is correct)
     -> Rens has time to help on Thursday full day
     -> Sebastian can help on Friday, and during next week
     -> Christian has time
     -> Bastian only partly from 1st - 3rd august
  ---> should be split up amongst the team members
* Tutorial should work on all systems
PUBLISHING PROCESS
* How do we publish the beta version?
  -> Update website content
  -> Clearly communicate upcoming annotation changes
  -> Clearly communicate upcoming changes in "cloning of objects / 
updates", changes in behavior of Repositories (finding objects already 
in memory)
  -> Disable localization with Feature Switch 
http://forge.typo3.org/issues/27926
  -> Render documentation
  -> Adjust build / deployment scripts (use SPRINKLE3?)
POSSIBLE RELEASE DATE of beta1: 1-2 weeks from now
TOC: http://db.tt/Ln0306J


T3CON11 papers
==============

TBA


The new FLOW3 Website
=====================

* very reduced website, big letters, unique eye-catchers (on the front 
page: why is FLOW3 so cool?) -> TODO: think about what is unique about FLOW3


Phoenix UI next steps
=====================

* Current status: we can create, edit & delete content
* Still some severe issues with TYPO3CR (with adding, but will also 
occur with copy paste)
* need server-side schema (what properties are available in which node)
* Aiming for a fully usable UI, disable unfinished features via Feature 
Switch (avoid breaking changes)
* Local storage works (closing & opening the browser will restore the state)
Does *not* work yet:
* P1 -- Publishing of changes
* Moving of CEs
** will be implemented with copy & paste rather than drag & drop at first
* P2 -- Editing of page properties
* P3 -- adding new pages
* (Bonus) -- Launch bar - jump to pages
* Tests
* Sebastian will keep issue list in TYPO3CR up to date, Robert will fix them

GIMMICK: http://db.tt/sWzP7Pl


NEXT MEETING: Next Wednesday, 3. August, 14:30 -- 16:00

~~~
Legend:
✔   done
➜   next steps
☠   impediment
ℹ    background info
♫   celebrated


More information about the TYPO3-team-core-v5 mailing list