GvSIG CE Code Sprint in Berlin

From gvSIG CE Wiki

Jump to: navigation, search

gvSIG CE Code Sprint Berlin 2013

The gvSIG CE Team will organize a gvSIG CE Code Sprint in Berlin (Germany) from 22.11 until 25.11.2013. Developers and Users are invited to decide on the next steps of the project together.

Contents

Purpose

This second community sprint of gvSIG CE is a great opportunity to support the development of the project contributing actively to the source code, manuals or improving any aspects of gvSIG CE. The community sprint is a get-together for gvSIG CE project members and supporters and the best way to make decisions and treat larger problems. For this meeting developers, document writers, bug reporters, translators etc. are welcome!

Time and location

We are planning a three days hack fest.

Location: Topoi Building Dahlem

Freie Universität Berlin

Topoi Building Dahlem

Hittorfstraße 18

D-14195 Berlin

Duration: 22-25.11.2013 from approximately 9am-4pm

Agenda

Please write here which items we should discuss or write an email to our community list to discuss them together. Suggestion: We use the second code sprint mainly to continue the work that we started at the first code sprint: API clean-ups, gvtools, working in the webpage and wiki, language updates, etc.

Clean-up work

One of the main goals of this code sprint will be to get the code base into better shape:

  • Remove duplicated .jar files.
  • Remove all test classes and data.
  • Remove the manual from extHelp (move the useful stuff to the wiki, delete the rest).
  • Remove proprietary, unneeded or duplicate features and extensions. Candidates:
    • SEXTANTE native Java algorithms that duplicate SAGA modules
    • Wizard GUI for processing tools (can use SEXTANTE now; but keep tool GUIs)
      • Remove: /extGeoProcessing/src/com/iver/cit/gvsig/geoprocess/gui (?)
      • Remove: /extGeoProcessing/src/com/iver/cit/gvsig/geoprocess/manager
      • Remove: /extGeoProcessing/src/com/iver/cit/gvsig/geoprocess/wizard
    • gvSIG native processing tools that are also available via SEXTANTE
    • Remove extMeasureGeometry once all tools are in SEXTANTE
    • Remove custom menu system from Raster and Remote Sensing tools and move tools into SEXTANTE toolbox
    • Native drivers for formats also supported by Geotools/GDAL/OGR (no more libjni-gdal)
    • Java Advanced Imaging (dead since 2003!) -> use GDAL instead (keep, but ship Java-only)
    • Remove extJCRS, libProjection and libjni-proj4 after transition to GeoTools
    • Remove extJDBC after transition to GeoTools
  • Drop dead features that cannot realistically be maintained by us
  • Look for opportunities to refactor and "outsource" API parts
  • Identify low-hanging fruits for updates and improvements
  • Remove icon themes extension:
    • All config.xml must be modified in order to reference the actual icon instead of a "key".
    • There will be no need to register the icons in the initialize method of the extensions
    • All the tree under PluginServices.getIconThemeManager() and PluginServices.getIconTheme() could be removed.
  • API documentation
    • Start a new Wiki page with API-level programming hints
    • Update JavaDocs
  • Language updates
    • Find all hard-coded Spanish strings and translate them to English
    • Re-organize translation files: Merge all files from extension folders into one main file and resolve duplicates
    • Fix missing or wrong English translations

Bug fixing

  • Raise patch level to that of gvSIG 1.12 (final): evaluate those functionalities that should be integrated
  • Bugs with highest importance for the 1.0 release ("major", "crash" and "block"):
    • Fix everything that is marked "critical" or "blocker" on the bug tracker

GUI improvement

  • Find inconsistencies:
    • OK and Cancels buttons always present?
    • Always the same button order?
  • Annoyances:
    • Dialogs resizable when they should be?
    • Transient/non-transient as they should be?
    • Layout errors such as unneeded frames or wasted space?
    • Text field contents readable?
  • Labelling:
    • Are ":" and "..." used properly in all cases?
    • Do dialogs and buttons have meaningful titles/labels?
  • Menu items:
    • Correct order and groups?
    • Hotkeys working/appropriate?
    • Submenu system intuitive, everything in the place where it should be?
    • Do all context menu items and icons have corresponding entries in the main menu?
    • Should the context menu be extended/reduced?
  • Where to put the Raster Tools functions?
  • Where to put the SEXANTE tools?
  • Add Shortcuts

Geotools integration improvements

As a result of last codesprint, a branch called gvtools has been created which is totally based on GeoTools. This branch has very few functionalities and we are adding functionality from the main branch little by little. For detailed information on the precedents see Geotools in gvSIG CE.

The following functionalities are interesting since they would give the gvtools branch the possibility to create symbology, export to SLD (and import in GeoServer with full compatibility), and compose layouts. While it is not possible to finish this in a codesprint it may be interesting to advance on these lines.

  • Symbology: In the latest weeks some effort has been invested on the migration of the symbology extensions to the gvtools branch. It would be a good opportunity to add more functionality and to agree on the way the GeoTools symbology will be managed in the gvtools branch at an internal level.
  • Addition of the layout designer extensions. Fernando G. has the feeling that this extension is not based strongly on gvSIG API. In that case could be easy to migrate. It may be worth to take a look on the work of gvSIG 2.0 related to this functionality.
  • Upgrade GeoTools version. It may be also worth to upgrade to the latest Geotools version which, at least, will include an improvement on the speed of selecting features.

SEXTANTE

The manual of the last Version ( 22/3/2013) of SEXTANTE has been updated. We will discuss how to bring this information and the help of all algorithms into the web (wiki, sphinx, etc)

New features

  • Best patches from 1.11:
    • Extension org.gvsig.consecutivenumber
    • Functionality "split lines" of geoprocessing tools
    • Functionality "lateral buffer" of geprocessing tools
  • Best patches from 1.12:
    • Some improvements in TOC usability
    • Some usability improvements
    • Bugfixes in Postgis driver
    • Improvements in table join and ODBC conexions.
    • WMS 1.3 and new versions of KML
  • Integrate Kevin Well's color tables
  • Integrate GGL2
  • Automatic loading and applying of vector layer styles
  • SEXTANTE 1.0 + GRASS + SAGA + bug fixes
  • Navtable
  • Create a Recent Projects option under the File menu.

Documentation

  • Update Website
  • Wiki cleanup
  • SEXTANTE & gvSIG CE help pages in Wiki
  • gvSIG CE Outreach (product brochures, conference posters, etc.)
  • gvSIG CE annual report
  • Use Cases
  • Social networking

Project Organization

  • gvSIG CE & OSGeo (get information; prepare for incubation after gvSIG CE 1.0). gvSIG CE Team will work following The OSGeo Way preparing ourselves for the incubation process.
  • Sponsorship program
  • Plan the gvSIG CE Project Steering Committee
  • Discuss the gvSIG CE Enterprise list
  • Release process
  • Source Control Management system (change to GIT?)

GIT crash course

Even if we don't change to GIT it will be interesting to have a first contact with GIT for the members that do not know it yet.

Costs

Please keep in mind that all participants are volunteering several days of their time in addition to paying for their own travel and hotel expenses.

Participants should plan for the following costs:

  • Travel to Berlin, variable depending on where you are.
  • Accommodation for four nights, 60 €-90 € depending on what room you choose.
  • Breakfast, lunch, and other snacks.

Preparation

Please join the mailing list at: gvSIG CE users list

Remote Participation:

If you can not make it to Berlin in person, and you still want to actively participate, there will be a chance to do it by joining the event on IRC. If you are interested in remote participation, feel free to add yourself below.

Equipment needed:

List of participants

You are welcome to join us and bring new ideas with you. Please add your name an email adresse to the list. The following people will attend our first code sprint:

  • Benjamin Ducke <benducke[at]fastmail.fm>
  • Fernando González <fernando.gonzalez[at]geomati.co>
  • Ruth Schönbuchner <ruth.schoenbuchner[at]csgis.de>
  • Jose Canalejo <jose.canalejo[at]csgis.de>
  • Víctor González <victor.gonzalez[at]geomati.co>
  • Add you name

Announcement

The code sprint will be announced on the following lists:

  • gvsigce-community@lists.sourceforge.net 16px-Ok.png
  • gvsigce-users@lists.sourceforge.net 16px-Ok.png
  • Geotools-gt2-users@lists.sourceforge.net
  • fossgis-talk-liste@fossgis.de
  • Slashgeo
  • discuss@lists.osgeo.org
  • grass-dev@lists.osgeo.org
  • saga-gis-developer@lists.sourceforge.net
  • add your list

FAQ

What is a code sprint?

A code sprint is getting developers for a set amount of time and just writing code. Participants will learn from others, but the focus is not on instruction. A significant benefit of sprinting is that the project members meet in person, socialize, and start to communicate more effectively than when working together remotely.

Pictures

Next Code Sprint

The Next Code Sprint in 2014 will be held in ... (to be discussed in Berlin):

  • a) Toulouse (France)
  • b) Santiago de Compostela (Spain)
  • c) Add a location

Summary