This is to notify you about a requirement for a deviation of
standard package naming for a part of Triquetrum, i.e. not
following the advised org.eclipse.<project>... naming. We've
got an OK for this from Wayne, on the related incubation mail
thread (cfr below).
For one of our lines of work, we will provide connectors to
external systems and to distributed resource managers (a.k.a.
grids etc).
DRMAA [1] is an interesting initiative to define a standard API
for job submission and monitoring on DRMs.
There is no standard Java API
source code available yet, let alone as an OSGi bundle, and we
would provide that in Triquetrum.
There is an advised binding definition though [2].
This requires using the package name
org.ggf.drmaa for the
API definition.
The DRMAA group has expressed interest to potentially use this as
the basis for a Java reference definition/implementation.
For actual implementations for concrete DRMS we will be using the
normal package naming rules.
regards
erwin
[1]
https://www.drmaa.org/
[2]
https://redmine.ogf.org/documents/11
-------- Doorgestuurd bericht --------
Yes. Use the package name space that makes the best technical
sense.
However... please ensure that the package name does not
infringe on trademarks held by others or that you follow the the
rules established for their use.
Also... bear in mind that I will completely forget that the
conversation occurred and at some point in the future (likely
when you're asking me to review an IP Log) I will almost
certainly ask you about the package name (we really need to come
up with a way to track this sort of thing).
It's a good idea to just let the PMC know that you're doing
this. They shouldn't push back, but it's good for them to know.
Wayne
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.
--
Wayne Beaton
@waynebeaton
The Eclipse Foundation