Difference between revisions of "Udig round the world sprint"

Revision as of 03:14, 22 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 Contributor Commitment

1. Create uDig 1.2(trunk-test) distros for OSX PPC & x86, XP & Vista, and Linux. These are needed for user testing. Please Add your name to one/some/all of the following Operating systems if you are able to compile a usable uDig 1.2(trunk-test) for everyone else to download, install, test, and prepare bug reports accordingly. Please remember to post the d/l link(s) here.
- A. OS X packager = (Volunteer?)
- B. Windows packager = (Volunteer?)
- C. Linux packager = (Volunteer?)
2. Setup & configure test server/slices. The purpose of these servers are ot allow users the ability to install/configure server side services for use with uDig. Users who are interested will need to obtain ssh access, and should start by placing their name here( --Eric Jarvies, --Mark Leslie ). Also, please add to this list what you would like to see setup/configured on these slices, and of course, if you would like to help setup any of these server-side services, please request SSH acccess.
- A. Ubuntu, Apache, PHP, MySQL, Subversion/Trac, etc.
- B. GeoServer
- C. PostgreSQL/PostGIS
- D. TileCache
- E. ?
  - Update: 2 slicehost.com slices(1GB each)/IPs are ready to be configured. --Eric Jarvies, --Mark Leslie now have server access. If anyone else wishes to help setup various server-sided tools/resources for the purposes of users testing uDig against said types of server-sided services, please advise and we'll provide you with access accordingly --Eric Jarvies.
3. Content/data preparation/creation. The idea is to create a good collection of data that can be replicated across formats(shapefiles, PostgreSQL, etc.), so that the same geometry/data may be sampled/tested in various ways on/with various formats. This will allow all of us to test against the same server, service(s), and geometry(s)/data, whilst having the ability to easily/quickly make any changes on the server for any of it's running services. For example, if we are all testing an editing feature bug in uDig against a PostgreSQL/PostGIS database, we cna reference the same geometry and data when communicating with one another, and when we edit/commit changes, the other users can immediately see those changes(or not, in case of a bug)
4. SDK Documentation?
5. User Guide Documentation?
6. What is the top 10 list of uDig bugs that users would like to have stomped during this sprint? If a uDig Jira ticket exists for this bug, please link to it.
- 1-
- 2-
- 3-
- 4-
- 5-
- 6-
- 7-
- 8-
- 9-
- 10-
6. What is the top 10 list of uDig enhancements that users would like to have added during this sprint? If a uDig Jira ticket exists for this enhancement/feature request, please link to it.
- 1-
- 2-
- 3-
- 4-
- 5-
- 6-
- 7-
- 8-
- 9-
- 10-
  - Note: Items from the above two lists will represent what is actually addressed/worked on during the 2-3 day code sprint in January.

Code sprint is tentatively scheduled for January 16th(Friday) through the 18th(Sunday).
- Users pitch-in to purchase pizza for programmers whow will be working the 2-3 days during the sprint. Programmers, you should list your favorite pizza place here, along with their telephone number!

Committed Contributors

Name	Contribution Type	Operating System
Andrea Antonello Rome	Programming	Linux & Mac OSX
Silvia Franceschi Rome	Testing	Linux & Mac OSX
Harry Bullen	Programming
Ugo Taddei	Testing & Programming	Windows XP
Mauricio Pazos Bilbao	Programming
Aitor Lertxundi Bilbao	Programming
Eric Jarvies Cabo San Lucas, Baja California Sur, Mexico	Server, Admin, Testing	OS X PPC/x86
Mark Leslie	Host/Services Configuration
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.

@@ Line 25: / Line 25: @@
 ** E. ?
 *** ''Update: 2 slicehost.com slices(1GB each)/IPs are ready to be configured. --[[User:Ericjarvies|Eric Jarvies]],  --[[User:MarkLeslie|Mark Leslie]] now have server access.  If anyone else wishes to help setup various server-sided tools/resources for the purposes of users testing uDig against said types of server-sided services, please advise and we'll provide you with access accordingly --[[User:Ericjarvies|Eric Jarvies]]. ''
-* 3. Content/data preparation/creation.  The idea is to create a good collection of data that can be replicated across formats(shapefiles, PostgreSQL, etc.), so that the same geometry/data may be sampled/tested in various ways on/with various formats.
+* 3. Content/data preparation/creation.  The idea is to create a good collection of data that can be replicated across formats(shapefiles, PostgreSQL, etc.), so that the same geometry/data may be sampled/tested in various ways on/with various formats.  This will allow all of us to test against the same server, service(s), and geometry(s)/data, whilst having the ability to easily/quickly make any changes on the server for any of it's running services.  For example, if we are all testing an editing feature bug in uDig against a PostgreSQL/PostGIS database, we cna reference the same geometry and data when communicating with one another, and when we edit/commit changes, the other users can immediately see those changes(or not, in case of a bug)
 * 4. SDK Documentation?
 * 5. User Guide Documentation?

Difference between revisions of "Udig round the world sprint"

Revision as of 03:14, 22 December 2008

Contents