Live GIS Disc Meeting Minutes - Revision history

Wiki-HamishBowman: /* Th/Fr 4 Mar 2010 */ web data dir

2010-03-03T03:27:14Z

Th/Fr 4 Mar 2010: web data dir

2010-03-03T03:17:04Z

Th/Fr 4 Mar 2010

2010-03-03T03:15:59Z

Th/Fr 4 Mar 2010

2010-03-02T22:14:10Z

dupe cat

2010-03-02T22:12:59Z

Th/Fr 4 Mar 2010: wordo

2010-03-02T22:12:06Z

Th/Fr 4 Mar 2010

2010-03-02T22:11:05Z

Th/Fr 4 Mar 2010

2010-03-02T22:07:08Z

Th/Fr 4 Mar 2010

2010-03-02T22:06:42Z

Th/Fr 4 Mar 2010: wikifix, category:live-demo, etc

2010-03-02T19:50:41Z

Th/Fr 4 Mar 2010

@@ Line 16: / Line 16: @@
 * 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. '''[link please]''' 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.
-* SVN &rarr; website cron job; project presentation.
+* SVN &rarr; website cron job; project presentation; data/ dir.
 =We/Th 27 Jan 2010=

@@ Line 1: / Line 1: @@
 =Th/Fr 4 Mar 2010=
-Time: Thursday, 4 March 2010 at 7pm GMT - [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 Click here to see this time in your local timezone]
+;Time: Thursday, 4 March 2010 at 7pm GMT - [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 Click here to see this time in your local timezone]
-Location: irc://freenode.net#foss4g
+;Location: irc://freenode.net#foss4g
-Background:
+;Background:
 * According to [http://spreadsheets.google.com/ccc?key=0Al9zh8DjmU_RdE1SYUN3YWJ2N1NpSUczbW9IRWZNclE&hl=en_GB our schedule], we are a few days late for our RC3 release. I hope that we can get the next release out this weekend,
 * 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:
+;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.
 : ''New "Tested in RC?" column added in google spreadsheet''

@@ Line 16: / Line 16: @@
 * 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. '''[link please]''' 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.
+* SVN &rarr; website cron job; project presentation.
 =We/Th 27 Jan 2010=

← Older revision		Revision as of 22:14, 2 March 2010
Line 17:		Line 17:
	* 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. '''[link please]''' 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.		* 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. '''[link please]''' 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.

−	~~[[Category: Live-demo]]~~

	=We/Th 27 Jan 2010=		=We/Th 27 Jan 2010=

@@ Line 5: / Line 5: @@
 Background:
-* According to [http://spreadsheets.google.com/ccc?key=0Al9zh8DjmU_RdE1SYUN3YWJ2N1NpSUczbW9IRWZNclE&hl=en_GB our schedule], we are a few days late for our RC3 release. I hope that we can the next release out this weekend,
+* According to [http://spreadsheets.google.com/ccc?key=0Al9zh8DjmU_RdE1SYUN3YWJ2N1NpSUczbW9IRWZNclE&hl=en_GB our schedule], we are a few days late for our RC3 release. I hope that we can get the next release out this weekend,
 * 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.

@@ Line 15: / Line 15: @@
 * 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. ('''[link please]'') 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.
+* 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. '''[link please]''' 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.
 [[Category: Live-demo]]