Workspaces Codesprint 16, 17 and 18th of September 2010 - Wiesbaden¶

Attendees¶

attending¶

1. Sonja Scholz (from friday on)
2. Benni Mack
3. Tolliev Nietsch
4. Oliver Hader
5. Steffen Ritter
6. Michael Klapper
7. Marco Bresch
8. Lars Zimmermann (friday only)

not attending¶

1. Peter Niederlag (available online until friday 12:00)
2. Ben van 't Ende
3. Susanne Moog
4. Mathias Stuebner

Targets¶

The next steps on the way to TYPO3 4.5 are finishing the work we began at the T3DD10. A major task is refactoring the existing code, and working on usability with the TYPO3 design team. On the long run, the goals of the workspace team will be to have a better documentation and to simplify the workspaces feature for everyone, the developer, the administrator and, of course, the end user.

To reach our goals we organize this Code Sprint. If you want to help out developing, documenting or any other kind of support you are highly appreciated to join our forge project and/or team-meeting.

Location¶

AOE media
Borsigstraße 3
65205 Wiesbaden
Germany

see on Google Maps

Agenda¶

We will start at 10:00 CEST in the morning and will be in the office until at least 19:00 in the evening (lunch and coffee breaks included).

Thursday¶

• define the tasks and the workload that will be assigned to a group or person

Friday¶

Saturday¶

Tasks to be done¶

List of issues on Forge

The following points should be finished as core list patches:

High priority¶

• New module accordingly to the discussed screens. Issue (Design) #9472
  • Important: Good new code basis, so further changes are simple and clean - Steffen Ritter thinks about a concept for the code
  • _code basis can be found here: http://github.com/t3dev/typo3v4core/tree/workspace-stages-ng/typo3/sysext/workspace/
• Use user permissions feature
  • Use the permissions of the be_user if no special settings were done in the workspace configuration (functionality is already available by Sonja, only needs to be put in a nice core patch)
• Custom stages feature
  • Make it possible to configure the stages in the workspace configuration (Functionality is already available in custom_stages git - needs to be put in a nice core patch with the new module)
• Cleanup "workspace owners" as discussed during the kickoff
  • Owner and Reviewer should be removed because these roles are no longer needed (Tolliev already has something here)
  • discussion postponed since the behaviour is unclear what the role of owners is concerning custom stages

Low priority¶

• Find a good test concept for new features/changes (Suggestion by Olly)
• How to handle IRRE elements in workspace concept correctly (Suggestion by Olly)
• Discuss about how to visualize that one is currently using workspaces