<div dir="ltr"><div dir="ltr">Edzer:</div><div dir="ltr"><br></div><div>I have setup "edzer" with "project author" permissions to create a project on the osgeo website, when you have something ready (or need any assistance figuring out wordpress) let us know. The page for <a href="https://www.osgeo.org/community/getting-started-osgeo/add-service-provider/">service providers</a> is a good example of how everything is broken into tabs.</div><div dir="ltr"><br></div><div dir="ltr">Having a dual license (MIT and GPL-2) is just fine and can really be used to reflect your participants values etc.... Indeed a dual license approaches can be very valuable as each encourages a different balance of responsibility and assurances.</div><div><br></div><div>Examples for your team:</div><div><ul><li>The JTS project has a dual license (<a href="https://github.com/locationtech/jts/blob/master/LICENSES.md">LICENSE.md</a>) of BSD (permissive license promoting wide adoption) and Eclipse License (promoting some projection against patents and so forth). This is a good example of how to do a dual license.</li><li>When you have a dual license approach some care is needed in accepting contributions from others: As an example we have run into the GeoServer project which as GPL (with a small exception allowing some eclipse license code). Normally we collect a CLA for all contributions (so we have the ability to donate code to other projects like GeoTools and JTS). Recently some folks collected some code that was abandoned and the original authors were no longer available to sign a CLA. The result is our codebase now has some extensions with LICENSE.md files in specific directories.</li><li>It can also be a challenge to communicate what is going on when working with a codebase that has collected influence from different sources. I just updated the GeoTools codebase with its core LGPL <a href="https://github.com/geotools/geotools/blob/main/LICENSE.md">LICENSE.md</a>, followed by a clear <a href="https://github.com/geotools/geotools/blob/main/licenses/README.md">notice</a> describing listing all the individual <a href="https://github.com/geotools/geotools/tree/main/licenses">licenses</a> for content we have collected from the internet. As an example the project includes the EPSG database so <a href="https://github.com/geotools/geotools/blob/main/licenses/EPSG.md">EPSG.md</a> is there as a data distribution license.</li></ul></div><div dir="ltr">While the authoritative place for distribution may be CRAN, the source code that generates the work is what would be reviewed when auditing a codebase. Having the license information alongside your code is consistent with the GPL-2 header "<i>You should have received a copy of the GNU General Public License along with this program</i>" snippet, and protects your ass-ets.</div><div dir="ltr"><br></div><div>Licenses are all about communicating intent, by choosing github as your forge it is best to follow their conventions for communicating license information to avoid confusion.</div><div dir="ltr"><br></div><div>Although we are focused on the source code (being an open source foundation), your distribution via CRAN (<a href="https://cran.r-project.org/web/packages/sf/index.html">https://cran.r-project.org/web/packages/sf/index.html</a>) is ... incomplete:</div><div><br></div><div>1) link to LICENSE: <a href="https://cran.r-project.org/web/packages/sf/LICENSE">https://cran.r-project.org/web/packages/sf/LICENSE</a> is just a copyright declaration</div><div><br></div><blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div><i>YEAR: 2016-2020</i></div><div><i>COPYRIGHT HOLDER: Edzer Pebesma</i></div></blockquote><div><br></div><div>2) link to GPL-2: <a href="https://cran.r-project.org/web/licenses/GPL-2">https://cran.r-project.org/web/licenses/GPL-2</a> seems okay<br></div><div>3) link to MIT: <a href="https://cran.r-project.org/web/licenses/MIT">https://cran.r-project.org/web/licenses/MIT</a> has not yet filled in the MIT license (just has the template):</div><div><br></div><div>Based on <a href="http://opensource.org/licenses/MIT">http://opensource.org/licenses/MIT</a><br><br></div><blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div><i>This is a template. Complete and ship as file LICENSE the following 2</i></div><div><i>lines (only)</i></div><div><i><br></i></div><div><i>YEAR:</i></div><div><i>COPYRIGHT HOLDER: </i></div><div><i><br></i></div><div><i>and specify as</i></div><div><i><br></i></div><div><i>License: MIT + file LICENSE</i></div><div><i><br></i></div><div><i>Copyright (c) <YEAR>, <COPYRIGHT HOLDER></i></div><div><i><br></i></div><div><i>Permission is hereby granted, free of charge, to any person obtaining</i></div><div><i>a copy of this software and associated documentation files (the</i></div><div><i>"Software"), to deal in the Software without restriction, including</i></div><div><i>without limitation the rights to use, copy, modify, merge, publish,</i></div><div><i>distribute, sublicense, and/or sell copies of the Software, and to</i></div><div><i>permit persons to whom the Software is furnished to do so, subject to</i></div><div><i>the following conditions:</i></div><div><i><br></i></div><div><i>The above copyright notice and this permission notice shall be</i></div><div><i>included in all copies or substantial portions of the Software.</i></div><div><i><br></i></div><div><i>THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,</i></div><div><i>EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF</i></div><div><i>MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND</i></div><div><i>NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE</i></div><div><i>LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION</i></div><div><i>OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION</i></div><div><i>WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.</i></div></blockquote><div>--<br></div><div dir="ltr"><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div dir="ltr"><div>Jody Garnett</div></div></div></div></div><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, 1 Jul 2021 at 13:35, Edzer Pebesma <<a href="mailto:edzer.pebesma@uni-muenster.de">edzer.pebesma@uni-muenster.de</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">Dear Jody, thanks for your efforts and positive response!<br>
<br>
I'll try to answer your questions:<br>
<br>
> Q: What is the project license for sf? Can you clearly indicate it in <br>
a LICENSE.md file? Or would that mess up your build?<br>
<br>
The licence is MIT or GPL-2; I guess that that effectively means MIT, <br>
but trying to express appreciation when others share modifications <br>
they'd redistribute.<br>
<br>
It wouldn't be a problem to add LICENSE.md, I didn't do that because the <br>
authoritative place for released versions is CRAN, which has a landing <br>
page for each CRAN package; the one for sf is: <br>
<a href="https://cran.r-project.org/web/packages/sf/index.html" rel="noreferrer" target="_blank">https://cran.r-project.org/web/packages/sf/index.html</a> where you can see <br>
that the licenses are listed with to their corresponding texts. If I <br>
would add a LICENSE.md, it duplicates and could be one more source for <br>
confusion. This is also the reason we don't do github tags or releases, <br>
as CRAN archives all releases; look for "Old sources", which in this <br>
case points to all CRAN releases of sf: <br>
<a href="https://cran.r-project.org/src/contrib/Archive/sf/" rel="noreferrer" target="_blank">https://cran.r-project.org/src/contrib/Archive/sf/</a><br>
<br>
For most R developers, github is a convenience, but CRAN is the place <br>
where we release, and where information is complete.<br>
<br>
<br>
> Q: What is your osgeo id? So you can be setup with website access to <br>
make a project page<br>
<br>
My osgeo ID is edzer<br>
<br>
Many regards,<br>
-- <br>
Edzer Pebesma<br>
Institute for Geoinformatics<br>
Heisenbergstrasse 2, 48151 Muenster, Germany<br>
Phone: +49 251 8333081<br>
<br>
<br>
<br>
Previous message:<br>
<br>
First up it is great to see such a strong R community, I have even seen<br>
presentations on the *sf* in my local university down "geogeeks" meetup<br>
(back when we could you know meet up).<br>
<br>
I was checking in to see if you had made any progress towards an osgeo<br>
project page, and I did not see anything yet...<br>
<br>
Checking your github repositories such as <a href="https://github.com/r-spatial/sf" rel="noreferrer" target="_blank">https://github.com/r-spatial/sf</a><br>
<br>
1 Be geospatial<br>
- README.md clearly spatial topic :)<br>
<br>
2. Have a free license or open source license<br>
- sf LICENSE <-- does not actually list an open source license (so you<br>
would trick github license detection)<br>
- mapview was clearly GPL<br>
- Searching the codebase shows<br>
<a href="https://github.com/r-spatial/sf/blob/master/DESCRIPTION#L50" rel="noreferrer" target="_blank">https://github.com/r-spatial/sf/blob/master/DESCRIPTION#L50</a> indicating some<br>
combination of MIT and GPL (what is your thought here?)<br>
<br>
3. Welcome participation and new contributors.<br>
- Well I have personally experienced your enthusiastic community, ... but<br>
this is a bit more focused on having a policy for things like pull requests.<br>
- Massive number of closed pull requests from a wide range of contributors<br>
- For sf I did not find a CONTRIBUTING.md file (shown to folks making a<br>
pull request) but the README has heading about contributing which is great<br>
<br>
So this looks okay, but I have questions:<br>
<br>
Q: What is the project license for sf? Can you clearly indicate it in a<br>
LICENSE.md file? Or would that mess up your build?<br>
Q: What is your osgeo id? So you can be setup with website access to make a<br>
project page<br>
<br>
<br>
<br>
<br>
<br>
<br>
--<br>
Jody Garnett<br>
<br>
<br>
On Mon, 22 Feb 2021 at 06:21, Robin Lovelace <rob00x at <a href="http://gmail.com" rel="noreferrer" target="_blank">gmail.com</a>> wrote:<br>
<br>
> We would like to apply, as the 'R-Spatial' community, to become an OSGeo<br>
> affiliated organisation.<br>
><br>
> We are a diverse group with a shared interest in developing free and open<br>
> tools for the reproducible analysis of geographic data. R is a <br>
popular and<br>
> rapidly growing language for statistical computing and 'data science'. It<br>
> is already part of the OSGeo ecosystem: the OSGeo Live distribution ships<br>
> with R <<a href="https://github.com/OSGeo/OSGeoLive/blob/master/bin/install_R.sh" rel="noreferrer" target="_blank">https://github.com/OSGeo/OSGeoLive/blob/master/bin/install_R.sh</a>><br>
> and R integrates with established OSGeo projects such as GRASS GIS<br>
> <<a href="https://grasswiki.osgeo.org/wiki/R_statistics" rel="noreferrer" target="_blank">https://grasswiki.osgeo.org/wiki/R_statistics</a>>, SAGA<br>
> <<a href="https://cran.r-project.org/package=RSAGA" rel="noreferrer" target="_blank">https://cran.r-project.org/package=RSAGA</a>> and QGIS<br>
> <<a href="https://docs.qgis.org/3.16/en/docs/" rel="noreferrer" target="_blank">https://docs.qgis.org/3.16/en/docs/</a>>. R tutorials (which would benefit<br>
> from being updated) are listed on the tutorials listed on OSGeo's old<br>
> website <<a href="http://old.www.osgeo.org/educational_content" rel="noreferrer" target="_blank">http://old.www.osgeo.org/educational_content</a>>. We would like to<br>
> update existing content and create new OSGeo-affiliated tutorials for <br>
using<br>
> R-Spatial software. Many R-Spatial projects have support from the R<br>
> Consortium <<a href="https://www.r-consortium.org/" rel="noreferrer" target="_blank">https://www.r-consortium.org/</a>>, opening the possibility of<br>
> stronger links between R and OSGeo at an organisational level.<br>
><br>
> After a discussion on our GitHub Organisation at <a href="http://github.com/r-spatial" rel="noreferrer" target="_blank">github.com/r-spatial</a>, it<br>
> is clear that closer links could be mutually beneficial. Collaboration is<br>
> at the heart of open source software and the R community has a long<br>
> history. The history of R-GRASS GIS bridges, for example, covers more <br>
than 20<br>
> years <<a href="https://doi.org/10.1016/S0098-3004(00)00057-1" rel="noreferrer" target="_blank">https://doi.org/10.1016/S0098-3004(00)00057-1</a>> and goes in both<br>
> directions. R interfaces enable a wide range of people to access<br>
> OSGeo-supported software from a reproducible command-line interface.<br>
><br>
> Continued development and innovation in R-OSGeo links are illustrated the<br>
> qgisprocess <<a href="https://github.com/paleolimbot/qgisprocess" rel="noreferrer" target="_blank">https://github.com/paleolimbot/qgisprocess</a>> package, which<br>
> motivated positive changes in the QGIS source code (see<br>
> <a href="http://github.com/paleolimbot/qgisprocess/issues/21" rel="noreferrer" target="_blank">github.com/paleolimbot/qgisprocess/issues/21</a>). The R-Spatial community<br>
> relies on the OSGeo projects GDAL, PROJ and GEOS for data access and<br>
> geographic operations. Core R-Spatial packages sf, raster and terra use<br>
> bindings to the libraries for much of the heavy lifting and many <br>
thousands<br>
> of people using R for spatial research (often without knowing) run OSGeo<br>
> support code every day. We would like to support the ongoing work of <br>
these<br>
> vital components of the wider community that is represented by the<br>
> OSGeo-affiliated conference series FOSS4G. We also anticipate <br>
benefits from<br>
> being part of the wider OSGeo community and would like to be more active<br>
> members of the wider movement advocating free and open source <br>
software for<br>
> geospatial.<br>
><br>
> 'R-Spatial' can be loosely defined as the ecosystem of code, projects and<br>
> people using R for working with and adding value to spatial data. A<br>
> manifestation of the wider R-Spatial community is the friendly, <br>
vibrant and<br>
> diverse range of voices using the #rspatial<br>
> <<a href="https://twitter.com/search?q=%23rspatial" rel="noreferrer" target="_blank">https://twitter.com/search?q=%23rspatial</a>> tag on Twitter. For the<br>
> purposes of OSGeo supported *software* projects however, we define<br>
> R-Spatial as the packages found at <a href="https://github.com/r-spatial/" rel="noreferrer" target="_blank">https://github.com/r-spatial/</a> (which<br>
> includes sf, stars, mapview, gstat, spdep and many other popular packages<br>
> for working with spatial data) and <a href="https://github.com/rspatial/" rel="noreferrer" target="_blank">https://github.com/rspatial/</a> (which<br>
> includes packages raster and terra). A (possibly incomplete) list with R<br>
> packages that directly link to OSGEO libraries is found here<br>
> <br>
<<a href="https://github.com/r-spatial/discuss/wiki/R-packages-that-use-the-OSGEO-stack-in-System-Requirements" rel="noreferrer" target="_blank">https://github.com/r-spatial/discuss/wiki/R-packages-that-use-the-OSGEO-stack-in-System-Requirements</a>:>.<br>
> Thousands of R packages depend on these packages one way or another.<br>
><br>
> We would like to initiate the process needed for R-Spatial to eventually<br>
> become an OSGeo community project, by achieving the first two of the <br>
three<br>
> steps as outlined on the Incubation Committee web page<br>
> <br>
<<a href="https://wiki.osgeo.org/wiki/Incubation_Committee#Step_1:_Add_OSGeo_Website_Project_Page" rel="noreferrer" target="_blank">https://wiki.osgeo.org/wiki/Incubation_Committee#Step_1:_Add_OSGeo_Website_Project_Page</a>><br>
> :<br>
><br>
> - We would like to create an OSGeo web page with information about key<br>
> packages in the 'R-spatial stack', including how they relate to OSGeo<br>
> projects<br>
> - We would like to become an OSGeo Community Project<br>
> <br>
<<a href="https://wiki.osgeo.org/wiki/Incubation_Committee#Step_2:_Join_Community_Projects_Program" rel="noreferrer" target="_blank">https://wiki.osgeo.org/wiki/Incubation_Committee#Step_2:_Join_Community_Projects_Program</a>><br>
><br>
> All the best,<br>
><br>
> R-Spatial developers and contributors, including: Robin Lovelace, Roger<br>
> Bivand, Edzer Pebesma, Tim Appelhans, Robert Hijmans, Jakub Nowosad, Nick<br>
> Bearman, Emmanuel Blondel, Andy Teucher, Marynia Kolak, Timothée Giraud,<br>
> Ahmadou Dicko, Andrea Gilardi, Lorena Abad, Martijn Tennekes<br>
> _______________________________________________<br>
> Incubator mailing list<br>
> Incubator at <a href="http://lists.osgeo.org" rel="noreferrer" target="_blank">lists.osgeo.org</a><br>
> <a href="https://lists.osgeo.org/mailman/listinfo/incubator" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/incubator</a><br>
><br>
_______________________________________________<br>
Incubator mailing list<br>
<a href="mailto:Incubator@lists.osgeo.org" target="_blank">Incubator@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/incubator" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/incubator</a><br>
</blockquote></div></div>