[TYPO3-team-core-v5] Scrum Meeting Notes - 25.04.2013

[Bastian Waidelich]

Scrum Meeting Notes - 25.04.2013

SPRINT PLANNING

ⓘ Permanent Scrum Hangout: http://bit.ly/FlowHangout
ⓘ https://notes.typo3.org/p/renaming-technical-todo
ⓘ Code Sprint 2 dates fixed: week 20 (13. - 17. May)
	➜ Please post your arrival/departure dates 
http://forum.typo3.org/index.php?t=msg&th=194073&goto=680731&#msg_680731
ⓘ Flow: We should not introduce new breaking changes, if we get to the 
point it might be required we should meet and discuss solutions like 
possible backwards compatible solutions, feature switches or extracting 
in a separate package.

[ROBERT]

✔ reviewed, improved and submitted a few bug fixes for Flow 2.0
✔ a lot communication regarding individual efforts of community members 
regarding new features, changes to Neos / Flow etc
✔ started getting an overview of running development, reported issues 
and feature requests
➜ write some thoughts about the mailing lists to the mailing list
ⓘ will be offline during the next whole week and the week after
ⓘ Have a Neos and a Flow status meeting on: 23.05., 06.06., 20.06, 
06.07. (T3DD13), 18.07., 01.08. (16:00 Flow, 17:00 Neos)

[CHRISTIAN]

✔ 2 talks for SF accepted
✔ discussed mediabrowser with Karsten and Markus
✔ looking at tagging solutions
✔ GSoC mentor hangout
➜ reviews for 2.0
➜ find a good new working mode
➜☠  next week 2 days of training and rest free time (maybe a bit of 
flow/neos) to get mind free
☠ wants to get rid of some customers ;)

[BASTIAN]

ⓘ Became one of the organizers of the “2nd Neos code sprint” somehow..
➜ Please add your arrival/departure dates (see above)
✔ Created simple CSRF token ViewHelper
✔ Abandoned some shabby or irrelevant reviews
✔ Worked on and thought about my work package (improved REST support)
☠ Stuck with some changes that would break the API
➜ looking forward to some feedback on 
http://forge.typo3.org/issues/45290#note-8
➜ discuss possibilities (at the code sprint?)

[RENS]

✔ Got some good feedback from Rasmus about the navigation elements in 
the masterplan
✔ Finally has a blog site with Neos running
➜ Now get it online ;)
➜ Continue on accessibility & navigation elements
☠ Coffeemachine broken
♫ Coffeemachine will be fixed next monday
⚒ Customer work is a *****

[ASKE]

☠ Hard drive failure.. still recovering
✔ Some Neos discussions / reviews (Ember update, node links, etc.)
➜ Create UI master plan tasks
➜ Introduce/mentor Sebastian Hens (Neos JavaScript)

[KARSTEN]

✔ 2 talks for SF accepted
✔ discussed mediabrowser with Christian and Markus
✔ reviewed a number of Neos changes
✔ started to implement Media Browser, see 
https://github.com/mgoldbeck/TYPO3.Media/tree/dev

[JULLE]
✔ Updated a few patches
♫ Working on real Flow project - having a lot of fun - and learning stuff.

~~~
Legend:

✔   done
➜   next steps
☠   impediment
ⓘ  background info
♫   celebrated
⚒   work
☃  snow
⚖  life / work balance in danger