Re: [technology-pmc] Nomination of Exempt Pre-reqs for cloud software

[Andrew Ross <andrew.ross@xxxxxxxxxxx>]

Good news everyone! Approved.

I'll work with Jim to help finish off the process.

Special thanks to Jim for this, and to those who participated in the process.

Andrew

On 04/06/15 11:05, Andrew Ross wrote:

Hello Everyone,

Just as a quick status update, I've asked my colleagues to take a look at this. More soon.

Andrew

On 29/05/15 00:38, Rob Emanuele wrote:

+1 to having the mentioned dependencies be exempt pre-reqs. The only code we would want to distribute is client code that interfaces with pre-existing systems on user's machines. The version and setup of those frameworks on the user's machine will be entirely at their own discretion and will require their own installation.

The GeoTrellis dependency that Jim mentions deals with a transitive dependency of spark that our build process depends on. This gets a bit more tricky since the code we would be shipping with would not be the actual Spark system (that would be user installed), but the client code to interact with that system. I believe in Spark's case they don't make a distinction between the two, so client code pulls down a lot of dependencies what would otherwise be unneeded because they would be supplied by the installation. If the pre-req was exempt, and #3 of the benefits above holds, then that would certainly take a burden off of us for having to be responsible for transitive dependencies of the Apache Spark system that are pulled down by our build process.

On Thu, May 28, 2015 at 6:39 PM, Jody Garnett <jody.garnett@xxxxxxxxx> wrote:

My additional comments were for discussion only. My response is a +1.

I am happy to treat this category of "platform supplied" dependencies as exempt pre-reqs - specifically as it would not make sense for these dependencies to be distributed along side GeoMesa.

There is a similar platform story with Java Enterprise Edition and the servlet APIs, it is just the platform has a formal name and has been standardized across application server vendors.

--

Jody Garnett

On 22 April 2015 at 16:01, Jody Garnett <jody.garnett@xxxxxxxxx> wrote:

Thanks for the well organized post.

I am glad there is a category for exempt pre-reqs (as this software stack does form a foundation your software is built on - which you expect the customer to assemble before deploying your software).

Additional comments inline.

--

Jody Garnett

On 22 April 2015 at 14:03, Jim Hughes <jnh5y@xxxxxxxx> wrote:

Hi all,

As the PMC for LocationTech, we can identify various dependencies and ask that they be considered 'exempt prerequisites' by the EMO. To frame this discussion, check out https://eclipse.org/org/documents/Eclipse_Policy_and_Procedure_for_3rd_Party_Dependencies_Final.pdf.

If I'm understanding that pdf correctly, an exempt pre-req enjoys the following benefits:

1.  Projects would not need to file CQs for any version of the pre-req.
2.  Projects would be able to compile against new versions of an exempt pre-reqs without further discussion, etc.

When submitted are you submitting a specific version then? Actually that may be covered by there use as a compile time build dependency.

3.  Projects could ship code from an exempt pre-req's project.

Just to be clear, I think #1 and #2 are pretty standard and clear. For #3, I'm being aggressive in reading the document since it is silent and a broad interpretation will help with at least one use case*.

...

* In terms of shipping code, I *think* Rob mentioned a bit of GeoTrellis code which extended or required a bit of uncommonly deployed Spark code to add some monitoring capabilities.  If we can ship exempt pre-reqs, that may help with that corner case.

Three is indeed a bit tricky, we should wait for Rob to confirm. 

_______________________________________________
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