You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 2
Next »
Attendees
General
- Indicates who took minutes -
![(star)](/s/h9vz60/9012/1phy4ty/_/images/icons/emoticons/star_yellow.svg)
- 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
- 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