<div dir="ltr"><div>Hi Jody,</div><div><br></div><div>Thanks for the response and apologies for the slow response.</div><div><br></div><div>It's great to see there is appetite and that we mostly fit the criteria. Some of this discussion can happen in the FOSS4G panel here: <a href="https://callforpapers.2021.foss4g.org/foss4g2021/talk/VYRV77/">https://callforpapers.2021.foss4g.org/foss4g2021/talk/VYRV77/</a> <br></div><div><br></div><div>See below for detailed comments on the sf package from Edzer, I'm not sure if these were distributed to the list.</div><div><br></div><div>Can provide more detailed replies soon on the ecosystem of R-Spatial that is applying in the next month or so, any further follow-up questions in the meantime welcome.</div><div><br></div><div>Message from Edzer: <br></div><div><br></div><div><div id="gmail-divRplyFwdMsg" dir="ltr"><font style="font-size:11pt" face="Calibri, sans-serif" color="#000000"><b>From:</b> Edzer Pebesma <<a href="mailto:edzer.pebesma@uni-muenster.de">edzer.pebesma@uni-muenster.de</a>><br><b>Sent:</b> 01 July 2021 21:28<br><b>To:</b> <a href="mailto:incubator@lists.osgeo.org">incubator@lists.osgeo.org</a> <<a href="mailto:incubator@lists.osgeo.org">incubator@lists.osgeo.org</a>><br><b>Cc:</b> Robin Lovelace <<a href="mailto:R.Lovelace@leeds.ac.uk">R.Lovelace@leeds.ac.uk</a>>; <a href="mailto:Roger.Bivand@nhh.no">Roger.Bivand@nhh.no</a> <<a href="mailto:Roger.Bivand@nhh.no">Roger.Bivand@nhh.no</a>><br><b>Subject:</b> Re: [Incubator] Initiating the process for R-Spatial to become an OSGeo community project</font></div></div><div><br></div><div><font size="2"><span style="font-size:11pt">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" target="_blank" rel="noopener noreferrer">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/" target="_blank" rel="noopener noreferrer">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 <span class="gmail-mark34e7kkmif">edzer</span><br>
<br>
Many regards,<br>
-- <br>
<span class="gmail-mark34e7kkmif">Edzer</span> Pebesma<br>
Institute for Geoinformatics<br>
Heisenbergstrasse 2, 48151 Muenster, Germany<br>
Phone: +49 251 8333081<br>
</span></font></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, May 29, 2021 at 1:00 AM Jody Garnett <<a href="mailto:jody.garnett@gmail.com">jody.garnett@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div>First up it is great to see such a strong R community, I have even seen presentations on the <b>sf</b> in my local university down "geogeeks" meetup (back when we could you know meet up).</div><div><br></div>I was checking in to see if you had made any progress towards an osgeo project page, and I did not see anything yet...</div><div dir="ltr"><br></div><div dir="ltr"><div>Checking your github repositories such as <a href="https://github.com/r-spatial/sf" target="_blank">https://github.com/r-spatial/sf</a><br></div><div><br></div><div>1 Be geospatial<br></div><div>- README.md clearly spatial topic :)</div><div><br></div><div>2. Have a free license or open source license</div><div>- sf LICENSE <-- does not actually list an open source license (so you would trick github license detection)</div><div>- mapview was clearly GPL</div><div>- Searching the codebase shows <a href="https://github.com/r-spatial/sf/blob/master/DESCRIPTION#L50" target="_blank">https://github.com/r-spatial/sf/blob/master/DESCRIPTION#L50</a> indicating some combination of MIT and GPL (what is your thought here?)</div><div><br></div><div>3. Welcome participation and new contributors.</div><div>- Well I have personally experienced your enthusiastic community, ... but this is a bit more focused on having a policy for things like pull requests.</div><div>- Massive number of closed pull requests from a wide range of contributors</div><div>- For sf I did not find a CONTRIBUTING.md file (shown to folks making a pull request) but the README has heading about contributing which is great</div><div><br></div><div>So this looks okay, but I have questions:<br></div><div><br></div><div>Q: What is the project license for sf? Can you clearly indicate it in a LICENSE.md file? Or would that mess up your build?</div><div>Q: What is your osgeo id? So you can be setup with website access to make a project page</div><div><br></div><div><br><div><br></div><div><br><div><br></div><div><br clear="all"><div><div dir="ltr"><div dir="ltr"><div><div dir="ltr"><div>--</div><div>Jody Garnett</div></div></div></div></div></div><br></div></div></div></div></div></div></div></div></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, 22 Feb 2021 at 06:21, Robin Lovelace <<a href="mailto:rob00x@gmail.com" target="_blank">rob00x@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><p>We would like to apply, as the 'R-Spatial' community, to become an OSGeo affiliated organisation.</p>
<p>We are a diverse group with a shared interest in developing free and
open tools for the reproducible analysis of geographic data. R is a
popular and rapidly growing language for statistical computing and 'data
science'. It is already part of the OSGeo ecosystem: the OSGeo Live
distribution <a href="https://github.com/OSGeo/OSGeoLive/blob/master/bin/install_R.sh" target="_blank">ships with R</a> and R integrates with established OSGeo projects such as <a href="https://grasswiki.osgeo.org/wiki/R_statistics" rel="nofollow" target="_blank">GRASS GIS</a>, <a href="https://cran.r-project.org/package=RSAGA" rel="nofollow" target="_blank">SAGA</a> and <a href="https://docs.qgis.org/3.16/en/docs/" rel="nofollow" target="_blank">QGIS</a>. R tutorials (which would benefit from being updated) are listed on the tutorials listed on OSGeo's <a href="http://old.www.osgeo.org/educational_content" rel="nofollow" target="_blank">old website</a>. We would like to update existing content and create new OSGeo-affiliated tutorials for using R-Spatial software.
Many R-Spatial projects have support from the <a href="https://www.r-consortium.org/" rel="nofollow" target="_blank">R Consortium</a>, opening the possibility of stronger links between R and OSGeo at an organisational level.</p>
<p>After a discussion on our GitHub Organisation at <a href="https://github.com/r-spatial" target="_blank">github.com/r-spatial</a>,
it is clear that closer links could be mutually beneficial.
Collaboration is at the heart of open source software and the R
community has a long history. The history of R-GRASS GIS bridges, for
example, covers more than <a href="https://doi.org/10.1016/S0098-3004(00)00057-1" rel="nofollow" target="_blank">20 years</a>
and goes in both directions. R interfaces enable a wide range of people
to access OSGeo-supported software from a reproducible command-line
interface.</p>
<p>Continued development and innovation in R-OSGeo links are illustrated the <a href="https://github.com/paleolimbot/qgisprocess" target="_blank">qgisprocess</a> package, which motivated positive changes in the QGIS source code (see <a href="https://github.com/paleolimbot/qgisprocess/issues/21" target="_blank">github.com/paleolimbot/qgisprocess/issues/21</a>).
The R-Spatial community relies on the OSGeo projects GDAL, PROJ and
GEOS for data access and geographic operations. Core R-Spatial packages <code>sf</code>, <code>raster</code> and <code>terra</code>
use bindings to the libraries for much of the heavy lifting and many
thousands of people using R for spatial research (often without knowing)
run OSGeo support code every day. We would like to support the ongoing
work of these vital components of the wider community that is
represented by the OSGeo-affiliated conference series FOSS4G. We also
anticipate benefits from being part of the wider OSGeo community and
would like to be more active members of the wider movement advocating
free and open source software for geospatial.</p>
<p>'R-Spatial' can be loosely defined as the ecosystem of code, projects
and people using R for working with and adding value to spatial data. A
manifestation of the wider R-Spatial community is the friendly, vibrant
and diverse range of voices using the <a href="https://twitter.com/search?q=%23rspatial" rel="nofollow" target="_blank">#rspatial</a> tag on Twitter. For the purposes of OSGeo supported <em>software</em> projects however, we define R-Spatial as the packages found at <a href="https://github.com/r-spatial/" target="_blank">https://github.com/r-spatial/</a> (which includes <code>sf</code>, <code>stars</code>, <code>mapview</code>, <code>gstat</code>, <code>spdep</code> and many other popular packages for working with spatial data) and <a href="https://github.com/rspatial/" target="_blank">https://github.com/rspatial/</a> (which includes packages <code>raster</code> and <code>terra</code>). A (possibly incomplete) list with R packages that directly link to OSGEO libraries is found <a href="https://github.com/r-spatial/discuss/wiki/R-packages-that-use-the-OSGEO-stack-in-System-Requirements:" target="_blank">here</a>. Thousands of R packages depend on these packages one way or another.</p>
<p>We would like to initiate the process needed for R-Spatial to
eventually become an OSGeo community project, by achieving the first two
of the three steps as outlined on the <a href="https://wiki.osgeo.org/wiki/Incubation_Committee#Step_1:_Add_OSGeo_Website_Project_Page" rel="nofollow" target="_blank">Incubation Committee web page</a>:</p>
<ul><li>We would like to create an OSGeo web page with information about key
packages in the 'R-spatial stack', including how they relate to OSGeo
projects</li><li>We would like to become an <a href="https://wiki.osgeo.org/wiki/Incubation_Committee#Step_2:_Join_Community_Projects_Program" rel="nofollow" target="_blank">OSGeo Community Project</a></li></ul>
<p>All the best,</p>
<p>R-Spatial developers and contributors, including:
Robin Lovelace,
Roger Bivand,
Edzer Pebesma,
Tim Appelhans,
Robert Hijmans,
Jakub Nowosad,
Nick Bearman,
Emmanuel Blondel,
Andy Teucher,
Marynia Kolak,
Timothée Giraud,
Ahmadou Dicko,
Andrea Gilardi,
Lorena Abad,
Martijn Tennekes</p></div>
_______________________________________________<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>
</blockquote></div>