TYPO3 marketing sprint
The week long marketing sprint is now one week ago. The marketing team meets this Monday to discuss the results of the marketing sprint as a whole and to plan a sprint to finish marketing material.
Alain Veuve, head of the marketing team, writes about the third day of the marketing sprint in his article “<link http: typo3.org news article marketing-sprint-2013-strategy-workshop>Marketing Sprint 2013: Strategy Workshop”. Alain sees the marketing team as an enabler to gain findings on topics like “What will TYPO3 CMS be in the future?” and “What is TYPO3 CMS for you now?”, besides creating marketing materials like pens and lanyards.
CEBAB (Combined Expert advisory Board And Board meeting)
Every quarter of a year the Board and Expert Advisory Board of the TYPO3 Association meets 'live' to discuss legal, financial and governance topics. Usually the first day the boards meet separately and on the second day there is a combined meeting. Last week's meeting was at <link http: www.flagbit.de>Flagbit's offices in Karlsruhe on Monday and Tuesday November 25, 26. As a community manager I often find myself in a spot between the TYPO3 community and the TYPO3 Association. The community does not always understand the ways of the Association and vice versa the boards are not always aware of what goes on in the community. Until now there was no proper platform for the TYPO3 Association to connect to the community. With this last meeting we plan to change this and I will be present at the quarterly 'live' combined meetings as a representative of the community. In the meeting we agreed I would do some suggestions on how to improve the relationship with the community and give some examples of miscommunication and possible misunderstandings for the next combined meeting that will be prior to the <link http: association.typo3.org general-assembly>General Assembly in Frankfurt on Saturday February 1, 2014. Ingo Schmitt, representing the Budget Control Committee (BCC), was also present at the meeting to talk about invoicing to the TYPO3 Association. A number of things in the process are up for improvement and a number of decisions have been made to make sure the process gets a lot smoother. The meeting itself had it's heated moments, like meetings are known to be. I distinctly got the impression, now the organization structure has settled, everyone is aiming for the same goal supporting the TYPO3 community to do it's thing. Both boards have a public issue tracker, which you might find interesting to have a look at. Public list board: <link http: forge.typo3.org projects t3a-board-public issues>forge.typo3.org/projects/t3a-board-public/issuesPublic list EAB: <link http: forge.typo3.org projects t3a-eab-public issues>forge.typo3.org/projects/t3a-eab-public/issues In the meeting we also discussed diversity in the community and in the boards. There will be <link http: typo3.org news article upcoming-elections-in-the-typo3-association-1>upcoming elections for the TYPO3 Association and I would want to encourage people to nominate themselves for the vacant positions. Nomination is possible until the end of this year. Anyone is eligible for nomination. Don be shy and nominate yourself! Positions are elected directly by the members of the TYPO3 Association. A full report on this CEBAB will be published the coming week. Last report: <link http: typo3.org news article report-from-the-august-cebab-meeting>typo3.org/news/article/report-from-the-august-cebab-meeting/
Extension Development News
Georg Ringer of <link http: typo3.org extensions repository view news>News extension fame reports that he is working on an importer where it is possible to import emails as news entry which is just awesome for editors who are not used to TYPO3. Georg hosts the <link https: github.com georgringer mailtonews>mailtonews extension on Github in the dev phase and warns that is highly in dev mode, only tested with a hot 6.2 and not on many environments. Georg is open to ideas and features.Code sprints
As 'This Week in TYPO3' is written <link http: wiki.typo3.org cms_security_sprint_2013_hamburg>a security code sprint is being held at the <link http: www.e-net.info>e-net offices in Hamburg. The code sprint is about doing incident response and enhancing the security of TYPO3 CMS.
Steffen Ritter, Helmut Hummel, Marc Bastian Heinrichsen, Franz Jahn, Oliver Klee, Christian Kuhn and Anja Leichsenring (Marcus Krause looking through the lens) Thomas Löffler organizes a <link http: wiki.typo3.org code_sprint_ter_stuttgart_2013>TER code sprint surrounding the TYPO3 Extension repository. The Neos team will do <link http: wiki.typo3.org neos_code_sprint_december_2013>one final push towards the release of TYPO3 Neos 1.0, slated for December 10. To celebrate the launch of Neos, <link http: www.netlogix.de>Netlogix organizes a <link http: neosrelease.netlogix.de en>release party. <link http: neosrelease.netlogix.de en>
You can find all future code sprint on the <link events code-sprints>typo3.org code sprint section.
TYPO3 CMS 6.2 LTS
The TYPO3 Community announces the <link news article typo3-cms-4531-4716-6011-and-616-released>versions 4.5.31, 4.7.16, 6.0.11 and 6.1.6 of the TYPO3 Enterprise Content Management System. All versions are maintenance releases and contain bug fixes. For 'This Week in TYPO3' I interviewed Oliver Hader core team leader of TYPO3 CMS, mainly about his participation in the marketing sprint. Especially the Strategy Day, already mentioned above, was significant for the positioning of TYPO3 CMS. Tell us a little bit about yourself.
Hi there, I'm living in Bayreuth in the South of Germany - the city became famous for the traditional and yearly festival of opera composer Richard Wagner.
My involvement in TYPO3 started in 2006 with version 3.8, before I handed in my diploma thesis about the "Inline Relational Record Editing" feature, that has been released in TYPO3 4.1. After that I was elected to be the release manager of version 4.3 in 2008 and became the leader of the Core Team in 2010. I'm mainly working as a freelance web-developer and IT-coach.
What were your thoughts when you got the invitation to the TYPO3 Marketing Sprint Week and especially for the Strategy Workshop?
In general I was very happy and looking forward to that meeting. Most of the active bodies in the TYPO3 ecosystem have a specific scope on their product, but there was no common strategy for all of the product of the TYPO3 family - TYPO3 CMS, Flow and Neos. Thus, having the chance to elaborate on that with other team leaders of the TYPO3 community and marketing experts seemed to be very promising to me.
What were your expectations regarding the workshop?
In 2008 during the Transition Days, which resulted in the Berlin Manifesto, we already have been discussing whether there will be the classic TYPO3 CMS in 2011. Since time passed by and "5.0/Phoenix" was considered to be a separate and new product the will see its first release in December 2013, there's the same question again concerning expectation and acceptance for these products - TYPO3 CMS and TYPO3 Neos. So my main focus was on valuable feedback from agencies and marketing experts on this topic. Besides that I was keen on giving the products a better profile that supports end-users and developers to make the right decision to solve the challenges in the web.
Would you recommend the communication part of the TYPO3 Marketing Sprint Week to other Community Members?
Of course! The first to days with Mark and Scott form OSSwatch have been great and helped a lot to understand and interact our community, our expectations and our tools in terms of communication. The workshop style of the communication part of the sprint week encourage to put the self-reflexive view on various situations and how to deal with those. Insights from the Apache Software Foundation and Ubuntu could be compared and valued to similarities in the TYPO3 Community. What is your outcome of the Strategy Workshop? One of the tasks was to create an art work of the current TYPO3 products and the accordant interaction with the community - now and in five years. I was very excited about the futuristic visions and love towards the classic TYPO3 CMS and that there is still the demand of innovative new feature sets in this mature and robust piece of software. The feedback round on drawbacks and missing features helps us to understand the demands and pointed out specific expectations for the future. We aim to have an additional strategy workshop with the Active Contributors of TYPO3 CMS in cooperation with marketing experts in the spring of 2014.