Attendees

• Andrew Woods
• David Wilcox 
• Osman Din
• Yinlin Chen
• Nianli Ma

General

• Indicates who took minutes -
• Call-in: Google-hangout at:
  
  • https://plus.google.com/hangouts/_/event/c1glu6soq43r1rr6ou17qtobug8

Agenda

1. Meta analysis of sprint process
2. Summarize final state
3. Walk through in-process and unstarted tickets
4. Teeing up for next sprint

Minutes

Meta analysis of sprint process

• Nianli
  • First sprint
  • Learned a lot
    • Getting familiar with the process
    • GitHub
    • Maven
    • Javadocs
  • Difficulty setting up an environment
    • Too much information, hard to keep track of everything
    • Would have been helpful to prepare for the sprint in advance
• Yinlin
  • Feels more comfortable
  • Resolved some Eclipse formatting issues
  • Perhaps we need a list of developers and what tools they use. This could be helpful for troubleshooting problems
• Osman
  • Encode Sonar rules in build steps so a developer will receive a compile-time error when breaking a rule
    • This will obviate the need for refactoring code the breaks existing rules
• David
  • Everyone provided efficient status updates in IRC
  • We should be clear about what ‘blocker’ means - developers should ask for help once their toolkit is exhausted in figuring out a problem
  • When pointing to an issue, the format ‘FCREPO-xxxx’ is the most efficient for pasting into the notes
• Andrew
  • Disconnected from sprint
    • At Code4Lib week 1
    • It would be useful to have a phone call to summarize status if a similar situation comes up in the future