MinuteS20110613
TWiki>
LibrePlan Web>Meetings>MinuteS20110613 (20 Aug 2012, ManuelRego)EditAttach
- Date: June 13, 2011 at 16:00 CEST (GMT +2)
- Goal: General coordination meeting
- Agenda: Agenda
- Log:
navalplan-roadmap-meeting-20110613.txt
- (1) Periodic coordination meeting proposal
- Seems like a good idea
- They will have a defined structure
- We're going to arrange these meetings every 2 weeks with a maximum duration of 1 hour
- Default date and time would be on Mondays at 12:00 Central Europe time
- (2) One iteration per release
- Agreed to reduce the number of iterations
- One iteration every 3 months (as we have now defined the release period) seems a good approach
- Number of stories per iteration shouldn't be a problem
- We'll start next week with one iteration till September
- (3) Encourage developers to write comments
- Thanks to have one iteration per release it seems easier to have all comments about one task together
- People should try to write more comments about what they're doing every day or week
- About source code comments, code is not properly documented now
- Include more comments in some cases seems like a good idea
- Current agreement is to have at least a comment per class explaining what it does. However, we're even having problems to fulfil this agreement
- We should improve comments in classes explaining more things and try to use meaningful method names
- (4) Analysis stories
- Everything seems to be working fine the analysis part
- We should keep doing analysis to have the information about task requirements and so on
- (5) Regressions
- We have been debating about if it's needed or not to do some code review in order to avoid regressions
- We're not sure if it's worth
- We're going to try to test some tools that could help this process (like gerrit, gitorious, ...) and define a protocol to decide if we see it accurate for our needs
- Next Monday, the 20th we will start the periodic coordination meetings as agreed in first point
Copyright (c) by the contributing authors. All material on this collaboration platform is the property of the contributing authors.