[Live-demo] Project to be included on OSGeo Live GIS Disc - 52N WSS

Cameron Shorter cameron.shorter at gmail.com
Wed Jun 29 05:37:30 PDT 2011


Thank you Jan,
Based on your answers, I believe that the 52N WSS would be an excellent 
addition to OSGeo-Live.

Unless someone notes any further concerns within the next 24 hours, I 
would like to suggest that the 52N WSS should be included on OSGeo-Live. 
As such, I recommend you start working on your installers ASAP to meet 
our feature freeze.

Re your question below about "Risk adverse". Computer hackers, and 
universities are usually considered risk tolerant as they are more 
likely to accept buggy software.
Government and Defence, are often considered risk adverse, as they often 
require a higher level of testing before putting into production.

On 29/06/11 22:19, Jan Drewnak wrote:
> Please find my responses in-line.
>
>
> Jan
>
>> -----Original Message-----
>> From: Cameron Shorter [mailto:cameron.shorter at gmail.com]
>> Sent: Friday, June 10, 2011 10:53 PM
>> To: Jan Drewnak
>> Cc: live-demo at lists.osgeo.org
>> Subject: Re: [Live-demo] Project to be included on OSGeo Live GIS Disc
>>
>> Thank you for your application Jan. A Web Security Service will be an
>> excellent addition to OSGeo-Live.
>> I have a couple of extra questions in line below.
>>
>> On 10/06/11 22:31, Jan Drewnak wrote:
>>> Dear list, Cameron,
>>>
>>> I ask you to include our project "52┬░North Web Security Service" on the
>>> OSGeo Live Disc. Please find the details below, based on the questions
>>> documented at http://wiki.osgeo.org/wiki/Live_GIS_Disc_Apply.
>>>
>>>
>>> Thanks,
>>>
>>>     Jan
>>>
>>>
>>> * Please describe your application.
>>> ** What is its name?
>>> -- 52┬░North Web Security Service
>>>
>>> ** What is the home page URL?
>>> -- http://52north.org/communities/security/wss/2.2/index.html
>>>
>>> ** Which OSI approved Open Source Licence is used?
>>> -- GNU GPL 2.0
>>>
>>> ** What does the application do and how does it add value to the
>>> GeoSpatial stack of software?
>>> -- The application adds a security layer to any kind of geospatial Web
>>> applications and services, acting as a proxy, without the need to modify
>>> existing services. It provides policy-based authorization and
>>> authentication features to restrict access to spatial layers, features,
>>> and other resources provided by OGC Web Services.
>> Very nice. Would it be possible to lock down a WFS to a specific filter?
>> Eg: A user is only able to query features that are within a specific
>> polygon?
> Yes, it is. What the software actually does in that case is -- based on
> the applicable policy -- adding a Filter Encoding expression to the
> request before forwarding it to a protected WFS.
>
>
>>> ** What language is it written in?
>>> -- Java
>>>
>>> ** Which version of the application should be included in the next
>>> OSGeo-Live release?
>>> -- 2.2.0 (final)
>> I understand that 2.2 is currently in beta. Have you had a previous
>> stable version?
>> Maybe 2.1 or 1.0?
> We have 2.1 but I'd really prefer to add 2.2.0 final because of improved
> support for SOS and WPS.
>
>>> * Stability is very important to us on OSGeo-Live and we pay most
>>> attention to the following answers. If a new user finds a bug in one
>>> application, it will tarnish the reputation of all other OSGeo-Live
>>> applications as well.
>>> ** Has been rolled out to production in a number of locations? Can you
>>> mention some risk adverse organizations who use your application?
>>> -- Used in some administrative units in federal states of germany
>> Can you please expand on this. Has the application been deployed into
>> production or is it just in a R&D prototype?
> It has been deployed into production, though the actual number of
> production deployment is unknown. However, the core of the software is
> used in a closed source proprietary product (making use of the 52n
> dual-licensing) that is deployed in a big number of production
> environments.
>
>> I assume that these administrative units of federal states are part of
>> government? Would you consider these organisations to be risk adverse
>> themselves?
> Could you specify what you mean by "risk adverse"? In what sense?
>
>> If departments would be ok to be named, it would be nice if you could
>> name one or two of them.
> I needed to ask for permission first, but I assume yes.
>
>>> ** What is the size of the user community and developer community? You
> can
>>> often answer this by mentioning downloads, or describing a healthy, busy
>>> email list?
>>> -- About 500 download of latest beta release
>>>
>>> ** Do you have a bug free, stable release?
>>> -- Scheduled for end of June, current state is beta.
>>>
>>> ** Please discuss the level of testing that your project has gone
> through.
>>> -- Deployed on various Windows and Linux platforms, Tomcat versions,
>>> tested with several WMS, WFS, WPS, and SOS.
>>>
>>> ** How long has the project has had mature code.
>>> -- First version established in late 2004
>>>
>>> * 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?
>>> -- Web UI to set up protected services; policies and users are managed
>>> trough XML config files.
>>>
>>> * We give preference to OSGeo Incubated Projects, or Projects which are
>>> presented at [http://foss4g.org FOSS4G] conferences. If your project is
>>> involved in OSGeo Incubation, or has been selected to be presented at
>>> FOSS4G, then please mention it.
>>> -- presented in 2007 to 2009
>>>
>>> * 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.
>>> -- liaison person is Jan Drewnak (j.drewnak at 52north.org)
>>>
>>> * 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.
>>> -- Application is installed by script that copies the applications war
>>> file into a tomcat webapp folder
>>>
>>> * OSGeo-Live is memory and disk constrained. Can the application run in
>>> 512 Meg of RAM?
>>> -- definitely
>>>
>>> * How much disk space will be required to install the application and a
>>> suitable example application?
>>> -- about 35 MB
>>>
>>> * 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.
>>> -- datasets not needed; data that comes with application has very small
>>> footprint (couple of kB)
>> We have a few web services installed on OSGeo-Live already. It would be
>> good if your quickstart could make use of one of these.
>> For example, I understand the mapserver WMS/WFS doesn't require any
>> extra memory from a tomcat instance in order to run. You might want to
>> make use of it.
> I will try to work with them.
>
>>> * 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?
>>> -- No
>>>
>>>
>>>
>>
>> --
>> Cameron Shorter
>> Geospatial Director
>> Tel: +61 (0)2 8570 5050
>> Mob: +61 (0)419 142 254
>>
>> Think Globally, Fix Locally
>> Geospatial Solutions enhanced with Open Standards and Open Source
>> http://www.lisasoft.com
>>
>


-- 
Cameron Shorter
Geospatial Director
Tel: +61 (0)2 8570 5050
Mob: +61 (0)419 142 254

Think Globally, Fix Locally
Geospatial Solutions enhanced with Open Standards and Open Source
http://www.lisasoft.com




More information about the Osgeolive mailing list