Difference between revisions of "Udig round the world sprint"

Revision as of 06:16, 16 December 2008

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.

Proposed Dates and Contributor Commitment

The following is an initial and very rough draft of proposed workload and contribution. Please edit it and add notes to it, change dates, etc. Ideally, if we can step through each part in detail, covering specific features and functionality until fully discovered/exploited on each OS, prior to moving on to the next specific feature(s) and functionality, then we will all be able to better understand the problems, and create the list of priorities accordingly, based on what really matters. The following list needs to be added to until it is completely itemized and detailed, so both Programmers and Users can get on the same page, as we all strive to drive this forward in a very productive manner so we all end up with a much better uDig when all is said and done.

Server and content for Contributors: December 19th(Friday)
- Software & Services setup/configuration = Mark Leslie, --Ericjarvies
- Content/data preparation/creation = Mark Leslie, --Ericjarvies
uDig 2.1(trunk) release available for download by Contributors: December 19th(Friday).
- Windows packager = (Programmer?)
- OS X packager = (Programmer?)
- Linux packager = (Programmer?)
uDig 2.1 testing - Installation & Configuration: December 19th(Friday) - 21st(Sunday)
- Testers to report any/all problems with installation & configuration = (Testers? Bug Manager?)
uDig 2.1 testing - Local & Remote Data loading, setup and configuration: December 21st(Sunday) - 24th(Wed.)
- Testers to report any/all problems with data loading, data connections, & program errors related to data loading/connecting = (Testers? Bug Manager?)
uDig 2.1 testing - Preferences & Settings: on or before January 2nd(Friday)
- Testers to report any/all problems with uDig preferences and settings in combination with local and remote data = (Testers? Bug Manager?)
uDig 2.1 testing - Local & Remote Data editing: on or before January 9th(Friday)
- Testers to report any/all problems with local and remote database / data sets when editing, duplicating, exporting, importing, etc. = (Testers? Bug Manager?)
Jira Ticket cleaning/closing/merging of existing tickets based on findings from all recent testing on uDig 2.1: January 11th(Sunday)
- Review existing tickets and compare against all new reports by Testers = (Bug Manager?)
Jira Ticket Filings: January 11th(Sunday)
- Submit tickets on uDig Jira site = (Bug Manager?)

etc. etc. etc. more detail and direction...

Bug tickets review and re prioritization by contributing Programmers: January 11th(Sunday) through January 16th(Friday)
Code sprint: January 16th(Friday) through the 18th(Sunday).
- Users pitch-in to purchase pizza for each and every programmer working these 2-3 days. Need to make sure to locate pizza delivery places in each respective area that A. delivers, and B. accepts credit cards.

-SDK Documentation Manager, and three Programmers(one for each platform of Windows, OS X, and Linux) = (SDK Documentation Manager? Windows setup/instructions, OS X setup/instructions, Linux setup/instructions?)

-User Guide Documentation Manager = (User/Contributor?)

Attending people

Name	Rome +1	Bilbao	Baja California Sur
Andrea Antonello	*
Silvia Franceschi	*
Harry Bullen
Ugo Taddei
Mauricio Pazos		*
Aitor Lertxundi		*
Eric Jarvies			*
Mark Leslie
add yourself here

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.

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.

TASK	CHECKED BY
Make a set of shapefiles available. Best is to use shapefile containing exotic charsets like those used by italians or german or korean	I can provide a set of shapefiles(Point, Path, and Polygon), along with PostgreSQL(dB) and Geoserver(WMS) access to the same maps/layers(en español). --Ericjarvies 13:32, 12 December 2008 (UTC)
Loading of data without prj	meep
Selection of data and sorting in the table view	1. On OS X PPC/x86, when editing PostgreSQL/PostGIS layers, changes are not saved, and a nasty loopy bug is introduced, requiring restart of uDig. 2. Need to be able to adjust column width and rearrange columns, wherein user may exit table view, return to table view, without having those columns return to their previous state. --Ericjarvies 13:32, 12 December 2008 (UTC)
Create a project, save it, restart udig with project. Move the project folder and reopen it.	meep
...add here your thought... be mean!

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 - Will donate 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. --Ericjarvies 07:25, 16 December 2008 (UTC)

2. Sample data - Will donate 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). --Ericjarvies 07:28, 16 December 2008 (UTC)

Tutorial issues:

 * add your issue here

I will 'attempt' to find the time to create an OS X specific tutorial for SDK setup. --Ericjarvies 07:28, 16 December 2008 (UTC)

The Code Sprint

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

to be defined

@@ Line 12: / Line 12: @@
 This code sprint will take place mostly in IRC via udig's [http://udig.refractions.net/confluence/display/UDIG/IRC IRC channel].
-== Dates ==
+== Proposed Dates and Contributor Commitment ==
 The following is an initial and very rough draft of proposed workload and contribution.  Please edit it and add notes to it, change dates, etc.  Ideally, if we can step through each part in detail, covering specific features and functionality until fully discovered/exploited on each OS, prior to moving on to the next specific feature(s) and functionality, then we will all be able to better understand the problems, and create the list of priorities accordingly, based on what really matters.  The following list needs to be added to until it is completely itemized and detailed, so both Programmers and Users can get on the same page, as we all strive to drive this forward in a very productive manner so we all end up with a much better uDig when all is said and done.