typo3.org: Latest News

Putting Neos technology into usable form

rasmus@typo3.org — Fri, 17 May 2013 15:00:00 +0200

After gathering user feedback from the alpha version of Neos, we are working on improving both the overall user experience of Neos and the actual interface of the backend. In more broad terms this output is about organizing how all the state-of-the-art technology that have been worked into Neos and Flow can now come to life for all kinds of future uses of Neos. We’re essentially arranging how many years of development will finally interact with our users in an up-to-date manner.

Collectively within the TYPO3 community we have a lot of experience about how content is managed in real-life, about how integrators like to setup sites and about how WCM integrates with all the other components organizations use to publish on the web. All that experience is now flowing into the finalizing of the coming releases Neos.

A user experience master plan

Evaluating the interface of the alpha version of Neos, it’s been clear that we needed to improve the overall user experience and the layout of the interface. To make sure we have some high-level guidelines that can help us fit in all the many features, the team has developed a user experience master plan that formulates the general experience across.

A lot of work has gone into structuring the interface in a way that provides for future changes of how content is managed, how sites are built and how the CMS interfaces with business processes. We want the backend design to be generic enough for a vast amount of different scenarios - ranging from running a small campaign site to the management of multi-site, multi-channel enterprise websites. The overall layout is therefore being improved, providing a logical structure to make sure every conceivable functionality has a natural position in the backend.

Challenge our thoughts on the future of web content management

While we build TYPO3 Neos, we're working very hard to make the features of the releases after 1.0 have logic positions in the backend. We're making room for all what's coming. In that process, we'd love to get feedback on how to prioritize the features for complex web building. Neos.typo3.org/ux explains how to give input to the team.

Call for application interface designers

The Neos team is putting together all the generic design interface specifications into a single reference that will allow future designers and developers to achieve a consistent user experience. If you are an experienced application interface designer, this is a perfect time to help out. Write to Rasmus if you want to get in touch.

Neos and Flow: An update for the team structure

Thu, 16 May 2013 22:31:00 +0200

We, the team working on Neos and Flow, would like to be able to grow. We want to make it easy for new contributors to join us in building the coolest CMS built on our top notch PHP framework. We also want to make sure everyone is recognized for their contributions. It should be natural to recognize both active and inactive contributors while we keep the team at a manageable size. Finally, projects like TYPO3 Neos have plenty of things that need to be organized. Since they've got to be done, we want to give a group of people responsibility for these organizational tasks. To make all of this possible, we have set several groups and roles. With all these requirements in mind, the whole team agreed on an updated structure during the Neos sprint in Karlsruhe this week. You can read all about the updated structure as well as how to become a contributor on a new page we just published on neos.typo3.org.

TYPO3 CMS 6.2 LTS - Kick-Off

ernesto.baschny@typo3.org — Thu, 16 May 2013 15:23:00 +0200

TYPO3's next LTS version will be released in October, 2013 and will be supported for three years thereafter (until October, 2016). It will be a perfect replacement for the 4.5 LTS release, which will expire in October, 2014. The umbrella goals for the 6.2 LTS (Long Term Support) TYPO3 release are:

Smooth Migration
User Happiness
Robust, Stable and Secure Foundation
Modern Technologies / Interoperability

Being an LTS means special consideration during the development. It means to us that we don't want to add any experimental feature which could be an obstacle for the further development of TYPO3 CMS after 6.2. On the other hand we want to make sure the base is future proof because we will have to "carry it on" for at least three years to come. We have gained some experience with solving this situation during the development of the last LTS (4.5) - which was and still is a huge success - and are able to transpose this knowledge to the development of 6.2 LTS. Some realistic details of what we plan to finish to realize these goals:

Smooth Migration (from 4.5 LTS to 6.2 LTS)

We know about the huge 4.5 LTS user-base. Let those be able to migrate to the new modern code-base as easy as possible.

Identify and solve and/or document all migration issues
Migration "Checklist" for integrators
PHP Support: 5.3 (above 5.3.7) and 5.4
Upgrade Check Extension
- Install on 4.5 and see what "could break" on Upgrade to 6.2 LTS
Compatibility Extension
- Install on 6.2 and provide a layer emulating 4.5 functionality (to allow running legacy Extensions on 6.2)
Potentially a PHP Code Migration Tool (to ease upgrade of extensions)

User Happiness

We want to work on the product from the users point of view (customer, agency, integrator).
Making their experience fun and consistent should guide our efforts.

Usability Improvements
- Design Foundation (TYPO3 Backend Style / Layout Guide)
Ship Production Environment
- "Fast" by default
- Don't annoy users that are not developers (i.e. deprecation log "off" by default)
Install Tool goodies
- Configure and Solve problems as much as possible automatically
- Robust: no Fatal, also works with "broken" Extensions installed

Robust, Stable and Secure Foundation

The groundwork of TYPO3 should be modern, but still realistic and timeless.
Let's finish the "last 20%" for important loose ends.

File Abstraction Layer
- Missing features
- Robust integration
Media Extension (DAM)
- Not shipped with Core, but still important as a "DAM" replacement
- Allow easy migration from "TYPO3 4.5 + DAM" to "TYPO3 6.2 + FAL + Media"
Extbase Improvements
- Support read only Workspace and Localization
Workspaces for IRRE and MM Records
Salted Passwords enforced

Modern Technologies / Interoperability

We are well aware of what's going on in the PHP world and Web technologies in general.
Keep TYPO3 in sync with modern technologies, but avoid "experiments" in the LTS.

Package Manager supporting Composer Packages
JavaScript unification (less Prototype / Scriptaculous, more jQuery)
UUID for records
Logging API
Functional Testing Framework

Groundwork

The development of TYPO3 6.2 LTS already started long before the actual kick off. During the development phase of 6.0 and 6.1 many groundwork was laid paving our way to a rock stable foundation. This work will continue to have the loose ends finished for the release of 6.2 LTS in October, 2013.

One important change to achieve the desired goals has been the restructuring of the Core Team which started during 2012 and was finished by the Team Leader during the Active Contributor Meeting in Nürnberg: The Core Team is more dynamic, vibrant, active and motivated than it has been for a long time. New developers which proved their talents during the last years can now participate more actively in crafting the beloved CMS. Refer to the news article documenting this change.

Kick Off

The Kick-Off for TYPO3 6.2 took place during the Active Contributors meeting in Nürnberg in May, 2013. The tasks and main areas of work for the 6.2 release were identified as listed above. To organize the required work, we introduced initiatives and defined the groups / persons responsible for each individual area.

This allows all contributors to know where to lay the focus of development in the next months and helps new potential contributors to know whom to contact about an area of interest. The Release Manager will keep the strings together by having an overview of what is happening throughout the initiatives and also interacting with further teams (Design, Usability, Documentation, Marketing, Server, Security).

Release Manager

Ernesto Baschny was nominated and elected amongst the Active Contributors to take over the job of Release Manager for 6.2 LTS. He has been working on the TYPO3 CMS Core for the past nine years and was also the Release Manager of the last (and first) TYPO3 LTS (4.5). He'll try to make good use of his experience of having worked on a LTS before.

Information Channels

Keep yourself informed through the following channels, mainly:

Get news (and our roadmap) through the
Forge Project: http://forge.typo3.org/projects/typo3cms-v62
Discuss through
Mailing List / Newsgroup: typo3.teams.core / Forum: http://forum.typo3.org/index.php/f/18/
Get informed, praise and rant using
Twitter Hashtag: #TYPO3LTS

Your further wishes

This is an open source project: interests and activity of contributors might shift over time. The Core Team is pretty sure we can achieve the above mentioned goals, but this does not mean that we are not open for further initiatives or projects. The Active Contributors are volunteers working with heart and dedication on projects with whom they identify themselves. Still there is room for sponsorship of other features or initiatives. If you are interested in sponsoring or getting some other project realized, get in touch with the Release Manager Ernesto Baschny (ernesto.baschny@typo3.org).

TYPO3 CMS 4.5.26, 4.7.11 and 6.0.5 released

benni@typo3.org — Fri, 03 May 2013 13:20:00 +0200

We are announcing the release of the following TYPO3 CMS updates:

TYPO3 CMS 4.5.26
TYPO3 CMS 4.7.11
TYPO3 CMS 6.0.5

All versions are maintenance releases and contain bug fixes. For details about the releases, please visit the following websites:

http://wiki.typo3.org/TYPO3_4.5.26
http://wiki.typo3.org/TYPO3_4.7.11
http://wiki.typo3.org/TYPO3_6.0.5

MD5 checksums:

d9906add82d38bb9d7db589c24f5c888  blankpackage-4.5.26.tar.gz f5e832f8d566501ab60a6a885ea38918  blankpackage-4.5.26.zip 77dde86133919ac6273aee9d9f2de02a  dummy-4.5.26.tar.gz 70f0e46153b8fe39d2b0ea5dfc3f33f1  dummy-4.5.26.zip c6896c72bb43a471c3c236e4d327d402  introductionpackage-4.5.26.tar.gz a132963e4d996e1010b684c4f5cc329e  introductionpackage-4.5.26.zip 307ebab8e4b4b3e033556aae95b044ee  typo3_src+dummy-4.5.26.zip 06cb7852c5c471b62e43f97926520835  typo3_src-4.5.26.tar.gz 3563d5b76f761f33cda29ceb1c7e7f97  typo3_src-4.5.26.zip

b25417bb73e6900369546d9236f18621  blankpackage-4.7.11.tar.gz 681fa082f22e372a1d65dd87d1d049d5  blankpackage-4.7.11.zip f5f60d28de3201be449c908a304f31b1  dummy-4.7.11.tar.gz d0fd73ac90fa76cee9e6c28fa91ac9aa  dummy-4.7.11.zip 9e71432aac621b3a3e134dc38f5c931e  typo3_src+dummy-4.7.11.zip f01345aa7da876d19c0faf4b45ff885a  typo3_src-4.7.11.tar.gz cedb903c427222c66181339ef7819c74  typo3_src-4.7.11.zip

266a46064648faa00145efaffada4aae  blankpackage-6.0.5.tar.gz 07c171c8caa7d77d425b4f28606e8924  blankpackage-6.0.5.zip 593025ee397dc5a0b917805d541aeb58  dummy-6.0.5.tar.gz e02dd712dc795a41352b3f25a4b38fa2  dummy-6.0.5.zip 96768a1efe6f65e500ac19a6f66d7035  typo3_src+dummy-6.0.5.zip b37620d591d57332e1791bdcf1bd4396  typo3_src-6.0.5.tar.gz 85b6e5b92cb59358826d08f082dfb64c  typo3_src-6.0.5.zip

Download: http://typo3.org/download/

TYPO3 CMS: Core development roles and groups

oliver.hader@typo3.org — Thu, 02 May 2013 20:00:00 +0200

Introduction

The diversity between the current developers of the TYPO3 CMS Core, the Neos and Flow Team and the subteams (Extbase, Linkvalidator, Workspaces...) has become huge since the Core Team itself was instantiated back in 2002 by Kasper. The original Core Team was meant to be a group of people who fully understand the TYPO3 Core code and the principles of high quality, backwards-compatibility and extensibility.

Today, we have Git, submodules, Forge and Gerrit - instead of CVS, a closed core-mailing list and Mantis in earlier days. We face a lot of issues due to the fact that the current team structure still exists but grew, although a lot of the surrounding circumstances have changed.

During last year (2012), the TYPO3 CMS Team Leadership realized that there should be a bigger change within the team in order to overcome the current obstacles when pushing TYPO3 CMS further:

Slow development speed due to lacking reviews of Core developers
Little steering, mainly due to the fact that developers, especially when being Core Team members are highly demanded persons.
Since there is the parallel development of TYPO3 Flow and TYPO3 Neos (previously known as 5.0 or Phoenix), there was no understanding how the next version of TYPO3 CMS should be shaped until late last year.
TYPO3 Research & Development Committee does not exist anymore to take care of the visionary part in the TYPO3 project.

Additionally a new structure should address the following issues:

The big Core Team of 40+ people with the focus on multiple products is very inflexible in discussing, making and taking decisions in what direction the TYPO3 CMS should go to, as the focus of each person is different
There are a lot of regular, active contributors that have already earned the status to become a Core Team member, and as they know the code even better in some regions as Core Team members, they should have merge rights - at least for these areas.
A better working mode in order to reflect actual activity of all contributors, and to speed up development.
When coding, "Trust" is an important factor - self-discipline and mentoring others - should be even more important than hard rules.
The existence of the Core Team is not just about making regular releases but also to support the future of the product. It is about planning the product and guiding contributors in the right direction instead of simply maintaining an already full-feature product.
The Core Team itself should be about coding, but also about responsibility. Every Core Team member has privileges, but more important: has responsibilities and jobs that are crucial for the future of the product.

Restructuring the team

To address these issues, the following proposal has been presented to the current team. It aims to restructure the Core Team and the TYPO3 CMS development by opening up the development and introduce more and larger "groups" to the development process.

Roles and groups

There are several positions in the TYPO3 CMS project that exist already for a longer time. However, it’s currently not fully transparent whom to ask on particular topics and who takes care of a specific field of responsibility.

Basically there will be these roles and groups in the end:

Contributor
Active Contributor
CMS Team Member
CMS Team Leader
CMS Team Co-Leader
CMS Team Quality Manager
Budget Manager
Release Manager
Release Team

Find detailed overview and description for each section in the roles and groups section of the TYPO3 CMS Core Development area.

Further changes

Trust-based development / New areas of expertise

The TYPO3 CMS Core has a lot of different areas. Right now no individual contributor or Core Team member knows every area of code by heart. This often makes it really hard to decide on how to proceed when it comes to specialized code areas.

As we have the subteams (i.e. Extbase, DBAL and Workspaces), where experts work together and know their area, the rest of the TYPO3 CMS Core could be split up like this as well. With the new “Active Contributor” role, a lot of people will have merge rights. In order to assure the quality, each contributor has to really consider whether a particular change will break existing functionality (especially in other areas).

Therefore each area (i.e. Extbase, FAL, Installer, Caching, Inline Editing, Javascript Frameworks, etc.) should have a group of people who are responsible for the further development of the code, and they should connect to the Release Manager about features for the next version.

In reality, some areas already work informally like this. More areas will be defined by the TYPO3 CMS Team Leader, and responsible groups of Contributors will be defined for certain areas.

Like before, new code should follow these premises:

Each change-set shall pass the “4-eyes-principle” and thus have two other reviewers, at least one of them needs to be an Active Contributor (this will not be enforced technically, but shall be the basic principle of the review process)
Each merge must be fully tested and additionally covered by unit-tests to avoid future misbehaviours as far as possible
Every developer, but also every merger is responsible for those own changes
If there is a responsible person / group for an area, this person needs to approve bigger changes to still meet the concept
Any contributor is encouraged to do post-merge reviews, too

The future existence of the current sub-teams

The consequences for the subteams like DBAL, Workspace/Version, Linkvalidator, Extbase/Fluid will look like this:

the submodules will be resolved to the main Git repository
all of the external contributors will be Active Contributors and gain trust for their current area of expertise. However, they can merge changes in the whole core. This makes it easier to create one patch that modifies code in multiple areas or introduce new APIs that should be used.

While this opens up many new possibilities it clarifies what the trust-based working mode is all about.

Communication channels

Just as the “old” Core Team has done it in the past years , there will be at least one real-life TYPO3 Active Contributor Meeting (T3ACME) each year. The Team Lead will organize these meetings. Active Contributors should meet each 2-4 weeks via Skype / Google Hangout or similar technique, and all CMS Team Members are required to participate regularly in these meetings. A protocol of each meeting will be published before the next meeting to the “Core List”. These online meetings are public and may be joined by other interested listeners.

Apart from these channels, the “Core List” will stay the main communication area to present and discuss strategic changes to the TYPO3 Core. The smaller groups for smaller parts of the Core can define their own way of communication, but regular status posts on the Core List about the current state are desirable.

Consequences

The next steps are:

The role of Active Contributors is created. Merge permission is granted to each current Core Team Member automatically. Current Active Contributors are invited by Olly.
All(!) existing Core Team Members will have the status of an Active Contributor.
The election phase will be set up (ideally done by someone from the EAB), all Active Contributors can nominate candidates for being the team lead. After a phase of two weeks, the election info will be sent to all active contributors in a private voting process.
Since the budget granted by the association is managed and given to a specific budget responsible (currently Ernesto), this position can’t be touched for the current year.

There will be a new election for the CMS Team Leader. Once done, he will take care of adapting Forge and Gerrit.

Progression

This restructuring process has been discussed internally since November 2012 and for at least four weeks publicly on the core mailing list in April 2013. Furthermore it is a result out of a Google Document that has been commented and modified concerning all contributions and questions. The TYPO3 Expert Advisory Team has been informed about the planned changes as well. The first meeting will be at the TYPO3 Active Contributor Meeting 2013 in Nuremberg which lasts from May 3rd to 5th 2013.

TYPO3 Flow 2.0 beta 3 has been released

karsten@typo3.org — Thu, 02 May 2013 17:51:00 +0200

The fixed bugs touch role handling and lazy dependency injection, caused by recent changes, as well as some other issues. One of the last changes for beta 3 are changed dependencies and stability settings for composer. This should speed up install and update actions through composer, because it enables the use of archives for fetching dependencies. Read the release notes for Flow 2.0 beta 3 on http://flow.typo3.org/download/release-notes/flow-2-0.html for more information.

TYPO3 CMS 6.1 released

benni@typo3.org — Tue, 30 Apr 2013 16:48:00 +0200

After a groundbreaking and successful milestone release of TYPO3 CMS 6.0 in November 2012, the next step was naturally to build on this foundation and focus on stability and consistency through the code-base and the user-interface. With over 570 contributions in this development phase, a lot of finetuning was done in mostly the following areas. The Database Connection class, the layer between the raw PHP functions for connecting to MySQL (or via DBAL to other database platforms) has used PHPs built-in module "mysql", which is available since PHP 2.0 (= almost forever ;-)). Since PHP 5.0 this module has been superseeded by the shipped-by-default module "mysqli" (note the "i" at the end), which is the recommended database connection API for mysql (see php.net). TYPO3 CMS 6.1 now uses the mysqli API. Extensions that use the Database Connection layer correctly should not notice any difference. The File Abstraction Layer, the unified handling for working with files throughout the TYPO3 system, has had its difficulties in handling the deletion of a file that was still in use. This issue was solved in a clean way. When indexing new, replaced or modified files the indexing service detects these changes easier. The Extension Manager module - the heart of the extension maintainability - was code-wise ported to Extbase/Fluid for TYPO3 CMS 6.0, thus separating the visual output (Fluid) from the logic and the DB and TER handling (done in Extbase). However, the UI of the module was not completely integrated in the Backend interface. The look & feel was therefore adapted to conform to the user experience defaults that are common in other modules, making it easier and more comfortable to use. Detailed information about more changes can be found in the release notes. The packages can be found on the download page of TYPO3.org. The next version, the long-term-support version TYPO3 CMS 6.2, is already in development phase and scheduled for October 2013. Finally, BIG thanks go to all supporters, contributors and organizers in the last months to make this release possible.

End of life for TYPO3 4.6 - support for TYPO3 4.7 extended

oliver.hader@typo3.org — Tue, 30 Apr 2013 10:30:00 +0200

The long term support release TYPO3 CMS 4.5 is still supported with critical bug-fixes and security issues, while version 4.6 is now the first release no further bug-fixes will be applied to, even its codebase is younger. Systems that are currently using TYPO3 CMS 4.6 should be upgraded to the stable TYPO3 CMS 6.1.

TYPO3 CMS 4.6 became famous for important changes like the enabled caching framework, an optimized and faster Fluid rendering and the transition to XLIFF for localization handling, including the new translation server back then. Special thanks goes to our release manager of 4.6 Xavier Perseguers for managing and maintaining a TYPO3 version known for its stability and reliability.

By the same terms, TYPO3 CMS "old stable" 4.7 now reaches the end of full maintenance concerning regular bug-fixes. This means, only priority bug-fixes and security issues will be considered. However, we are proud to announce that this period of usually six months, now officially gets extended to 12 months in total. Special thanks go to TYPO3 Association Member m project Market Relations (Frankfurt/DE) for sponsoring the porting of security fixes and accordant release management in TYPO3 CMS 4.7 for the additional period from October 2013 to April 2014. On behalf of the TYPO3 CMS Release Team

TYPO3 Community March 2013

ben.vantende@typo3.org — Sun, 28 Apr 2013 21:04:00 +0200

TYPO3 CMS 6.1 - Improve

Simultaneously with the typo3.org code sprint there was a code sprint dedicate to the File Abstraction Layer. The FAL project was initiated years ago under the umbrella of the BLE project. Financed by a budget by the Bundesanstalt für Landwirtschaft und Ernährung FAL was one of the projects done to improve the usability of TYPO3. The basic idea of FAL is to have a DB driven layer between TYPO3 and your assets. Utilizing this will open up completely new possibilities like displaying usage information on a file or to deny users to delete a file which is used somewhere on the website and connectors to cloud storage. The antivirus software company G Data Software AG hosted this sprint in Bochum. There were a lot of different areas the team worked on, each developer had his/her own speciality and field to contribute to. some of these areas included: Media Gallery - an Extension that ships with a Frontend Extbase plugin to show FAL / media elements in a gallery, collection handling, improving usability, an external WebDAV driver and some smaller topics like "How do I delete file?" and "what is the correct default upload folder?" were identified and solved. There was one alpha release in March followed by two in April. The following noteworthy changes have been introduced in the alpha and beta releases: The main database connection class (formerly known as TYPO3_DB) now uses "mysqli" instead of the old "mysql" PHP extension, RequireJS has been introduced, the Caching Framework has now an additional XCache Cache Backend and of course 3rd party libraries were updated. Final release of TYPO3 CMS 6.1 is to be expected on April 30, coinciding with Kingsday in the Netherlands. News-item: http://typo3.org/news/article/coding-for-a-better-61-in-bochum-fal-code-sprint/
News-item: http://typo3.org/news/article/typo3-cms-61-alpha-1-released/
News-item: http://typo3.org/news/article/typo3-cms-610-beta-1-released/

Google Summer of Code

TYPO3 has been accepted as a mentoring organization in Google Summer of Code 2013. This is the 4th year we participate. Google Summer of Code is a global program that offers students stipends to write code for open source projects. TYPO3 is currently preparing the applications. You are invited to help in this by becoming mentors and by sharing your ideas for projects. Previously, we had some very successful summers of code and we hope to repeat the same again this year. Website: http://typo3.org/projects/google-summer-of-code/
WIKI: http://wiki.typo3.org/Gsoc2013
News-item: http://typo3.org/news/article/typo3-accepted-for-google-summer-of-code-2013/

CMS-Garden at CeBIT (March 6-9, Hannover)

TYPO3 together with the most relevant Open Source Content Management Systems, like Contao, Drupal, Joomla, OpenCMS and Plone presented itself in the CMS-GARDEN at CeBIT 2013 from March 6 to 9. A group of people from these Open Source CMS communities worked together to bring the event to life. CMS-Garden is there to promote dialog between the CMS communities. The projects shared a common booth where every CMS had one dedicated monitor to display a demo of it’s CMS. Representatives of the projects were dressed in gardner fashion, which made quite a distinction from the overall very business like presentation of the other IT projects at CeBIT and got quite some attention. You can also visit the CMS-Garden at Linux Tag and FROSCON. CMS-Garden is currently attempting to secure a booth at OSCON, Portland and will undoubtedly be present at FOSDEM, Brussels next year. Website: http://www.cms-garden.org

Code sprint typo3.org (March 21-24, Wiesbaden)

From March 21 -24 there was another sprint for typo3.org at the aoe offices in Wiesbaden. The code sprints for typo3.org are done on a regular basis, which is quite necessary with such a complex website. With this code sprint we have arrived at a stable point where most bugs have been solved and we can start thinking of new features and a news responsive relaunch. The next code sprints will definitely be dedicated to that. If you want to participate in the maintenance team that is at the core of the typo3.org code sprints the write a mail to info@typo3.org clearly stating your expertise and in what area you would want to participate. One of the areas that need attention is user management of the registered users on typo3.org. Currently there is not much interaction with the 60.000+ registered users and there are some ideas floating around about what possible new features can be. News-item: http://typo3.org/news/article/what-did-the-guys-do-at-the-last-typo3org-code-sprint/

TYPO3camp Denmark (March 15, Ballerup)

TYPO3camp Denmark was great! 50 people gathered for one full day of talks, with subjects like "TYPO3 as third party CMS for social media", "How to contribute to TYPO3 and it's projects", (the obvious) "Neos" talk, general talk about Domain Driven Design "The domain event", "SEO in TYPO3" and "Advanced forms with TYPO3 Extbase". The Danish insurance company Topdanmark sponsored the location, lunch, drinks and have welcomed this event for next year as well - they got a great insight into where TYPO3 is heading. A great mixture of people with great knowledge and new people were gathered that day. Finished of with a beer and food in Copenhagen and a "see you next time"! Website: http://www.typo3danmark.dk/

TYPO3camp Venlo (March 9-10, Venlo, Netherlands)

At the first TYPO3camp this year and the first TYPO3camp in the Netherlands there was a nice cross-section of the TYPO3 community with representatives from the TYPO3 Association, TYPO3 teams and some international visitors. There was a great constructive feeling at the TYPO3camp Venlo and outside of the sessions there were quite some meetings and discussions going on about current developments within the TYPO3 family. Meeting face to face is important to touch base on what is going on and to ensure progress. Website: http://www.typo3campvenlo.nl/en/
News-item: http://typo3.org/news/article/typo3camp-venlo/

Coming events

North American TYPO3 conference (May 30-31, San Francisco)

The Fifth North American TYPO3 Conference (T3CON NA) will take place from May 30-31, 2013 in San Francisco, California. Held at the Golden Gate Club in The Presidio of San Francisco, this year's conference will allow TYPO3 experts and those interested in TYPO3 to share all aspects of the current state of development and implementations of this worldwide market-leading Content Management System (CMS). Website: http://t3con-na.typo3.org/

T3UNI (June 24-27, Annecy, France)

The program of the French T3UNI for this year will return to “TYPO3 initiation and discovery" targeting our beginner audience and customers curious about TYPO3. The event aims to share the passion and it is with pleasure that we offer this university surrounding to share our experience with you all. T3UNI13 will feature technical presentations and satisfy even the most demanding guests. Website: http://t3uni.typo3-fr.org/

Developer Days (July 4-7, Hamburg)

The eighth edition of the TYPO3 Developer Days will take place from July 4 - 7, 2013 at ELBCAMPUS, Hamburg, Germany. The Developer Days 2013 will feature workshops, tutorials, the coding night and the social event. Of course we will have some surprises in store for you as well. The Call for Workshops and Tutorials (Call for Papers) will also start on April 2 when the site goes live. We will continue the "Getting Things Done" approach we had on previous Developer Days. This year’s slogan will be "Getting together to make it happen!". T3DD13 will be a great way for you to get in touch with the developer community, to meet core devs, to learn and to contribute to the TYPO3 project in the many workshops dedicated to either TYPO3 CMS, Flow and Neos Website: http://t3dd13.typo3.org/

European TYPO3 conference (October 29-31, Stuttgart)

The European TYPO3 conference for 2013 will have more focus on business and companies. For the first time we offer the possibility to order one-day tickets. Each day will be dedicated to a special theme and each day will also have talks focused on TYPO3 CMS and TYPO3 Neos. One slot per day will be dedicated to the following four subjects: General, Technical, CMS and Neos. Ticket sale has already started with a “Friends of the Conference” ticket program. The conference website will go live in the beginning of May. News-item: http://typo3.org/news/article/european-typo3-conference-2013/ Check out the events section on the typo3.org homepage to find an event in your area.

Report on the Extbase Codesprint 2013 Munich

anja.leichsenring@typo3.org — Sat, 27 Apr 2013 09:26:00 +0200

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.

Participants

Alexander Schnitzler
Andreas Wolf
Anja Leichsenring
Benny Bretz
Christian Kuhn
Danijela Grgic
Felix Oertel
Georg Ringer
Lars Peipmann
Marc Bastian Heinrichs
Oliver Hader
Rony Khoury
Robert Weißgraeber
Stefan Froemken
Thomas Maroschik
Tymoteusz Motylewski
Wouter Wolters

We 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 Bugfixes

Put 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/12
Backport current property mapper from Flow: https://review.typo3.org/19906
And many more...

“Tie-compatible” chart from Chartbreeze, which we used for tracking progress:

Decisions & Work in Progress

Resources & new Features vs. Generic Persistence

Since 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.

Workspaces

For the same reason as above, Extbase will not provide fully-fetches workspaces support in 6.1 or 6.2.

Language Handling

We 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 Support

We 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 Example

Due 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 Stuff

Composer Support

Tom 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_Teammeeting_next)

Miscellaneous

Core Team restructuring: Discussions on details on being more open and flexible for contributors and establishing the role of TYPO3 Active Contributors
Some discussions on the far future, including ideas for a task-based UI, CQRS

Documentation

The 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/drafts/github/froemken/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 the attempt to finish Extbase 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 organisation
Sweets are covered by Claus Due
@robert_we provided 2 beer crates
Patrick Lobacher provided 2 beer crates
Lightwerk 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)