Re: [technology-pmc] "Works with" dependency for GeoServer (subset)

[Wayne Beaton <wayne@xxxxxxxxxxx>]

Actually, before we go there...

Is this templating feature what you mean by "custom pages"?

http://docs.geoserver.org/latest/en/user/tutorials/GetFeatureInfo/index.html

Or is it something else? Can you give me a pointer to a specific example?

Wayne

On 24/11/14 11:35 AM, Wayne Beaton wrote:

My apologies for dropping the ball.

The GeoServer project is aware of these limitations and has a "community module" section that can be used host optional integration such as custom pages. For many DataStores the connection parameters described by DataStoreFactorySpi is descriptive enough to generate a connection page.

If I understand this correctly, as long as the GeoMesa project uses this "community module" as the Glue to GeoServer, you believe that we're in good shape.

Is that accurate?

Wayne

On 23/09/14 11:54 AM, Jody Garnett wrote:

Yes that was my understanding.

Indeed this understanding led to the geogig geoserver module being removed from our initial contribution.

Jody

Jody Garnett

On Mon, Sep 22, 2014 at 6:47 PM, Wayne Beaton <wayne@xxxxxxxxxxx> wrote:

Hi Jody.

I'm not sure that I understand your concern. I think that there might be a missing question.

Is it your concern that the implementation of a GeoServer interface constitutes linking?

Wayne

On 22/09/14 06:23 PM, Jody Garnett wrote:

This should be a clear works with dependency.

* Custom DataStore configuration page to allow a GeoMesa DataStore to be used in GeoServer. 

This could be a toned down to "works with GeoTools". 

* Implementation of various WPS processes, such as import into GeoMesa, an enhanced heat map, and various analytics. 

In general WPS processes could be toned down to "Works with GeoTools".

A custom "Import into GeoMesa" may require access to GeoServer catalog? See discussion on GPL below...

* Custom GeoServer pages that allow monitoring and inspection of GeoMesa data

This is tricky as it requires making use of GPL interfaces.

I always found it confusing as the language used in source code licenses refers to linking - a concept which does not directly match what we do in Java.

I could see this two ways:

1) Custom pages depend on GeoServer API to compile, but cannot be instantiated by the JVM unless deployed in a GeoServer environment. Result: Custom page is not "linked" and can be distributed as with GeoMesa project.

2) Custom page implements GeoServer interface, considered GPL, and cannot be disturbed with main GeoMesa project. For GeoGig we chose this interpretation (separated "tight" GeoServer integration out into a seperate project) to avoid any use of GPL license.

The GeoServer project is aware of these limitations and has a "community module" section that can be used host optional integration such as custom pages. For many DataStores the connection parameters described by DataStoreFactorySpi is descriptive enough to generate a connection page.

If a custom page is not considered to be GPL we would happily fold our GeoServer integration back into the GeoGig project (rather than create a community module).

--

Jody

Per the Guidelines for the Review of Third Party Dependencies [2]:

The Eclipse software does not require the third party software to be present. If the third  
party software happens to be present, the Eclipse software may call or invoke it.  
Example: If a web browser is present, clicking on URL's in Eclipse will cause the user's  
configured web browser to open the URL.  

If you have any concerns, please make them known on this thread. If you are satisfied with the laid out criteria and are confident that this qualifies as a "works with" dependency, please express your approval with a +1 on this thread.

I'll leave this thread open for a couple of days to give all members a chance to express their concerns/approval. I'll set the flag on the CQ.

Thanks,

Wayne

[1] https://dev.eclipse.org/ipzilla/show_bug.cgi?id=8744
[2] https://www.eclipse.org/org/documents/Eclipse_Policy_and_Procedure_for_3rd_Party_Dependencies_Final.pdf

--
Wayne Beaton
@waynebeaton
The Eclipse Foundation

_______________________________________________
technology-pmc mailing list
technology-pmc@xxxxxxxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://locationtech.org/mailman/listinfo/technology-pmc

_______________________________________________
technology-pmc mailing list
technology-pmc@xxxxxxxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://locationtech.org/mailman/listinfo/technology-pmc

--
Wayne Beaton
@waynebeaton
The Eclipse Foundation

_______________________________________________
technology-pmc mailing list
technology-pmc@xxxxxxxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://locationtech.org/mailman/listinfo/technology-pmc

_______________________________________________
technology-pmc mailing list
technology-pmc@xxxxxxxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://locationtech.org/mailman/listinfo/technology-pmc

--
Wayne Beaton
@waynebeaton
The Eclipse Foundation

_______________________________________________
technology-pmc mailing list
technology-pmc@xxxxxxxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://locationtech.org/mailman/listinfo/technology-pmc

--
Wayne Beaton
@waynebeaton
The Eclipse Foundation