| Re: [technology-pmc] Nomination of Exempt Pre-reqs for cloud software |
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 GarnettOn 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.