Report on the Extbase Codesprint 2013 Munich

[RSS Bot]

The second code sprint of the TYPO3 Extbase Team for this year took place last weekend (12/04 - 14/04/2013) in Munich at typovision GmbH’s new office. The Extbase Team and others met as a large group (17 people) for three days, focusing on finishing issues to get Extbase (and some other things) ready for the TYPO3 CMS 6.1 release.ParticipantsAlexander SchnitzlerAndreas WolfAnja LeichsenringBenny BretzChristian KuhnDanijela GrgicFelix OertelGeorg RingerLars PeipmannMarc Bastian HeinrichsOliver HaderRhony KhouryRobert WeissgraeberStefan FroemkenThomas MaroschikTymoteusz MotylewskiWouter WoltersWe especially welcome our new contributors and are looking forward to seeing them and their contributions again.Additional remote contributions where provided by Frans Saris and Stefan Neufeind.Important BugfixesPut into numbers, we closed a total of 95 tickets, the oldest ones being around 3 years, the newest 7 minutes ;-). Lots of side issues were also solved by fixing the new property mapper.A lot of issues are now ready for final review as well, and we would be happy to find some more testers to get them merged.During the weekend a total of 50 Patches were merged and backported to the stable branches as required.In passing, some TYPO3 Core issues were also fixed, but the constant submodule pointer raises spoil all statistics in this regard.Worth mentioning:In the area of MM relations: https://review.typo3.org/#/c/3390/Caching Layer for getTargetPidByPlugin https://review.typo3.org/#/c/19821/Translate validator errors: https://review.typo3.org/#/c/16544/12Backport current property mapper from Flow: https://review.typo3.org/19906And many more...“Tie-compatible” chart from Chartbreeze, which we used for tracking progress:Decisions & Work in ProgressResources & new Features vs. Generic PersistenceSince we are planning on moving to a new Persistence and we absolutely want to deliver a super-stable release for 6.2 LTS, we decided to focus our limited resources on fixing existing issues instead of providing new features. Therefore, a bunch of issues were rejected.WorkspacesFor the same reason as above, Extbase will not provide fully-fetches workspaces support in 6.1 or 6.2.Language HandlingWe also started rewriting the Extbase language handling, to provide working solutions for the default TYPO3 CMS language handling cases. Beyond that, we pulled apart persistence and language handling, since these things should be conceptually separated.The implemented services will be extendable without modifying the core, if custom language handling is needed.MySQL SupportWe now officially only support MySQL (obviously MariaDB as well, but without explicitly being tested). Like the workspace support, this is just our way of using our limited resources, and not opening new large issues which we cannot commit to for 6.2.Blog ExampleDue to lack of interested (developer side) we announce the Blog Example as "finished". As intended, it provides examples of Extbase usage. It is not - and was never planned as - a working extension for usage in a production environment - so, there is no need to implement features for that sake.Interesting StuffComposer Supportom provided his first patchsets for composer support for the TYPO3 package manager. This is of course considered to be a work in progress, but we are heavily looking for advanced testers. Please contact Anja Leichsenring or Felix Oertel, if you want to help out, more info will follow after the 6.1 release. (Or, join us at one of our teammeetings, which are public: https://notes.typo3.org/p/Extbase_Te...cellaneousCore Team restructuring: Discussions on details on being more open and flexible for contributors and establishing the role of TYPO3 Active ContributorsSome discussions on the far future, including ideas for a task-based UI, CQRSDocumentationThe Extbase documentation received a real activity boost by moving to ReST. The current status, that is still a work in progress, can be viewed on docs.typo3.org: http://docs.typo3.org/typo3cms/draft.../ExtbaseGuide/ . Contributors are welcome to push their changes to GitHub: https://github.com/froemken/typo3-extbase-guide/The Future looks good!We are really happy to have an active and large team working well together. The next code sprint will be in %TODO% where the attempt to finish Extbase will be tried again ;-).Thanks to all participants and our host typovision, who make the code sprint possible and for the continued focus on improving TYPO3 CMS.Special thanks to Alex Schnitzler for taking care of food, beverages, administrative stuff and enabling us to have a real productive and enjoyable codesprint.Furthermore we thank our sponsors:Accommodation and travel costs are covered through the Extbase Codesprint Budget.Our working place is sponsored by the typovision GmbH and also all the drinks, the daily breakfast for both days and some sweets. Thx a lot @ typovision!Lightwerk Gmbh and typovision GmbH for the organisationSweets are covered by Claus Due@robert_we provided 2 beer cratesPatrick Lobacher provided 2 beer cratesLightwerk Gmbh for sending 4 people (paying working hours and travel costs)Cyberhouse GmbH for sending Georg Ringer (paying working hours and travelcosts)WIND Internet for sending Wouter Wolters (paying working hours)

More...