This is the old archive of logs which were done manually (so some are missing). Now the mapbuilder channel is automatically archived at http://uwyn.com/drone/log/bevinbot/mapbuilder

IRC 01/02 June 2006

Read Logs

IRC 25/26 May 2006

Read Logs

IRC 18/19 May 2006

Read Logs

IRC 11/12 May 2006

Read Logs

IRC 04/05 May 2006

Read Logs

IRC 27/28 April 2006

Read Logs

IRC 20/21 April 2006

Read Logs

IRC 13/14 April 2006

Read Logs

IRC 06/07 April 2006

Read Logs

IRC 31/01 March 2006

Read Logs

IRC 24/25 March 2006

Read Logs

IRC 3/4 March 2006

Read Logs

IRC 24/25 February 2006

Summary:

1. Aim to freeze build for release 1.0 next week (Fri 3 March).
2. Mike is currently working the 1.0 bugs, but it would be great if one of the new programmers could help him and free Mike to work on some of the harder problems. In particular, we need someone to replace the Loading widgets with Loading2 in each of the demos. (A cut and paste exercise).
   We also want to fix the flicker problem when on IE (where old layers flicker on/off when rendering new layers). Might be fixable by setting old layers to null before rendering.
3. We need to ensure our documentation is ready for 1.0 release. In particular, the mapbuilder.sf.net web site needs to point to docs.codehuas.org/display/MAP
4. We aim to freeze code for a 1.1alpha release on 17 March, (although this might slip a week).
5. 1.1alpha will contain Pat's new rendering factory code, + GeoRSS, Google Maps Layer, maybe Geotracing.
6. Discussed Geotracing
7. Bert/Cameron/Patrice all have a need for a Feature Entry with Group based Authorisation and update history. This was discussed with no resolution.

Read Logs

IRC 17/18 February 2006

Summary:

1. Richard to come up with a projection project name
2. Richard to run the name and your RFC past the Mapbuilder email list.
3. Set up a mapbuilder-proj email list (or some other name)
4. Invite other projects to join the list
5. Initiate discussion with other projects on your library.
6. In slow time, create a mapbuilder-proj release which is seperate to Mapbuilder-lib.

Read Logs

IRC 3/4 February 2006

Agenda:

• Progress with 1.0RC2 - review issues
• Release date for 1.0RC2
• Subversion. Report from Matthew. When should we strike a 1.0 branch?
• Mapbuilder Foundation. Any issues we would like to forward?
• Release date for 1.1?
• What should go into release 1.1?

Read Logs

IRC 27/28 January 2006

Summary:

• It was proposed that 1.0RC2 be taken from the trunk instead of from the branches/1_0 directory. Since no one seems to have been adding features to the trunk yet, Cameron agreed. (Patrice, can you confirm that you have not been committing your development to the trunk.)
• Matthew is going to look into Subversion and see if he can do a better job than Cameron at working out how to set up a branches directory (for post 1.0RC2).
• Mike suggested we should clean up the Sourceforge web page before releasing 1.0RC2. We are still looking for a volunteer for this.
• Mike/Cameron discussed the Open Geospatial foundation.
  While we would accept assigning copywrite of Mapbuilder to our Project Management Committee (which is not possible unless we create it as a legal entity) we are not comfortable allowing the Geospatial Foundation relicence Mapbuilder for the commercial gain of the Foundation.
  I think Steven and Patrice had similar view?

Suggested agenda:

• Creating a 1_0 branch in Subversion and checking it out - why isn't it working?
• Progress with 1.0RC2
• Design issues - a number of questions have been raised on email that can be discussed here.
• What we want out of the Mapbuilder Foundation?

Read Logs

IRC 20/21 January 2006

Summary:

Agenda:

Read Logs

IRC 13/14 January 2006

Summary:

Meetings:

• Next IRC meeting: same time and day of week. Ie, 18:00 Friday UTC.
• Regular addendees should email if they will not be attending the meeting so we don't hold up the meeting waiting for them.

1.0rc2 and svn:

• Release 1.0rc2 freeze date is targeted for 3 Feb.
• We are looking for a volunteer to put the release together
• Aim to fix all priority 6 bugs and greater
• We will create scm/branches/1_0 branch for svn fixes which is based on 1.0rc1.
• The 1.0 branch will accept bug fixes only. Note, developers will also need to copy bug fixes into the trunk (I suggest using "svn join").
• Features will be added to the trunk

Confluence/Bug tracking:

• Linda volunteered to move open bugs from Sourceforge to Confluence on Codehaus. Confluence has many advantages, including assign a bug to one build and not another, assigning bugs/features to a release then tracking progress of the release.

Feature backlog:

• Decided that the feature backlog would be easier to manage if we moved it into Confluence.

Context/MapPane/Vector rendering refactoring:

• Cameron/Patrice discussed how this code should be refactored so that we can handle layers from multiple datasources. Currently MapPane only handles WMS layers and the other layers are a bit of a hack.

Read logs

IRC 8/9 December 2005

Agenda:

• IE on load bug that is being reported is a showstopper. Any ideas on what the problem is and how to fix it?
• Planning for future builds. What builds do people want to support? And Branching as suggested by Mike
• Do we want to move Sourceforge bugs to Codehaus. If so, do we have a volunteer?
• If we have time or if Pat turns up, we can talk about SCRUM.

Summary

• Steven will look into IE loading bug. Probably won't get to it until the new year.
• We will create a Subversion branch for release 1.0 bug fixes for bug fixes only.
• Pat has suggested using http://www.fitnesse.org for managing user stories and testing.
• Steven will update User Stories. We can prioritise these in the next meeting.
• Next meeting, same time next week.

Read logs

IRC 1/2 December 2005

Agenda:

• RC date
• Moving to SVN
• Future release and development (ideas from Pat/Linda)
• New time

Summary

• Cameron will build RC again today, Mike (and others?) to test, then Cameron to release tonight if ok.
• Assuming RC is put out tonight, Pat/Linda can move codebase to SVN on codehause from tomorrow.
• We can start branching for 1.0 from within SVN after the move.
• Pat/Linda to set up a Confluence area for developing Use Cases and wish list and we can start working the SCRUM way as suggested in their email.
• Research Pat/Linda doing into Testing highly encouraged and supported.
• Suggest a new timeslot for meetings: 5am Sydney, 1pm New York time, 7pm Europe time on Tues. or Wed.

Read logs

IRC 24/25 November 2005

Agenda:

• walk through the issues
• work out a plan for rc1
• 0.4-1.0 upgrade doc

Present: Cameron Shorter, Mike Adair, Sean Gillies
Summary:

• Mapbuilder 1.* has to be backwards compatible with 0.4
• Upgrade path 0.4 -> 1.0 is added to the wiki
• We build for jdk1.4 and hope that works jdk1.5 otherwise we can release 2 versions

Read logs

IRC 17/18 November 2005

Present: Cameron Shorter, Mike Adair
Summary:

• Freeze date for 1.0rc1 set to midnight Sunday (Eastern time)
• Cameron to ask Matt if he can build a release
• After release we will move codebase from CVS to Subversion on Codehaus

Read logs

IRC 10/11 November 2005

Agenda:

• Bug list
• When will we release 1.0?

Present: Cameron Shorter, Mike Adair

Summary:

• Discussed and closed bugs.
• No release this week. Still a couple of bugs we want to fix first.
• Aim for a release candidate next week. To be decided in next weeks meeting.
• Next meeting is same time and place next week.

Read logs

IRC 4/5 November 2005

Agenda:

• Stability of MapPan
• Outstanding bugs
• Pick a time for future meetings
• How we are going for a 1.0 release

Present: Cameron Shorter, Steven M Ottens, Mike Adair, Linda Derezinski

Summary:

• We have a plan for working off bugs.
• Release Candidate planned for next week
• Release 1.0 planned for the following week
• Meeting time decided for Thursday - same time as today + 30 mins
• Steven to Test MapPane

Read logs

IRC 27 October 2005

Agenda:

• MapPane stability and functionality
• Double rendering
• Memory usage and CPU/memory overloads
• Release plans

Present: Cameron Shorter, Pattrice Capellaere, Steven M Ottens, Mike Adair, Matthew Diez, Tom Kralidis, Linda Derezinski

Summary:

• Mike will have a look at mappane this weekend and give a recommendation how to fix it
• If he has time cameron will check memory leak in mapbuilder0.4 otherwise matthew will do so this weekend
• No release until mappane is stable
• Pat will add one more demo, but under the condition that nothing breaks

Read logs

IRC 20 October 2005

Agenda:

• Release plans

Present: Cameron Shorter, Pattrice Capellaere, Steven M Ottens

Read logs

IRC 13 October 2005

Agenda:

• Icons
• Mappane design
• Build status and plans for release

Present: Cameron Shorter, Pattrice Capellaere, Steven M Ottens
Summary:

• Mappane needs to be fixed, Mike/Michael need to give comments on it
• A long debate on how to implement icon palettes/SLD, no definitive conclusion, but no hand written SLDs

Read logs

IRC 4 October 2005

Agenda:

• Pat: Overlib and http://www.twinhelix.com/ (a similar library)
• Measurement Tool
• Release progress
• bug triage/prioritization
• Anything else?

Summary:

• Pat suggests to use twinhelix library instead of overlib and will write a report what needs to be done
• Steven and Imke have finished the measurement tool, it only works with XY coordinates so far, it will be commited
• Quite some bugs are already fixed or almost fixed, we want all priority 6+ bugs fixed before the release

Read logs

IRC 29 September 2005

Present: Cameron Shorter, Mike Adair, Steven M Ottens, Pattrice Capellaere
Summary:

• History: we try it first as a tool, if we find we need a model when we go to extend it further we can look at that
• We create and release a stable 1.0 before we move to dojo and SVN
• We release at the 1st of november
• Featurefreeze is set at 13 october
• Next meeting 6 october 11 UTC

Read logs