Live GIS Disc Meeting Minutes

Th/Fr 4 Mar 2010

http://timeanddate.com/worldclock/meetingdetails.html?year=2010&month=3&day=4&hour=19&min=0&sec=0&p1=22&p2=240&p3=195&p4=179&p5=137

Background:

• According to our schedule, we are a few days late for our RC3 release. I hope that we can the next release out this weekend, http://spreadsheets.google.com/ccc?key=0Al9zh8DjmU_RdE1SYUN3YWJ2N1NpSUczbW9IRWZNclE&hl=en_GB
• And we have 12 days till the final release.
• This meeting is to set out our plan for getting this final release out the door.

Agenda:

• Planning and documenting testing, as per: [Live_GIS_Disc_Testing]. I want to have a brief test description for every package, and then track that someone has tested every application.
• Decide on background image
• Decide on menu structure, (can we loose the icons from the desktop?)
• From the next release, we need to test creating an ISO image. Do we have a volunteer?
• Documentation: I'd love it if someone could go through all documentation and make it consistent (without changing any content). If we are really keen, it would be good if someone could incorporate Jody's OpenOffice overview of each package, and incorporate this into the documentation build. Jody has documented how to start up and run most of the packages, using screen snapshots and all. I've worked out how we can convert these docs into HTML from an install script using abiword. If we haven't got time for this, it will need to wait until the next release.

We/Th 27 Jan 2010

http://timeanddate.com/worldclock/meetingtime.html?year=2010&month=1&day=27&p1=137&p2=22&p3=240&p4=215

Agenda:

• Prioritise tasks that we will work on for the upcoming 3.0 release

• Roundup of new programs since 2.0

• Update on what's happening with Click2Try

• Look over & triage open bug reports

Possible Areas for improvement:

• Clean up desktop icons
  • maybe use a menu instead
  • probably create a section for "bleeding edge" releases and packages. This section doesn't need the same level of QA as the rest.

• Make build scripts consistent
  • copy config files from checked out svn directory, rather than "wget https://svn.osgeo.org/...xx.config". This means we can rebuild old releases (which can't be done at the moment).
  • Use the same tmp file names

• Quality Control:
  • Have each project write a test plan which explains how to test to see if the project works

• Move toward OSGeo incubation
  • Put commit processes in place, and specify which licences can and cannot be added
  • Have committers sign up to maintain the commit guidelines
  • Specify license guidelines

• Data Sets:
  • Package up a common dataset
  • Encourage (but not mandate) projects to use the dataset

• Documentation: (probably to target 4.0, foss4g 2010)
  • Provide tutorial guidelines
  • Encourage projects to populate the tutorials in line with the guidelines

• Install to USB Stick how-to

• Multi-lingual how-to

• Wireless network card firmware (and non-Free in general)