t3dd06 typo3 5.0 brainstorming results
DESCRIPTION
During the TYPO3 Developer Days in Dietikon, Switzerland two brainstorming sessions for TYPO3 5.0 took place. The slides present the results of these sessions.TRANSCRIPT
5.x brainstormingT3DD06 – 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
TypoScriptPage Tree
Graphic capabilities
Frontend editing
Workspaces
Access control list
Extension M
anager
ExtensibilityPermission system
Highly customizable
idea of TCEforms
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: New features
Unified data accessDifferent storage mechanismNo s
eparat
ion of
BE/FE
better s
eparatio
n of
logic an
d present
ation
TypoShell
Templating API
User mgm for
big portalsStaging / Synchronisationflexible list modulenot dependent onweb context
Form handling /rendering and validation Validation schema
for XML data
Results: New standards to support
SOAP
General object serialization to XML
German Purity Law
TMX (localization standard)
WebDAV
XHTML Open Document
LDAP
iCalJSR 170(for inspiration)
WCAG
Brainstorming:Teamwork
How can the workload be distributed?
How should teams be structured?
How should we communicate?
How do we stay motivated?
Results:Teamwork
Small teams (3-7 members)
Teams reflect what we develop
Team communication interfaces =code API interfaces
Don‘t rely on single
persons -
share the work!
Well communicated team
structures and work results
Frequently change thecoordinator of a team
Tree structur
e of
teams and sub t
eams
Document goals andteam history / culture
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
UI
Core
Ext
ensi
ons
Com
ponents
fundamental functionality
visi
ble
funct
ionalit
ypla
tform
functio
nality
Libraries Features
Architecture
Core Components
Testing Framework Extensions
Management
LoggingTCEmain / Storage Retrieval
Config
RightsVersioning
L10N/I18n
Libraries (Examples)
Asset Mgt
Transformation(Template Engine)
Messaging
Content Analysis
Workflow/BPM
Help System
Synchronisation
Media Manipulation
(Sorry, we did not have more magnets)
Extensions (Examples)
(Random Selection)
WIKI
Task Manager
Shop System
Calendar
News System
Blog
Forum
Image GalleryMail Form Generator
3rd RnD Committee MeetingBerlin 22.-23.rd of June 2006Next steps ...