Hi Robert,
From what I understand, a feature complete GUI SLD editor is something
that would be valuable for the Open Source community. If SLD Editor
provides such functionality, it would be a worthy addition.
With regards to including SLDEditor on OSGeoLive, from looking at your
application below, it looks like SLDEditor hasn't yet reached the level
of maturity we look for before including the project.
I'd be looking for indications that SLDEditor has been adopted more
widely, which provides validation that the community think this project
is good. In particular, it would be very valuable to see other
developers being attracted to the community. A very powerful form of
validation would be if your code were included into another project,
such as GeoServer.
What are your thoughts on integrating with existing mature projects?
Warm regards, Cameron
On 22/5/17 10:47 pm, Robert Ward wrote:
Looking at the timescales I appreciate I am late responding and it
will invalidate the application, however any feedback would be great.
Questionnaire answers attached.
__________________________________________________________________
*
Robert Ward*
Technical Architect – Enterprise Solutions & Defence
*SCISYS UK Limited*
T: +44 (0)1249 466575
E: [email protected] | www.scisys.co.uk
SCISYS UK Limited. Registered in England and Wales No. 4373530.
Registered Office: Methuen Park, Chippenham, Wiltshire SN14 0GB, UK.
Before printing, please think about the environment.
SLDEditor OSGeo-Live.txt
Please describe your application.
What is its name?
SLDEditor
What is the home page URL?
https://github.com/robward-scisys/sldeditor
Which OSI approved Open Source Licence is used?
GPL-3.0
What does the application do and how does it add value to the GeoSpatial stack
of software?
The aim of the project is to develop an application enabling the generation of
SLD files, where a user has complete control over all aspects of the OGC SLD
standard using a graphical interface.
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.
The application reads and writes files conforming to the OGC Styled Layer
Descriptor standard (version 1.1) as supported by the GeoTools library.
What language is it written in?
Java 1.8
Which version of the application should be included in the next OSGeo-Live
release?
Version 0.7.5
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?
The application has been used within SciSys and the generated data has appeared
in production systems.
I am not aware of how the application has been used and in which organisations.
Open HUB provides metrics to help assess the health of a project.
Eg: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/sldeditor
What is the size of the user community? You can often answer this by mentioning
downloads, or describing a healthy, busy email list?
1028 Downloads of the released applications @ 21/05/2017
What is the size of your developer community?
1
Do you have a bug free, stable release?
There are currently 1093 unit tests providing 75% code coverage. There are
also a series of integration tests that check:
* whether the application is displaying the expected values when an SLD file is
read
* if a value is updated in the GUI it appears in the generated SLD file
correctly
How long has the project has had mature code.
About a year.
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.)
We give preference to OSGeo Incubated Projects, or Projects which are presented
at FOSS4G conferences. If your project is involved in OSGeo Incubation, or has
been selected to be presented at FOSS4G, then please mention it.
The project was initially presented at FOSS4G UK, at Southampton in 2016.
OSGeo incubation status has been sought.
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.
Robert Ward,[email protected]
OSGeo-Live is Ubuntu Linux based. Our installation preference is:
Install from UbuntuGIS or DebianGIS
Install .deb files from a PPA
Write a custom install script
Can you please discuss how your application will be installed.
A Ubuntu PPA has been created to install the package from a .deb file.
OSGeo-Live is memory and disk constrained. Can the application run in 512 Meg
of RAM?
Yes
How much disk space will be required to install the application and a suitable
example application?
75MB
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.
I think the GeoServer SLD Cookbook datasets should be added to the OSGeo-Live
release. They are not part of the SLD Editor release however they are used in
the unit and integration testing.
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?
I can
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?
Mac installer exists.
Windows install could be created if required.
_______________________________________________
Live-demo mailing list
[email protected]
https://lists.osgeo.org/mailman/listinfo/live-demo
http://live.osgeo.org
http://wiki.osgeo.org/wiki/Live_GIS_Disc
--
Cameron Shorter
M +61 419 142 254
_______________________________________________
Live-demo mailing list
[email protected]
https://lists.osgeo.org/mailman/listinfo/live-demo
http://live.osgeo.org
http://wiki.osgeo.org/wiki/Live_GIS_Disc
