Attendees

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

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

• Osman
  • Likes the new standup format. Saves time.
    • May be even more useful when there are more people on the sprint and more tickets to review
• Yinlin
  • Also likes the new format
    • More efficient
  • Would be helpful to have test cases in the tickets in advance
• Andrew
  • Still some tickets left unworked
  • Sprint was not as productive as it could have been
    • Some tickets have obvious implementations, but some require more investigation. Implementation is not always obvious at the outset 
    • Large codebase and toolset, processes to learn. Takes time to get up to speed
    • Slow turnaround on questions/answers. Byproduct of IRC standups?
  • Calls and messages with Yinlin were productive; good way to avoid getting stuck on issues

Working on tickets outside of sprints

• Send out emails with outstanding tickets
• Discuss new and outstanding tickets during Fedora Tech calls
• Encourage committers to take on tickets outside of sprints

Summarize final state

• 5 tickets in review
• 1 ticket in progress
• 4 unstarted/unassigned tickets

Walk through in-process and unstarted tickets

• Unable to locate Jira server for this macro. It may be due to Application Link configuration.
  
  • Complete - just needs review
• Unable to locate Jira server for this macro. It may be due to Application Link configuration.
  
  • Will likely require a bit more iteration after review
• Unable to locate Jira server for this macro. It may be due to Application Link configuration.
  
  • This issue may be the result of a ModeShape bug. Osman will investigate further
• Unable to locate Jira server for this macro. It may be due to Application Link configuration.
  
  • Currently writing tests.
• Unable to locate Jira server for this macro. It may be due to Application Link configuration.
  
  • 5 minute ticket
• Unable to locate Jira server for this macro. It may be due to Application Link configuration.
  
  • High-priority
• Unable to locate Jira server for this macro. It may be due to Application Link configuration.
  
  • URL encoding not behaving as expected
• Unable to locate Jira server for this macro. It may be due to Application Link configuration.
  
  • Vagrant proxying requests, changing baseURL
  • Low-priority