Readers/Web/Team/Retrospectives/2015-01-05

From mediawiki.org

Events of Last Iteration[edit]

Kindergarten Cop/Unstructured (12/08/14-12/19/14 and 12/22/14-01/02/15)[edit]

Notable events:

  • Maryana -> Africa
  • Collections
  • Holiday Party Dancing!!!
  • A new year
  • beards
  • Max's arm (-1 arm velocity)

Absences:

Points carried over from previous iteration: 34 Points attempted: 71 Points completed: 36

Velocity chart: https://docs.google.com/a/wikimedia.org/spreadsheet/ccc?key=0AqEdtQuSLdAxdGF0Unlob2MtRmZTeU4tODJXbk9rQ1E&usp=drive_web#gid=1

Actions from last retrospective:

  • Make sure that internationalization/localization of WikiGrok is part of our Q3 planning/post-testing discussions [KRISTEN]
  • Start mailing list conversation to document the remaining blockers for our team to move to Phabricator for project management [JON]
  • Update team on latest WikiGrok deployment and testing plan [KALDARI] DONE!
  • Schedule a meeting for the team to talk to Damon about some of the challenges we are facing as we try to "move faster and stay current"; set agenda, get it scheduled! [Moiz/Kaldari]


https://docs.google.com/a/wikimedia.org/document/d/1NqzIX9hXJbaY-ke6uWThKFBEj7CUweSQrw6cCR_fGcY/edit

What's been working well?[edit]

  • I enjoyed having time allocated for devs to talk about architecture and code in general during dev backlog
  • Nice code
  • Lots of good stuff got done during unstructured sprint (hygiene, fixing old bugs, new experimental features) ++
  • Vacation+
  • I poured coffee into my laptop and it's working fine!
  • code review across the atlantic
  • florian+
  • Mediawiki-vagrant hasn't used 3 cores at once 300%cpu for a few weeks echo flushall | redis-cli Thanks!
    • It would be nice if there was better documentation on troubleshooting, aside from reloading

What hasn't worked well?[edit]

  • I didn't enjoy having too many meetings because of the developer backlog
  • I am fed up with the monthly showcases. -
    • make them optional?
  • oojs ui didn't have any demos for the bit of code I wanted to use+
  • vagrant has been slow recently
  • i feel like code review is not evenly distributed+++++
    • Jon feels like he's doing a lot
    • Rob is going to make an effort to shoulder some of the load
    • +1 even if you just look at it
    • Action: schedule a gerrit/general tools (eg how to derploy) session [JON]
    • gamify code review!
  • Still oodles of outstanding (!) code review
  • Refreshing phabricator a thousand times in standups
  • Seems like lots of bugs recently (especially in alpha)
    • what should our interval for human acceptance testing be?
    • weekly? sprintly?
  • Bringing up the team split last minute before holidays+
    • was shocking/out of the blue
  • OS fucking X
    • Is that the name of the latest version?
  • vagrant in general, maybe switch to docker
    • Is docker better? Needs a spike ;)) file system snapshots (git-like deps/upgrades)
    • needs defintion of the problem(s) that are cropping up: memory usage, anything else?

What is confusing?[edit]

  • Developer backlog/kittens/megateam
  • Phabricator migration plan++
    • we should proactively identify our blockers
  • schema2 branch=
  • How the team split will work with no dedicated backend engineer for list stuff
  • should we abandon patches over 30 days old?+
  • Team split, what, how, where, why, when++++++++
  • What's going on with the Mantle/MF split? +1+ [Action: please everyone reply to this email thread so we can kill it]
  • A lot of hygiene patches. Why? 3 years worth of building stuff but not actively caring for our code :-) We should be in the loop too then, not just review code.Inline conversations FTW.
    • emails to mobile-tech mobile-l? especially for large commits/changes [Let's try this out from now on, I will do so on my big patches (ACTION)] +1
    • Seems, there will always be hygiene patches
    • Better commit messages?
Retrieved from "https://www.mediawiki.org/w/index.php?title=Readers/Web/Team/Retrospectives/2015-01-05&oldid=3045126"