**TYPO3 Phoenix Sprint 9: July 2012**
(planned Sprint release: July 27)
**How To Work with this document**
* Please do not add new stories to this sprint
* please only modify this document if you are a Phoenix team member. If you are no phoenix team member, contact us in the #flow3 chat on irc.freenode.net if you want to help out. Then we will find some task for you :-)
* Please link to JIRA issues where they exist.
* in case of bigger modifications to this document or bigger parts finished, write an e-mail to the phoenix core list
* Before working on a task, add a ➜ before the task and add your name behind the task.
* When a task is finished, replace the ➜ with the ✔. Please add a link to the corresponding review request.
* If the review request is merged and everything is done, mark the task using ✔✔
**High level goals as per budget application:** see \url{https://notes.typo3.org/p/PhoenixSprintOctober}
**Related Documents / other Tasks**
\url{https://notes.typo3.org/p/PhoenixSprintMay}
\url{https://notes.typo3.org/p/PhoenixMocSprint}
**Needed FLOW3 Features**
* Custom Configuration files: \url{https://review.typo3.org/#/c/11982/}
-------------------------------
✔✔ **Story: As a user, I want a polished setup process** → Sebastian, Bastian, Aske
* \url{http://forge.typo3.org/issues/33612}
* \url{http://jira.phoenix.typo3.org:8080/browse/PHX-73}
Tasks:
* ✔✔ make checking for FLOW3 requirements at the very beginning of the setup process work
* ✔✔ after the FLOW3 requirements have been checked, display a loading screen while the proxy classes are built
* ✔✔ do not display the initial password, but instead place it in a file in the FLOW3 base directory. Delete this file after the initial login.
* ✔✔ make the database connection settings more robust, fetching the list of databases and testing user/password
* ✔✔ make it possible to create a new database if the user has the rights for it
* ✔✔ Add request handler to avoid using subroutes for setup
* ✔✔ Add custom final setup step with link to the backend
* ✔✔ Update Installation documentation
* \url{http://review.typo3.org/12892}
* (low prio) \url{http://jira.phoenix.typo3.org:8080/browse/PHX-41} - As a System Administrator I want to be asked to create an admin account if no accounts exist yet.
* (low prio) \url{http://jira.phoenix.typo3.org:8080/browse/PHX-43} - As any User, if no site exists I want to be redirected to the Setup wizard
* what happens if there is no database configured or the DB connection failed?
-------------------------------
**✔✔ Story: As Phoenix Release Manager, I want to use Surf and Jenkins for the Release **→ Sebastian
Tasks:
* ✔✔ Build Surf configuration for packaging phoenix release (Sebastian) - \url{http://forge.typo3.org/issues/38500}
* \url{https://review.typo3.org/#/q/topic:38500,n,z}
* Remove/clean up old and deprecated Phing scripts in all phoenix distributions
* ✔✔ Update on Jenkins (Karsten)
* ✔✔ Add the Phoenix release configuration onto Jenkins (Karsten)
* ✔✔ Add Jenkins job (Sebastian)
* **✔✔ **Test a phoenix release, including SourceForge upload and Jenkins
-------------------------------
**Story: As Phoenix Release Manager, I want to assess the quality of the product using Jenkins **→ Rens
-> NOT DONE IN THIS SPRINT.
Tasks:
* PHP Metrics (PMD, Duplicate Code, Code Coverage)
* JSHint
* Explore: JavaScript Unit Tests
-------------------------------
**Story: As Phoenix Developer, I want all external dependencies to be up-to-date and a stable content module **→ Christopher / Rens
-> PREPARED in this sprint, but not yet merged. Will be merged after the sprint release.
Tasks:
* ➜ Aloha Update (Rens)
* sout➜ Build Aloha using its build chain, or use own custom bootstrap (Rens)sout
* RequireJS Update
* \url{https://review.typo3.org/#/c/12116/}We now have a 'working' version with some styling issues, but we're using the jQuery UI update of Aloha already. Not sure if this should be merged
at current state
-------------------------------
**✔✔ Story: As Content Manager, I want a concise and clean Module Overview **→ Aske, Soren
\url{http://jira.phoenix.typo3.org:8080/browse/PHX-112} → navigation pages inside main modules
Tasks:
* ✔✔ Decide on a UI concept that will work for the first basic version (Aske)
* ✔✔ Implement that UI concept
-------------------------------
**Story: As Phoenix Developer, I want a fully testable prototype of VIE integration into editing behavior** → Rens
-> Work in Progress, see: \url{https://github.com/radmiraal/VIE-Emberjs}
Tasks:
* ✔ PhantomJS, JSTestDriver, RequireJS, Jasmine, jQuery, VIE works now in combination
* ✔ Make a standalone version of a page using EmberJS, not relying on Phoenix (Rens)
* ✔ Integrated createjs with VIE
* ✔ Created a 'black manager like' class
* ✔ Started a simple inspector panel
* ➜ Bind the jquery ui editable widget to the block manager
* ➜ Generate VIE Schema Definition from TYPO3 Content Type Definitions (Mattias Nilson is working on this)
* ✔ setup Stanbol server for testing (using the public dev version of IKS)
* Implement VIE widgets (implemented createjs)
* Local Storage
* ✔ Halo Editor / Aloha Editor (Halo is now used)
* Tagging
* ✔ Annotate
* Phoenix Inspector Panel
-------------------------------
**Story: As Content Editor, I want the final content types** → Christian
* \url{http://jira.phoenix.typo3.org:8080/browse/PHX-59}PREPARED, will not be part of this sprint.
*
Tasks:
* ✔ Update Content Type definitions for Text, TextWithImage, Html, Image, Headline (Christian) \url{https://review.typo3.org/#/c/12716/}
* ✔ Implement migration script for the above content type changes (Christian) - \url{https://review.typo3.org/#/c/13073/2}
* ➜ Implement MultiColumn Content Element
* ✔ Implement Menu Content Element \url{https://review.typo3.org/#/c/12716/}
* Explore: Plugin Configuration / Plugin Content Elements
* Explore implementation of ContentReference: on TYPO3CR level or on Content Element type level?
* Implement Video / Audio Content Element (see \url{http://git.typo3.org/FLOW3/Packages/PhoenixDemoTypo3Org.git?a=blob;f=Resources/Private/TypoScripts/homepage/Root.ts2;h=5eb0486cd8ecb525506696edec69c04db46fce24;hb=HEAD#l9} )
**OTHER FEATURES:**
* sout[FEATURE] Package management module - sout\url{southttps://review.typo3.org/#/c/9740/sout}
* sout[TASK] Code clean up to follow coding guide lines - sout\url{southttps://review.typo3.org/#/c/13045/sout}
* sout[FEATURE] Handle content hash scrolling after ajax redirect - sout\url{southttps://review.typo3.org/#/c/12885sout}
* sout[TASK] Make sure ExtDirect errors messages to stay inside box - sout\url{southttps://review.typo3.org/#/c/12889/sout}
* sout[TASK] Launchbar search results should navigation to content (PHX-121) - sout\url{southttps://review.typo3.org/#/c/12886/sout}
---- more long-term:
* Patrick Broens needs a contact point to work on accessibility → Rens
* Management Module Progress (Marc Neuhaus, Sebastian)
------ ANNOUNCEMENT
Today the TYPO3 Phoenix team has released Sprint Release 9, about one month after Sprint Release 8.
In this sprint, we polished existing functionality, in order to provide a stable basis for the upcoming code sprints.
In particular, we focussed on making the Phoenix setup as easy and straightforward as possible. We ship a web based installer now which guides you through the setup process and gives you guidelines on how to set up your environment.
Additionally we improved the backend module infrastructure and layout, and added a basic package management module.
Finally we worked hard to eliminate bugs and glitches in the content editing experience, and worked on the sprint release process.
For the <link \url{https://notes.typo3.org/p/r.E6x1RRh3RtaH1dsq}>next sprint</link>, we'll continue focussing on the editing experience, and also work on implementing the Management module. The next sprint release will be around August 24.
You can download the sprint release from <link \url{http://phoenix.typo3.org/download.html}>phoenix.typo3.org</link>, and check out the <link \url{http://integration.phoenix.typo3.robertlemke.net:8080/}>demo system</link> for trying it out!
For further details on the work done in this sprint, check our <link \url{https://notes.typo3.org/p/r.L5zKJQgjqxUj5K8G}>sprint notes</link>.
TYPO3 Phoenix team.