Attendees
General
- Indicates who took minutes -
- Call-in: Google-hangout at:
Agenda
- Meta analysis of sprint process
- Summarize final state
- Walk through in-process and unstarted tickets
- Teeing up for next sprint
Minutes
Meta-analysis
...
- 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
...
- 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
...
- 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
...
- 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
- Jared
- Would have liked to be more engaged since last sprint
- Thurs call was fairly quiet relative to email threads
- Should encourage discussion from threads into tech meeting
- Nianli
- Was distracted by local resposibilities
- Interested in migration-utils, but need person for feedback/help
- Yinlin
- Need more detail in ticket
...