#TYPO3 Planet #1 meeting 6th november 2013 5pm **Present**: Thomas Maroschik, Ben van 't Ende, Fabien Udriot, Helmut Hummel,Søren Malling **Not present**: Christopher Hlubek **Agenda**: * Who are we? * Person \& skills * Thomas Maroschik: Developer * Ben van 't Ende: Testing, management * Helmut: Developer * Søren Malling: Developer * Fabien: Developer * What are we building? * Big Picture * Why? * Better representation of the knowledge and experience in the community * How? * Step 1: * RSS parsing * Own content - Buzz * API * Is it a new buzz.typo3.org? * Yes (Step 2) * Will TYPO3 still deliver a blog platform? * Yes (Step 2) * What are the goal of planet.typo3.org * Read "Big picture" -> "Why?" * Who takes care of what (skills mentioned above)? * Technical setup * At least two repositories for: 1 site package, 1 application package, 1 distribution * Will ask for development server, when we have "something to show" * Going to use **Neos** * Contact to the server team * Michael Stucki * Development plan * Current state of Planet Flow: \url{https://github.com/chlu/Planetflow3-Package/} * Figure out if we use TYPO3CR for storing the RSS items * We most likely will, if we are running on Neos ##Tasks **Ben** * Talk to Robert from Design Team about a wireframe focused on "content is king" (reference: www.medium.com, www.webplatformdaily.org, Lists: \url{https://medium.com/design-ux}, \url{https://medium.com/@GBKS}, \url{https://medium.com/design-ux/latest)} * Add "Submit your site" on a different page, not on the frontpage * In general, functionality not having to do with content goes on a different page