This document discusses plans for TYPO3 version 6.0. It will include improvements to usability, manageability of extensions, jQuery integration, deployment/updates, and support for mobile devices. The release team is outlined and the schedule and goals are presented. Code sprints are planned to work on specific areas like the backend, security, and continuous integration. The jQuery integration project and extension manager project are described in more detail.

1. T3CON12
Québec City
TYPO3 6.0
BACK TO THE FUTURE 1

2. AGENDA
 New products at the horizon  T YPO3 6.0 Projects (optional)
 FOO 1.0 vs. TYPO3 4.x  jQuery Integration
 Marketing  Extension Manager
 Development
 future versions
 T YPO3 6.0 Overview
 Release Team
 Schedule
 Goals
 Sprints
2

3. STEFFEN RITTER
 Germany, near Frankfurt
 Studied Computer Science
 Freelancer for T YPO3 Development
 T YPO3 since 2006
 Core Team Member
 Release Manager 4.7
3

4. NEW PRODUCTS Why 6.0?
AT THE HORIZON
4

5. T YPO3 6.0 – A NEW VERSION NUMBER
A great discussion arouse around this slide…
5

6. PRODUCT COMPARISON: TODAY
T YPO3 4.x T YPO3 “Phoenix” (Foo 1.0)
 Thousands of Features  Basic feature set
 Thousands of Extensions  No packages/repository yet
 > 50 backend languages  Translation prepared
 CMS with extension  Application framework with
framework small CMS
… …
Different Target  Different concepts  Different Products  Different Name
6

7. MARKETING NEEDS
11 years, 7 years, 9 years,
7 major versions 5 major versions 4 major versions
31 minor 11 minor 17 minor
11 years, 2 major versions , 16 minor
7

8. MARKETING NEEDS
8

9. DEVELOPMENT NEEDS
Matthew Laird Acred
9

10. DEVELOPMENT NEEDS
 new PHP possibilities
 new coding paradigm
 new way of external communication
 new client devices
 new website behavior
 Remove old code
 Change old design decisions
Breaking Changes needed
Major version needed
10

11. NUMBER 5
11

12. FUTURE VERSIONS
LTS ?
12

13. FUTURE VERSIONS
There will be another LTS!
Maintenance Policy still in discussion!
6 month release cycle is fixed!
13

14. An overview
TYPO3 6.0 about the
development
14

15. T YPO3 6.0 - CODENAME
 Back to the Future
15

16. T YPO3 6.0 – RELEASE TEAM
Helmut Susanne Christian
Hummel Moog Kuhn
Skype: Skype: Skype:
helhum susanne.moog christiank.enet
helmut.hummel susanne.moog christian.kuhn
@typo3.org @typo3.org @typo3.org
16

17. T YPO3 6.0 – RELEASE SCHEDULE
17

18. T YPO3 6.0 - GOALS
 Improve Usability  Move towards more
simplicity
 New way to manage
extensions  Infrastructure to monitor
code quality
 jQuery Integration
 Secure the building
 Deployment and Updates
 Let's get into the FLOW
 Support for Mobile Devices
 It's getting cloudy
 External tool integration /
REST API  Revamp the Logging
18

19. T YPO3 6.0 - ORGANIZATION
Inspiring people to share! – Community meetings inspire us…
 No Money for Code! Money for Code -Sprints…
 enthusiasts will join
19

20. T YPO3 6.0 – CODE SPRINTS
 Bootstrap and init.php  Extbase BE Extensions
 THIS WEEKEND!!  End of July
 Backend Usability and UI  Distribution & Packages
 Beginning of July  Mid of August
 Security Sprint  Continuous Integration
 End of July  September
Got your own idea for a TYPO3 6.0 sprint?
Want to organize one yourself? Contact the Release Team… 20

21. A closer look
TYPO3 6.0 - PROJECTS to some
special tasks
21

22. JQUERY INTEGRATION
 Daniel Sattler, Bachelor Thesis
 B13 GmbH, Stuttgart
 Mentored by Benjamin Mack
 “The main goal will be to implement a
robust, extensible integration of jQuer y
in any version and plugin constellation
for the T YPO3 Core.”
22

23. JQUERY INTEGRATION
Infrastructure // Events // Widgets
wild mixture…
23

24. JQUERY INTEGRATION
jQuery: Infrastructure, Events, ExtJS: only “rich”
Effects, uiHelper widgets like
Grid or Tree
24

25. EXTENSION MANAGER
 Susanne Moog
 extbase extension Manager
 New Interface in 4.5
 Old backend-code
 re-implementing old behavior
 No real improvement
 Revamp for 6.0
 Concentrate on “Installing”/”Uninstalling”
 Improved workflows and User Experience
 clean services: reuse the logic
25