5.x brainstorming
T3DD06 – Dietikon 11.-13.rd of August 2006

Brainstorming:
Current features
What current features are the most valuable?
What‘s the soul of TYPO3?
What features make TYPO3 unique?

Results:
Current great features

Results:
Current great features
Work
Page Tree Frontend editing
space
s
Graphic
capabi
lities
T ypoS cript Ext
ens
ibilit
Access control list y
ana ger Permission system
nsionM
xte
E of TCEforms customizable
idea H ighly

Brainstorming:
New features
What features which require a radical change do you miss
most?
What standards do we want to support?
What parts of the current architecture cause the biggest
problems?
What components do you imagine for TYPO3 5.0?

Results:
E
/F
New features
BE
Diff Ty poShell
of
eren
access
on
data t stor
ati
Unifi ed a
par
ge m
of
User mgm for
se
ion ion echa
rat tat n
No
epa sen portals ism
r s pre
tte nd Staging big
be a / Synch
ogic flexible ronisatio not depend
l list module n ent on
Tem web contex
pla t
ting A Form handling /
PI
rendering and validation Validation schema
for XML data

Results:
New standards to support
LDAP WCAG General objec
t
serialization to
bDAV XM L
We
S OAP TM
X (l
ocal
izati
on s
tand
XHTML Open Document ard)
JSR 170 iCal
German Pur (for inspiratio
ity Law n)

Brainstorming:
Teamwork
How can the workload be distributed?
How should teams be structured?
How should we communicate?
How do we stay motivated?

Document go
Results: team history
als and
Teamwork / culture
f Teams re
ur eo flect
Small teams tr uct eams
e s sub t
what we
develop
e
Tr and
(3-7 members) s Frequently
t eam coordinato
change t he
r of a team
e pers ons -
rely o n singl ! Team c
ommunic
D on‘t work ation int
sha re the code AP
I interfa
erfaces
=
Well communicated team ces
stru ctures and work results

Development principles
Iterative development
No big jump, but realistic steps with intermediate results
Small steps and frequent results ...
keep us motivated
allow for adjusting the direction based on our experiences
provoce cleaner code and architecture by frequent refactoring

Development principles
Upfront recycle design and radical refactoring
Upfront design for data model and related components
Recycle code from 4.x for the initial components
Radically refactor the new components:
Iterate between adding functionality and refactoring
Use clean and dirty code
Start with clean code based on clean concepts for
fundamental changes
Start with dirty code based for a working prototype

Development principles
100% innovative, 0% backwards compatible
Be free from constraints of earlier TYPO3 versions
Define the soul of TYPO3 and make sure to keep it
Develop a migration path for essential parts (e.g. content).
Develop the migration path already during the development
of 5.0

Joint Development Model
Architecture
fundamental functionality
Core
Co UI
ns
pla
mp
ty
Libraries Features
sio
ali
tfo
on
on
ten
rm
cti
en
fun
Ex
un
ts
ctio
ef
ibl
na
vis
lity

Core Components
Testing
Framework Extensions
Management
Config TCEmain / Logging
Storage Retrieval
Rights
Versioning
L10N/I18n

Libraries (Examples)
Transformation
(Template Engine) Asset Mgt
Workflow/BPM
Messaging Help System
Content Analysis
Synchronisation
Media Manipulation
(Sorry, we did not have more magnets)

Extensions (Examples)
Task Manager
WIKI
News System
Shop System
Calendar
Blog
Forum
Mail Form
Image Gallery Generator
(Random Selection)

3rd RnD Committee Meeting
Next steps ...
Berlin 22.-23.rd of June 2006