[PROJ] Put PROJ-JNI bindings under PROJ wing?

[Even Rouault]

Martin,

at the very least, those new gen bindings should be mentionned in the documentation in 
https://proj.org/development/bindings.html . Please submit a PR.

My personal view, not speaking on behalf of the PSC:

Regarding putting them more formally under PROJ umbrella, I'm less convinced. We would 
need more than one person in the team with deep interest in them, and I'm not sure that's 
currently the case. Other bindings exist by themselves, with their own way of managing 
themselves, with very good cooperation with PROJ core when needed, and some really shine 
with this setup. I'm not sure why having PROJ-JNI under PROJ umbrella or not would change 
your interest in it.

If you're looking for some kind of official affiliation, I guess you could apply to register PROJ-
JNI as a OSGeo community project. The requirements for that are pretty low (much less than 
a OSGeo graduated project). Regarding hosting of the git repo itself, having it under 
github.com/OSGeo could have some disadvantages as we share some CI ressources like 
Travis-CI and AppVeyor at the organization level, and they are already quite heavily stressed 
by existing projects (especially for AppVeyor where we only have 1 concurrent build for the 
whole organization and delays of several hours can happen).

The existence of the separate PROJ-data git repo is mostly because of its large size.

Even

-- 
Spatialys - Geospatial professional services
http://www.spatialys.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/proj/attachments/20200416/756b9d9b/attachment.html>