Thank you Mike for the fast reply.
In the meantime I have also received a reply from the DRMAA WG, and it
appears it is allowed to re-deliver the Java interface definitions with
an EPL license. I.e. they only protect their specification documents,
implementors are allowed to (re)distribute actual code with any
preferred open- or closed-source license. So i.o. reusing the jars from
Sun/Oracle or of Son of Grid Engine we could deliver our own bundle jars
then.
/
//So now the issue has potentially changed into : can I deliver an API
with a predefined (non-eclipse) namespace as part of Triquetrum?//
//More concretely, the package name should be //org.ggf.drmaa//for the
interfaces/API./
I couldn't find a detailed statement about such a need, to provide
externally specified APIs, on e.g.
https://wiki.eclipse.org/Development_Resources/HOWTO/The_Eclipse_Code_Namespace_Policy
Implementations for specific grid technologies would be free to use the
normal org.eclipse.triquetrum namespace.
(I would still go through the CQ process for the implementation for SGE
as that is based on a JNI binding to a C implementation from Sun)
thanks again,
erwin
Op 27/06/2016 om 19:02 schreef Mike Milinkovich:
Erwin,
SISSL [1] has not been previously used or approved for use at
Eclipse. Our process (defined in Section A of [2] if you are
interested) requires that new licenses be unanimously approved by the
Board. Based on a preliminary review of the license, it looks like
the license should be okay. As with all licenses, adherence to the
license terms would be necessary and a special note should be made of
the requirements of Section 3.1.
So in other words, if you want to use this SISSL-licensed dependency,
we can probably make it work. The first step would be to open a CQ to
get the IP team started on the necessary reviews and license approvals.
Hope that helps.
[1] https://opensource.org/licenses/SISSL
[2]
http://www.eclipse.org/org/documents/2015.12.08.Implementing.the.IP.Policy.pdf
On 2016-06-23 10:58 AM, erwindl0 wrote:
Dear all,
For Triquetrum we want to include (optional) connectors to grids /
distributed resource managers.
This would be done via the DRMAA api [1] and corresponding
implementations for different grid implementations.
For DAWN (not its Eclipse project part) I have already repackaged the
DRMAA v1 api as an OSGi bundle, and in the meantime we have
implementations available for SGE [2] and SLURM [3]. Others could be
added when there's an interest. I would like to contribute this work
to Triquetrum.
The DRMAA v1 API was originally licensed with the so-called SISSL [4]
which has been retired in the meantime.
The implementations could be brought in with an EPL license.
Questions :
- is the SISSL compatible with an Eclipse product delivery?
- can I include/contribute the API bundle in the Triquetrum
repository as sources?
- if yes, can I then maintain the SISSL header/license?
- if not, can it be included as a "works-with" 3rd-party dependency?
thanks!
erwin
[1] https://www.drmaa.org/
[2] https://en.wikipedia.org/wiki/Oracle_Grid_Engine and
https://arc.liv.ac.uk/trac/SGE
[3] http://slurm.schedmd.com/
[4] https://en.wikipedia.org/wiki/Sun_Industry_Standards_Source_License
_______________________________________________
incubation mailing list
[email protected]
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/incubation
_______________________________________________
incubation mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://dev.eclipse.org/mailman/listinfo/incubation
