[TYPO3-team-core-v5] Sprint 5 planning protocol (15.10.2010)
"Christian Müller (Kitsunet)"
christian at kitsunet.de
Mon Oct 18 10:23:54 CEST 2010
TYPO3 Phoenix Sprint Planning 15.10.2010
Participants:
Robert Lemke, Karsten Dambekalns, Sebastian Kurfürst, Bastian Waidelich,
Rens Admiraal, Christian Müller, Jens Hoffmann, Daniel Pötzinger, Berit
Jensen
Sprint Review
* "Add Page" story - http://forge.typo3.org/issues/7921
* we can add pages, but still a technical debt there
* we do not yet have the widget to select the page position
* NO selenium tests yet
* Node Name is used for that page in the URL
* "Delete Page" story - http://forge.typo3.org/issues/7922
* "Page not found" after deletion of page is technically correct,
but redirect to parent page
* basic management view - http://forge.typo3.org/issues/8644
* Christian did a lot of work on that in the last months
* We'll discuss with Christian how to proceed there after the
planning
* Basic set of content element types -
http://forge.typo3.org/issues/9474
* Berit did some work here: attached to the story as a zip file
* it's just HTML
* Use some REST-Service to access the Content Repository-
http://forge.typo3.org/issues/9475
* that works, but documentation is missing
* Authentication still missing
* I want to use the CR to store content and domain objects (please
correct the title!) - http://forge.typo3.org/issues/9473
* really necessary task, very powerful concepts, very few code
* workspace "shine-through" functionality and localization is
already prepared
* a lot of technical debt -> no unit tests!!
* JavaScript User Interface refactoring
Sprint Planning
General Goal: Keep Things Clean in TYPO3
Stories from last Sprint -> EVERYBODY: Fix that!
* Add Page:
* add Tests
* add the Placing Widget
* Node Name => Rename to the Editor? "Path Segment"
* Missing Validation on this field
* TODO Jens: Define how validation errors should be shown
(http://forge.typo3.org/issues/10267)
* Delete Page:
* After Delete redirect to Parent Page
* button labels must be corrected
* Visual Bug when clicking edit and delete and ...
* General in Admininterface:
* Animation for the Edit Bar (Discuss and Improve)
* Use Tooltip for the label to avoid unrequired moving?
* Management View List
* Integrate it and make it done done
* Basic CE HTML
* jquery
* embed the html content types in an example page that has the
layout of the starterpackage
* place the HTML Template to Versioncontrol (robert will point to
the correct location :-)
* Use some Rest Service
* Documentation on flow3.typo3.org is missing:
* Explaining path, authentification, usage
* add Authentification policies
* PRIO2: Content-Repository (TODO Robert)
* add Unit-Tests with sufficent Coverage
* add Documentation that explains Usage
New Stories:
* PRIO1: Implement new visual design (Berit, Jens, Christian,
Rens)
* creating general logic / architecture for having our design in
ExtJS
* TODO Jens: we need photoshop files for Content View, Login, ...
* Use WebDav for sharing these files
* TODO Sebastian: set up this WebDav server
* create a generic Icon-Widget with Glow+Shadow+... -> TODO
Christian
* Create ExtJS Theme?
* "Guideline for Design Implementation"
* use DocBook for that
* TODO Karsten: create dummy document for that, and make sure it
is rendered on flow3.typo3.org
* http://forge.typo3.org/issues/10271,
http://forge.typo3.org/issues/10272
* CSS Guidelines (TODO Berit)
* general guidelines, and maintenance of this document (TODO
Sebastian)
* Guide for the visual design (TODO Jens)
* Start with Login Screen
* afterwards: Content area
* We will try out SASS!
* TODO Christopher / Christian: is there a PHP parser available
for that? http://code.google.com/p/phamlp/
* If not, we will use the command line ruby "sass" compiler to get
started
* some nice presentation:
http://dl.dropbox.com/u/98303/dkd-sass-compass.pdf
* TODO Rens: Focus on Breadcrumb menu
* TODO Nils: Create ExtJS Theme for Phoenix, including xtemplate
cleanup
* Basic workspaces support (TODO: Robert)
* no GUI for it
* just personal workspace
* after logout it ask to publish changes to live
* Clean Up Javascript (TODO: Sebastian, Rens)
* PRIO3: Exploration Task: Use Doctrine2 as persistence backend
(TODO Karsten, Bastian)
* http://forge.typo3.org/issues/10273
* benefit: our DB structure would be compatible with other
packages
* Persistence is actually really usable afterwards :)
* They offered their help
* if Doctrine supports versioning, we should use it really soon
* Exploration Task: Installer -> not in this sprint
* concerning Installer: talk with Zeta Components, and join forces
there
* Exploration Task: Package Management -> not in this sprint
* some ideas floating around, maybe using PEAR2
* TODO Nils, Sebastian: JavaScript guidelines
* where to put additional resources / folders
* Functional Testing support for FLOW3 -> TODO Christopher :-)
* Kunagi, we should first evaluate scrum plugins for redmine. But
if Daniel wants to set it up, feel free
ToDo
* get a Mac for everyone ;-)
Availability (4 weeks until sprint end)
* Robert: 3 weeks
* Karsten: 3 weeks - GSoC Mentors Summit (3-5 days)
* Berit: 1 - 99 days (if the craftsmen and bachelor thesis let
her)
* Nils: 2-3 days
* Rens: 4 days -> time could still increase (Ben will handle that)
$$$
* Jens: 2 days / week
* Christian: about 1 week in total but difficult to plan. $$$
* Sebastian: ~ 1 day (or night) / week
* Bastian: ~ 1 day (or night) / week i want $$$ too
* Andi??
* Christopher??
Sprint ends at 12th of November
Tasks are created by the responsible people (watch TODO items); and mark
TODO items if they are created.
Greets,
Christian
More information about the TYPO3-team-core-v5
mailing list