Difference between revisions of "Udig round the world sprint"

From OSGeo
Jump to navigation Jump to search
m
 
(24 intermediate revisions by 5 users not shown)
Line 1: Line 1:
−
__TOC__
+
THIS EVENT IS PASSED. TO GET INFORMATION ABOUT WHAT HAPPENED, PLEASE VISIT THIS SITE:
 +
 
 +
http://udig.refractions.net/confluence/display/HACK/Code+Sprint+Jan+2009
 +
 
 +
-----
 +
-----
 +
-----
 +
 
  
 
== Udig round the world - code sprint ==
 
== Udig round the world - code sprint ==
Line 12: Line 19:
 
This code sprint will take place mostly in IRC via udig's [http://udig.refractions.net/confluence/display/UDIG/IRC IRC channel].
 
This code sprint will take place mostly in IRC via udig's [http://udig.refractions.net/confluence/display/UDIG/IRC IRC channel].
  
−
== Proposed Dates and Contributor Commitment ==
+
== 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( --[[User:Ericjarvies|Eric Jarvies]], --[[User:MarkLeslie|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. Please list any and all server-side applications/services you would like to have running/working/available on the above mentioned test server:
 +
** A. Ubuntu, Apache, PHP, MySQL, Subversion/Trac''(installed)''
 +
** B. GeoServer(version #?)
 +
** C. PostgreSQL/PostGIS (version #'s?)
 +
** D. TileCache(version #?)
 +
** E. Ruby
 +
** F. Python
 +
** G. ???
 +
''Update: 2 slicehost.com slices(1GB each)/IPs are up and running, and have Apache, PHP, and MySQL installed. --[[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.  Create a standard geo-dB set(Point, LineString, Polygon, MultiPoint, MultiLineString, MultiPolygon, and GeometryCollection), then serve this standard set on each of the following geometry-enabled services:
 +
** 1. MySQL
 +
** 2. PostgreSQL(PostGIS extension)
 +
** 3. IBM DB2
 +
** 3. Oracle Spatial
 +
** 4. SQL Server 2008
 +
And then the same data output the following ways:
 +
** 1. dB direct(PostGIS, DB2, Oracle, and MySQL)
 +
** 2. WFS via GeoServer
 +
** 3. ?
 +
As well as serving the above-mentioned geometry/data as WMS via Geoserver.
 +
 
 +
----
 +
 
 +
* 4. Prior to the code sprint, we want to find all of the critical bugs, and many other bugs.  uDig discussion about something that does not work, or works a certain incorrect or partial way, or anything else, please start posting those below:
 +
** A. Create a project, save it, restart udig with project. Move the project folder and reopen it.
 +
** B. Loading of data without prj
 +
** C. Selection of data and sorting in the table view
 +
** D. On OS X PPC/x86, when editing a PostgreSQL/PostGIS layer, changes are not saved after being committed, and a nasty loopy bug is introduced, requiring a restart of uDig. 
 +
** E. 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.
 +
** F. more...
 +
''Note: 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.''
 +
 
 +
----
  
−
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.  
+
* 5. 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
  
−
* Server and content for Contributors: December 19th(Friday)
+
----
−
** Software & Services setup/configuration = Mark Leslie, --[[User:Ericjarvies|Ericjarvies]]
 
−
** Content/data preparation/creation = Mark Leslie, --[[User:Ericjarvies|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...
+
* 6. SDK Documentation?
  
−
* 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.
 
  
 +
* 7. 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-
  
−
-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?)
+
* 8. 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 ==
 
== Committed Contributors ==
Line 57: Line 118:
  
 
|-
 
|-
−
|[[User:Moovida | Andrea Antonello]] Rome || Programming || Linux & Mac OSX || ||  
+
|[[User:Moovida | Andrea Antonello]] Rome || Programming || Linux & Windows Vista || ||  
 
|-
 
|-
 
| [[User:Silli | Silvia Franceschi]] Rome || Testing || Linux & Mac OSX || ||  
 
| [[User:Silli | Silvia Franceschi]] Rome || Testing || Linux & Mac OSX || ||  
Line 65: Line 126:
 
| [[User:Tupi | Ugo Taddei]] || Testing & Programming || Windows XP || ||  
 
| [[User:Tupi | Ugo Taddei]] || Testing & Programming || Windows XP || ||  
 
|-
 
|-
−
| [[User:mauricio.pazos | Mauricio Pazos]] Bilbao || Programming || ||  ||  
+
| [[User:mauricio.pazos | Mauricio Pazos]] Bilbao || Testing & Programming || Linux ||  ||  
 
|-
 
|-
−
| [[User:Aitorlertxundi | Aitor Lertxundi]] Bilbao || Programming || ||  ||  
+
| Aritz Davila Bilbao || Testing & Programming || Linux ||  ||  
 
|-
 
|-
−
| [[User:Ericjarvies | Eric Jarvies]] Cabo San Lucas, Baja California Sur, Mexico || Server, Admin, Testing || OS X PPC/x86|| ||  
+
| [[User:Aitorlertxundi | Aitor Lertxundi]] Bilbao || Testing || Windows XP ||  ||
 +
|-
 +
| [[User:Ericjarvies | Eric Jarvies]] Cabo San Lucas, Baja California Sur, Mexico || Server, Admin, Testing || OS X PPC/x86|| Will work on creating some Jira associations(as it relates to components) we can all use for reference use on Wiki|| Will work on uDig GUI examples(images and videos) suggesting layout and button improvements, feature and functionality improvement, and bugs in action.
 
|-
 
|-
 
| [[User:MarkLeslie | Mark Leslie]] || Host/Services Configuration || || ||  
 
| [[User:MarkLeslie | Mark Leslie]] || Host/Services Configuration || || ||  
 +
|-
 +
| [[User:EmilyGouge | Emily Gouge]] Victoria || Programming/Testing || || ||
 
|-
 
|-
 
|add yourself here ||  || ||  
 
|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.
 
−
* 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.
 
−
 
−
{| border="1" cellpadding="2" class="wikitable"
 
−
!width="70%"|TASK
 
−
!width="30%"|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).
 
−
--[[User:Ericjarvies|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.
 
−
--[[User:Ericjarvies|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.
 
−
--[[User:Ericjarvies|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). --[[User:Ericjarvies|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.
 
−
--[[User:Ericjarvies|Ericjarvies]] 07:28, 16 December 2008 (UTC)
 
−
 
−
== The Code Sprint ==
 
−
 
−
=== Triage: Tasks that were chosen to be fixed during the sprint ===
 
−
 
−
to be defined
 
−
 
−
 
−
 
−
 
−
 
−
 
−
 
  
 
[[Category:Code Sprints]]
 
[[Category:Code Sprints]]
 +
[[Category:Past Events]]

Latest revision as of 02:15, 4 September 2011

THIS EVENT IS PASSED. TO GET INFORMATION ABOUT WHAT HAPPENED, PLEASE VISIT THIS SITE:

http://udig.refractions.net/confluence/display/HACK/Code+Sprint+Jan+2009


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. Please list any and all server-side applications/services you would like to have running/working/available on the above mentioned test server:
    • A. Ubuntu, Apache, PHP, MySQL, Subversion/Trac(installed)
    • B. GeoServer(version #?)
    • C. PostgreSQL/PostGIS (version #'s?)
    • D. TileCache(version #?)
    • E. Ruby
    • F. Python
    • G. ???

Update: 2 slicehost.com slices(1GB each)/IPs are up and running, and have Apache, PHP, and MySQL installed. --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. Create a standard geo-dB set(Point, LineString, Polygon, MultiPoint, MultiLineString, MultiPolygon, and GeometryCollection), then serve this standard set on each of the following geometry-enabled services:
    • 1. MySQL
    • 2. PostgreSQL(PostGIS extension)
    • 3. IBM DB2
    • 3. Oracle Spatial
    • 4. SQL Server 2008

And then the same data output the following ways:

    • 1. dB direct(PostGIS, DB2, Oracle, and MySQL)
    • 2. WFS via GeoServer
    • 3. ?

As well as serving the above-mentioned geometry/data as WMS via Geoserver.

  • 4. Prior to the code sprint, we want to find all of the critical bugs, and many other bugs. uDig discussion about something that does not work, or works a certain incorrect or partial way, or anything else, please start posting those below:
    • A. Create a project, save it, restart udig with project. Move the project folder and reopen it.
    • B. Loading of data without prj
    • C. Selection of data and sorting in the table view
    • D. On OS X PPC/x86, when editing a PostgreSQL/PostGIS layer, changes are not saved after being committed, and a nasty loopy bug is introduced, requiring a restart of uDig.
    • E. 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.
    • F. more...

Note: 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.

  • 6. SDK Documentation?
  • 7. 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-
  • 8. 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 Components GUI
Andrea Antonello Rome Programming Linux & Windows Vista
Silvia Franceschi Rome Testing Linux & Mac OSX
Harry Bullen Programming
Ugo Taddei Testing & Programming Windows XP
Mauricio Pazos Bilbao Testing & Programming Linux
Aritz Davila Bilbao Testing & Programming Linux
Aitor Lertxundi Bilbao Testing Windows XP
Eric Jarvies Cabo San Lucas, Baja California Sur, Mexico Server, Admin, Testing OS X PPC/x86 Will work on creating some Jira associations(as it relates to components) we can all use for reference use on Wiki Will work on uDig GUI examples(images and videos) suggesting layout and button improvements, feature and functionality improvement, and bugs in action.
Mark Leslie Host/Services Configuration
Emily Gouge Victoria Programming/Testing
add yourself here
Retrieved from "http://wiki.osgeo.org/w/index.php?title=Udig_round_the_world_sprint&oldid=57003"