Udig round the world sprint

Udig round the world - code sprint
There's a plan afoot to take a couple of days to do a code sprint on uDig trunk (aka 1.2). Since doing the sprint in one place is too much to organize, plan and fund, the idea is to spend the time working on IRC. The goal is to push uDig trunk towards stability since it uses newer versions of GeoTools and Eclipse which have fixed many bugs and provide more capabilities.

There is a strong desire to prepare the code sprint with a bug festival. The bug fest would use a new release of uDig and try to break it in as many ways as possible and file those bugs. The code sprint could then aim to triage the bugs, pick areas that need work, and clean that code to fix the bugs.

This event was born out of this email thread: http://lists.refractions.net/pipermail/udig-devel/2008-December/013591.html

This code sprint will take place mostly in IRC via udig's IRC channel.

Dates
Proposed date for the sprint is 16-17th of January.

Preparatory Bug Fest
Prior to the code sprint, we want to find all of the critical bugs, and many other bugs.

A new uDig trunk(pre1.2) release is required
Someone needs to step up and do a release to build and package the latest trunk for XP/Vista, OS X, and Linux.

(Links to the release version to appear here soon.) [actually, we should just point to the uDig download page]

What will be tested before the sprint on the released version
Everyone gets to try and break uDig their own way. For more structured examination, we can accumulate ideas here.

We need to go through the uDig tutorials; these cover the functionality we need to work in order to have the product function.
 * http://udig.refractions.net/confluence/display/EN/Quickstart
 * http://udig.refractions.net/confluence/display/EN/Walkthrough+1
 * http://udig.refractions.net/confluence/display/EN/Walkthrough+2

Just going through this in order and listing any problems an amazing help (we can do the list in the next section).

We can list other ideas for issues to test in the table below.

Issues encountered during testing
If you use the released uDig to go through the tutorials or other tests described above, but don't have time or know how to fix the wiki text of the tutorials and file JIRA tasks, please list issues you run into below.

The wiki text can be fixed directly on the site of the tutorials if you have the right permissions.

JIRA Tasks can be filed at: http://jira.codehaus.org/browse/UDIG.

Donated services
1. Test server - Eric Jarvies offers two 1GB slices over at slicehost web hosting, along with ssh/sftp access to whomever assumes responsibility( Mark Leslie?? ) for all, or a portion thereof, of Geoserver, PostgreSQL/PostGIS, tilecache, etc., and user accounts for those wishing access to the data for testing purposes. So, two types of accounts... one for those who will need to edit something server side, and those who will only be accessing the data for testing within the uDig client. Thus, we should organize the list of users and which category they fall into. 2. Sample data - Eric Jarvies offers point, path, and polygon shapefiles covering the Los Cabos Municipality in Baja California Sur, Mexico. These data sets include shapefiles(or PostgreSQL ready) and raster satellite images(if need-be). I will reduce the content from these maps, specific for this testing, and will submit them to Mark Leslie for review, and providing they fit the bill, then of course permission to use them is granted. They cover area municipality, neighborhoods, titled properties, POIs, tax zones, arroyos, streets, and so on. Thus, they contain a good mixture of data, some containing large number of records, all containing the same coordinates and coverage area(a nice layer stack/mixture).

Tutorial issues: * add your issue here

Triage: Tasks that were chosen to be fixed during the sprint
to be defined