LibrePlan Meeting 2011/06/20

• Date: June 20, 2011 at 12:00 CEST (GMT +2)
• Agenda: Coordination meeting
• Log: navalplan-coordination-meeting-20110620.txt

Minutes

• Rego
  • 
    • Improved content of README, INSTALL and HACKING files. Now with info about how to install in Debian, Ubuntu or openSUSE and how to compile in Debian, Ubuntu, openSUSE and Fedora.
    • Get rid of Ruby for web services example scripts. Updated web services README file too.
    • Prepared PPAs for Natty found an issue because of CutyCapt is already packaged in Natty (and also in Debian Sqeeze) and the command is cutycapt instead of CutyCapt. We should update LibrePlan to use the new command, and also update packages for Lucid and Maverick.
    • Bugfixing: closed #971 and #1090
  • 
    • Not too much time this week.
    • Patch review and general bugfixing.

• Nacho
  • 
    • LDAP LibrePlan role matching, some patches pending.
    • Realised that small patches are better to review and manage.
  • 
    • Finish this week the role matching task.
    • If more time available help Cristina with her task.

• Cristina
  • 
    • Working on language configuration for users.
    • Found a problem getting authentication user in the controller.
    • New method for that: org.navalplanner.web.security.SecurityUtils.getLoggedUser()
  • 
    • Keep working in those tasks.

• Óscar
  • 
    • Working in ZK5 merge.
    • Fixed some critical bugs: JavaScript issue changing zoom, JavaScript error moving tasks.
  • 
    • Finish to try ZK5 and merge it in master.
    • Document the user stress testing done in previous weeks.

• Susana
  • 
    • Changing calendar interface to include some usability improvements.
  • 
    • Finish this task.
    • Some bugfixing if free time.

• Javichan
  • 
    • Analysed task about user language and preferences.
    • Sent mail about some Monte Carlo issues.
  • 
    • Analyse more tasks for 1.2 release.
    • Test and develop some of the features that are being developed.

• After that we reviewed a proposal by Óscar to send this info to the mailing list and avoid the meetings. But we think that sending the minutes and logs is enough. And 1h every 2 weeks is not too much.

• Next meeting will take place on July, the 4th.