[Live-demo] OSGeo live - new candidate: Halestudio
Johan Van de Wauw
johan.vandewauw at gmail.com
Tue May 16 05:39:40 PDT 2017
I've proposed Hale in the past
https://lists.osgeo.org/pipermail/live-demo/2013-December/008557.html
So +1 here if we have a suitable install and enough space.
Technically speaking the current linux binaries include the jre and
the resulting package is definitely too large. It should use the
openjdk provided by ubuntu. We should then still check if the
application is still not too big.
Kind Regards,
Johan
On Tue, May 16, 2017 at 2:26 PM, Cameron Shorter
<cameron.shorter at gmail.com> wrote:
> Hi Dirk,
>
> Looking through your responses, Halestudio looks to be a very strong
> candidate for including on OSGeo-Live.
>
> Whether we have time to get it included in time for OSGeo-Live 11.0 is
> questionable.
>
> For prior projects we have often taken two releases to onboard the project
> to OSGeo-Live. Firstly we include the project in stealth mode. (It is
> installed, but the docs are not linked into the main docs, so new users
> don't accidentally use it. This gives us more time to do QA.
>
> I'll be interested to hear thoughts from other OSGeo-Live folks. I'd
> especially like to hear from anyone who has experience with Halestudio to
> hear their thoughts.
>
> Warm regards, Cameron
>
>
>
> On 15/5/17 10:44 pm, Dirk Frigne wrote:
>>
>> Hello,
>>
>> Hereby we would like to ask if hale studio is appropriate to be included
>> on the next OSGeoLive release.
>> Below you can find the answers to the application questions as described
>> on the wiki page.
>>
>> Kind regards,
>>
>>
>> Please describe your application:
>>
>> What is its name? hale studio
>> What is the home page URL?
>> https://www.wetransform.to/products/halestudio/
>> Which OSI-approved Open Source License is used? GNU Lesser General
>> Public Licence (LGPL) v3.0
>> What does the application do and how does it add value to the
>> Geospatial stack of software? hale studio enables you to transform and
>> harmonise spatial data, with a focus on highly complex data sets. Set up
>> reporting, analysis and data publishing workflows easily by defining
>> schema mappings. Furthermore, hale studio documents the data
>> transformation process and its impact on data quality.
>> Does the application make use of OGC standards? Which versions of
>> the standards? Client or server? You may wish to add comments about how
>> standards are used.
>> Read and write GML (2.1.2 to 3.3)
>> WFS client (1.1, 2.0, 2.0.2), including support for WFS
>> Transactions
>> WMS client (1.1.0, 1.1.1, 1.3.0)
>> Simple Features SQL
>> JSON (RFC 7159, ECMA-404)
>> GeoJSON (IETF RFC 7946)
>> What language is it written in? Java, Groovy
>> Which version of the application should be included in the next
>> OSGeo-Live release? 3.3.0
>>
>> Stability is very important to us on OSGeo-Live. If a new user finds a
>> bug in one application, it will tarnish the reputation of all other
>> OSGeo-Live applications as well. (We pay most attention to the following
>> answers):
>>
>> If risk adverse organisations have deployed your application into
>> production, it would imply that these organisations have verified the
>> stability of your software. Has the application been rolled out to
>> production into risk (ideally risk adverse) organisations? Please
>> mention some of these organisations
>> State of Hamburg (Germany)
>> State of Bavaria (Germany)
>> State of Rhineland-Palatinate (Germany)
>> Institute of Forest Management of Baden-Württemberg (Germany)
>> Armed Forces (Germany)
>> SMWA Sachsen (Germany)
>> GDI Südhessen (96 districts and municipalities in Germany)
>> Prisma Solutions (Austria)
>> IGP (Portugal)
>> IRCELINE (Belgium)
>> HL Consulting (Belgium)
>> Statkart (Norway)
>> European Environmental Agency (Denmark)
>>
>> Most of these organisations sponsor continued development of the
>> software through support contracts.
>>
>> Open HUB provides metrics to help assess the health of a project.
>> E.g.: http://adhoc.osgeo.osuosl.org/livedvd/docs/en/metrics.html Could
>> you please ensure that your project is registered with Open HUB, and
>> Open HUB has been updated to reference the correct code repository(s)
>> for your project. What is the Open HUB URL for your project?
>> https://www.openhub.net/p/halestudio
>> What is the size of the user community? You can often answer this by
>> mentioning downloads, or describing a healthy, busy email list?
>> Downloads per year: 4.000 to 5.000
>> Posts on the forum per year: 80 to 100
>> What is the size of your developer community?
>> At wetransform: 3 FTE
>> Outside wetransform: 2-3 major contributions per year, e.g.
>> SQLite reader, Geoserver app-schema integration
>> Do you have a bug free, stable release?
>> There are stable releases for production usage available since
>> release 2.0.1 (2010). A release history is available through GitHub:
>> https://github.com/halestudio/hale/releases
>> The latest release is 3.2.0, with version 3.3.0 being released
>> this week (19.05.2017)
>> Please discuss the level of testing that your project has gone
>> through.
>> hale studio's alignment creation and transformation capabilities
>> have been thoroughly tested in a multitude of data transformation
>> projects both by its developers as well as its open source user community.
>> Furthermore, continuous integration tests are performed by our
>> build infrastructure at https://builds.wetransform.to on every commit to
>> the master branch. The integration test suite is continuously extended
>> with every new feature or problem report. We publish detailed test
>> reports using Allure.
>> Every release candidate of hale studio undergoes additional
>> manual/explorative testing.
>> How long has the project has had mature code?
>> Version 1.0 of hale studio was released in December 2009. Since
>> the release of version 2.0.1 in 2010, the code base can be regarded
>> mature.
>> OSGeo-Live is targeted at applications that people can use rather
>> than libraries. Does the application have a user interface (possibly a
>> command line interface) that a user can interact with? (We do make an
>> exception for Incubated OSGeo Libraries, and will include Project
>> Overviews for these libraries, even if they don't have a user interface.)
>> hale studio has a graphical user interface to create
>> transformation projects and perform data transformations.
>> With around 50 applications installed on OSGeo-Live, us core
>> packagers do not have the time to liaise with every single project email
>> list for each OSGeo-Live release. So we require a volunteer (or two) to
>> take responsibility for liaising between OSGeo-Live and the project's
>> communities. This volunteer will be responsible for ensuring the install
>> scripts and English documentation are updated by someone for each
>> OSGeo-Live release. Also test that the installed application and
>> Quickstart documentation works as expected on release candidate releases
>> of OSGeo-Live. Who will act as the project's liaison person?
>> Simon Templer (st at wetransform.to)
>> Florian Esser (fe at wetransform.to) as backup
>> OSGeo-Live is Ubuntu Linux based. Our installation preference is:
>> 1. Install from UbuntuGIS or DebianGIS
>> 2. Install .deb files from a PPA
>> 3. Write a custom install script
>>
>> Can you please discuss how your application will be installed? A custom
>> installation script will be used to extract the application archive at
>> the appropriate location and create an application launcher.
>>
>> OSGeo-Live is memory and disk constrained. Can the application run
>> in 512 Meg of RAM?
>> Yes, though we recommend 1 GB or more. Very large/complex
>> transformation projects will benefit from 2GB+.
>> How much disk space will be required to install the application and
>> a suitable example application?
>> ~380 MiB including example data sets and Java runtime
>> We aim to reduce disk space by having all applications make use of a
>> common dataset. We encourage applications to make use of the example
>> datasets already installed:
>> http://wiki.osgeo.org/wiki/Live_GIS_Add_Project#Example_Datasets If
>> another dataset would be more appropriate, please discuss here. Is it
>> appropriate, to remove existing demo datasets which may already be
>> included in the standard release.
>> In the standard release, some demo datasets are included. These
>> may be removed for the installation on the OSGeo Live DVD. The default
>> ‘Natural Earth’ dataset could be used to illustrate the potential of the
>> application as an ETL tool with respect to INSPIRE and complex schemas.
>> However, this would be better illustrated by providing a more
>> specialized INSPIRE dataset.
>> Each OSGeo-Live application requires a Project Overview available
>> under a CC By and a Quickstart available under a CC By-SA license. (You
>> may release under a second license as well). Will you produce this?
>> Yes. Both the Project Overview and Quickstart will be created
>> based on the existing project documentation, help and demos.
>> In past releases, we have included Windows and Mac installers for
>> some applications. It is likely we won't have space for these in future
>> releases. However, if there is room, would you be wishing to include
>> Windows and/or Mac installers?
>> Both Windows and Mac installers exist for the project.
>
>
> --
> Cameron Shorter
> M +61 419 142 254
>
>
> _______________________________________________
> Live-demo mailing list
> Live-demo at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/live-demo
> http://live.osgeo.org
> http://wiki.osgeo.org/wiki/Live_GIS_Disc
More information about the Osgeolive
mailing list