Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Should sprint wrap-ups be public?
  2. Meta analysis of sprint process
  3. Summarize final state
  4. Walk through in-process and unstarted tickets
  5. Teeing up for next sprint

Minutes

 

 

...

Open Wrap-ups?

  1. Public should be allowed/encouraged to join wrap-ups
    • Agreement

Analysis and Tickets

  • Scott Prater
    • Did not get as much done as liked
    • Got cluster and tooling put together
    • Will be working halftime next sprint - every other day for both weeks
    • Will be running Frank's
    • Worked mostly at the level of where the software meets the hardware
  • Osman Din
    • Builds are taking 5 - 9 minutes (4 times longer than before)
      • Sometimes builds fail
      • Andrew to get historic timing of builds on travis and jenkins
    • Interested in discussing ISPN/F4 architecture
  • Mike Durbin
    • Process is fine
    • Snow days interupted work
    • Stand-ups worked, and were quick
    • IRC conversations were work
    • Was judicious with making builds
    • Will get locking into a "pass off-able" state
  • Mike Daines
    • Spent fair amount of time getting up to speed
    • Assigning ticket of initial tour worked well
  • Greg Jansen
    • Snow days had an impact
    • Worked well to be in same room with Mike and Ben
    • Frustrated by the pace of get clustering setup in place
    • Puppet is effective, good to tease out fedora parts from the infra parts
    • Goal to run performance tests today/tomorrow
    • Forked Scott's puppet project, will close tomorrow
  • Frank Asseg
    • out
  • Eric James
    • Sprint went fine
    • Most useful part of sprint was debugging deep into the code
    • Difficult to stay in IRC, need to focus when coding
      • Catching up with IRC during breaks seemed to work
  • David Wilcox
    • Catching up with how things work
    • Looking forward to digging into use cases
  • Ben Pennell
    • On-boarding was fine
    • Starting with unit tests was good
      • A unit test guide would be useful
      • Need to document test helper apparatus
    • Interested in testing eclipse/checkstyle PR
  • Adam Soroka
    • Making tickets that encourage engagement is great to have on-hand
    • OSGi will extend into next sprint
    • Models/Ontology LDP/F4/JCR moving forward, making process

 

Actions