**underlineMinutes of the conference call underline**
12.6.2012 10:00h - 12:44h
Karsten Dambekalns, Michael Stucki, Peter Pröll
FOR Responsibilities
Michael is main contact person for your team in the EAB. Peter is also contact.
**Time Schedules**
*Phoenix*
Planned release date for a release candidate: T3CON12 Stuttgart
Planned release date for the final until:
*FLOW3*
1.1 - 19.6.2012
1.2 - Together with Phoenix 1.0
**Current Status**
Based on the Budget Application (Version 3)
Demo Server: \url{http://integration.phoenix.typo3.robertlemke.net:8080/}
*Content View *
* After installation set up a site within the GUI
* includes a “wireframe template” so content is visible and editable immediately (0%)
* Flexible templating support
* for pages and content (100%)
* including inheritance (100%)
* Rich text editing
* full WYSIWYG in the frontend using the Aloha editor (100%)
* internal and external links (50%)
* Support for image use
* upload and placement through the FE editing (50%)
* simple image editing (crop, resize) (100%)
* Support for plugins
* easy use of FLOW3 applications as plugins (100%)
* the ability to place and configure plugins in the FE editing (100%)
* import packages / plugins via browser 0% (Input by EAB - Karsten will give feedback)
* TypoScript support
* Basic TS (100%)
* Object Browser (Input by EAB - Karsten will give feedback)
* Template Analyzer (Input by EAB - Karsten will give feedback)
* Domain-Model support
* render any domain model to a template (0%)
* place domain models on pages using FE editing (0%)
* Launchbar
* search for any editable item (50%)
* quickly invoke actions (50%)
* Workspace support
* editing always happens in personal workspaces (100%)
* publishing to base workspace (can be nested), live workspace (100%)
Overall done (time): about 50%
*Management View*
* Add, edit, remove items
* Domain records
* Content
* Publishing of changes (batch actions and fine-grained control)
Overall done (time): about 30% (but Karsten will give feedback)
*System View*
* User management (50%)
Overall done (time): about 50%
**Naming of Phoenix**
The final name of Phoenix can be inserted easily in the source code and outputs.
**Milestone definitions by EAB**
* Deadline
* Featureset (what is money spent for actually)
* Costs related
Change of milestones:
* Team ACK
* EAB ACK
Karsten will send a milestone planning for the 2nd half of 2012 until end of June.
**EAB strategical plannings for 2013 // Community Fostering FLOW3/Phoenix**
The mid-term goal of the EAB is to not have any paid worktime anymore. That requires a vital developer community. Besides the support of newbies there are no strategical plans by the FLOW3/Phoenix Team. Karsten asks if other teams can support community building (ie. marketing team). Peter tells about the FLOW3-Challange which is initialized by the EAB and will be executed by the marketing team.
Peter will talk to Ben about community building in general.
**Jira**
Jira is available at \url{http://jira.phoenix.typo3.org:8080/secure/TaskBoard.jspa}
Jira is now seen as an experiment. Michael and Karsten agreed to discuss the outcome of this experiment in the focus of having one tool in future (and not two like in Jira and Redmine).
See also:
* \url{http://typo3.org/news/article/starting-signal-for-phoenix-sprint-number-8/}
* \url{http://typo3.org/news/article/typo3-phoenix-and-flow3-march-2012/}
*
**Payment of new team members**
See question from Steffen (\url{http://typo3.org/news/article/typo3-phoenix-and-flow3-may-2012/)}. Some questions are answered by \url{http://typo3.org/news/article/budget-use-in-the-typo3-phoenix-and-flow3-project/} and Karsten is going to write another post.
**Next Meeting**
Doodle invitation: \url{http://www.doodle.com/bhhqd2qvaau3p7gw}