#Meeting Point: Skype as helhum, if you aren't in the conference! ((temporary notes: * Martin Bless: I will have time from 8.00 until 8.30 today only )) ##Dates to watch: Release date of TYPO3 version 6.0: **2012-11-27** #Motivation TYPO3 6.0 is around the corner and it's not only the Core Team that as some work to do. We'd like to coordinate with all the other affected teams to have the best release ever! #Agenda 1. Present the current state and plans (Helmut Hummel) 1. Go through the list of teams and their working packages (max 10min/team) 1. Set up next meeting, if necessarry ## #Working packages ## Feel free to add potential work packages for your team or other teams. Please put **your** name next to it! If you feel that your team was forgotten, just add yourself here, please! ##Release Team Delegates: Helmut Hummel, Oliver Hader, Christian Kuhn, Susanne Moog, ... * Prepare keywords for the article for press ## ##Documentation Team ## Delegate: Martin.Bless@typo3.org (8.00 - 8.30 only) Rest Documentation Rendering will be ReST based Rendering Separate meeting on that topic (Documentation Team, typo3.org Team, Marketing Team). Steffen j emails to everybody involved. * Update manualsthe manuals - as they were migrated to ReST - need quite a bit of human, manual care. This takes a lot of time. We will try to "clean up" the manuals before updating them, but if time runs out we will make sure that they are at least up to date. The main drawbacks of an unfinished cleanup are that URLs to the various pages will not be final and that permalinks will not be available everywhere they should. But we will make sure to have at least up to date manuals and will highlight the beta state of the documentation if needed. we also have to measure the impact of the rebranding. Since we only have TYPO3 CMS documentation of the docs server for now, the impact should be limited. We still have to review our naming scheme. * Set up server docs.typo3.orgEnable this server to render our manuals assigned to: Fabien Udriot, Martin Bless, François Suter -> \url{https://forge.typo3.org/projects/team-doc-rendering/issues} and \url{https://forge.typo3.org/projects/team-doc-infrastructure} * Replace links to the old manuals on typo3.org (we currently do not have access to the whole site so we can't do that) (everything is under Version-Control - what else do you need? ~tolleiv)François: this remains to be discussed IMO. If we're not ready with final URLs, it makes little sense to change links of typo3.org. We should rather inform the community that they can find updated manuals at temporary URLs. Write news article about that the new docs are in ReST format François: I think this was already quite well communicated about, but we will for sure continue to updated the community of the progress we make. Do a meeting with Screencast Team and Editorial Team about the changes in 6.0 related to Editors ##Introduction Package Team Delegate: *put your name here* ##Server Team Delegate: Michael Stucki * soutUpdate demo.typo3.org sout * added by Steffen Gebert * assigned to: Fabien Udriot -> \url{southttps://forge.typo3.org/issues/41696sout} * soutUpdate api.typo3.orgsout * added by Fabien Udriot * assigned to: Fabien Udriot -> \url{southttps://forge.typo3.org/issues/41695sout} ##Editorial Team Delegate: Boris Hinzer * Provide an article, why it's 6.0 together with sb. from the Core team * added by: Steffen Gebert * assigned to:Boris Hinzer / Editorial Team * Send that to the Documentation Team too (added by Martin Bless), and also to Screencast Team, please (added by Daniela) * Write about demo.typo3.org * added by: Steffen Gebert * assigned to:Boris Hinzer / Editorial Team * Send that to the Documentation Team too (added by Martin Bless) * Check typo3.org and update content regarding TYPO3 v6 * Support for Relase Notes * Update Wikipedia (German, English) immediately after release * added by: Steffen Gebert * There Slides covering all feature in detail (done by ##Press Team Delegate: Søren * write \& publish a press release * added by Steffen Gebert * assigned to: * Steffen Gebert: this has to include information about the version number * Send that to the Documentation Team too (added by Martin Bless), and to Screencast Team (added by Daniela) Process Timeline • 4 weeks before the event: Inform the press team that you need a press release on date X for product Y. If possible already provide a few keywords for what should be in the press release. • 3 weeks before the event: Provide keywords for what you want to communicate. You can provide a nice text but this is not required! It’s a lot more important to get information in time than getting a perfectly fine-tuned text. Please provide us with a few pictures/screenshots/charts as well. • 2 weeks before the event: We will provide you with a first version of the press release to check. Please let us know, if we can publish it within 3 days. • 1,5 weeks before the event: If you confirmed the content of the press release, we will hand it over to international press people for translation • 1 week before the event: Please confirm that the press release should be published and the dates you gave are still correct. • 4 days before the event: If you confirmed dates and the text, we will now hand over the press release to the press and inform them that the publishing date is in 4 days. This is not a time buffer! It is just more likely to get published if the press has some time to plan their publications. ## ##Marketing Team Delegate: *Ben* * plan release parties (Ben) * added by Steffen Gebert * assigned to * Send that to the Documentation Team too (added by Martin Bless) ##Design Team Delegate: Robert Zierhofer * Create Key Visual -> Q: New claim from marketing team or use "Back to the future"? \url{http://forge.typo3.org/issues/40807} Back on track - embracing the future * Claim changed in task * Create stage banner for typo3.org * Create Release Party Banners * Parent Task for all T3v6 related tickets created in forge... \url{http://forge.typo3.org/issues/41758} ##Screencast Team Do a separate meeting on that topic. -> who writes emails? Helmut will contact Daniela/ Silke as well as Editorial team to have another meeting at the beginning of Nov. Idea: Do a 2min Video on the major features of 6.0 * Delegate: *Silke Arend (until 8:45) and Daniela Laabs* * Create a screencast about 6.0 * added by Steffen Gebert * assigned to: * if it will be finished, this should also feature the new Introduction Package * added by Daniela Laabs: * major questions/points: * time frame (4 weeks would be good) > 27.11.12? > video about major new features to be sent to Søren at least on the 22nd Nov. * Is 6.0 a long term support version? (if so, we would probably do all new videos in 6.0 and not 4.5 LTS anymore) -> NO LTS * Whom can we address in case of questions/discussions about the content? > skype meeting with Helmut later on for all of those doing editorial work * further questions (maybe need not all be discussed in this meeting but rather later on with single persons) * Which target group are we aiming at (editors/administrators/decision-makers) and should we focus on marketing or rather on how to work with 6.0/how working has changed in 6.0? * We always use the Introduction package without customizations (as far as possible). Are there any new features about the new Introduction Package we need to show or is it enough to use it as background scene like usual? * Can anyone provide us a list of new features in 6.0 and especially of the new introduction package that need to be covered in the screencast? Send that list to the Documentation Team too (added by Martin Bless) * Where can we do the recordings or which package can we install in our installation? * Should 6.0 be presented as a new product or in comparison to any older version (if so, which one? 4.5 LTS?) * Should we explain why 6.0 comes after 4.7 (and not 5.0)? * Should we produce the screencast also in German or in English only? Ideas for a very short (1 or max 2 minutes) video introducing the most important new features of TYPO3 version 6 Examples: \url{http://tv.adobe.com/watch/photoshop-elements11-feature-tour/whats-new-in-photoshop-elements-11/} \url{http://www.youtube.com/watch?v=B5D43p4\_qcY} I think it would be nice if the videos had music in the background or between the different features. Also showing the new visuals would be great. ##typo3.org Team Delegate: *Tolleiv Nietsch*,* Joern Bock* * Do something to support the new Installtool Sysext-Migration - related to \url{https://review.typo3.org/#/c/13863/} (Kay Vogel has sent very rough requests) * see: \url{http://forge.typo3.org/issues/41760} * Integrate the new documentation somehow (?)