<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Forwarding to list<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">Begin forwarded message:</div><br class="Apple-interchange-newline"><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class=""><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);" class=""><b class="">From: </b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class="">Bruce Bannerman <<a href="mailto:bruce.bannerman.osgeo@gmail.com" class="">bruce.bannerman.osgeo@gmail.com</a>><br class=""></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class=""><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);" class=""><b class="">Subject: </b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class=""><b class="">Re: [Incubator] MOSS: OSGeo Heritage Project</b><br class=""></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class=""><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);" class=""><b class="">Date: </b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class="">20 August 2021 at 08:23:56 AEST<br class=""></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class=""><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);" class=""><b class="">To: </b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class="">Peter Löwe <<a href="mailto:peter.loewe@gmx.de" class="">peter.loewe@gmx.de</a>><br class=""></span></div><br class=""><div class=""><div class="">Hello Peter,<br class=""><br class="">What is your motivation for wanting to take MOSS through an incubation process?<br class=""><br class="">It can be a lot of work for the community and the mentor.<br class=""><br class="">Are you planning to resurrect MOSS into an active project?<br class=""><br class="">If not, based on the information to hand, I don’t see the benefit. <br class=""><br class="">Kind regards,<br class=""><br class="">Bruce<br class=""><br class=""><br class=""><blockquote type="cite" class="">On 20 Aug 2021, at 06:25, Peter Löwe <<a href="mailto:peter.loewe@gmx.de" class="">peter.loewe@gmx.de</a>> wrote:<br class=""><br class="">Hi incubation list, (cc: MOSS archives list)<br class=""><br class="">the incubation effort for the MOSS project has made significant progress in the last months.<br class=""><br class="">Since a tight timeline was laid out for the recognition of R Geospatial as an OSGeo community project in time for FOSS4G 2021, I would like to ask the incubation committee to consider and assess wether the incubation for MOSS as the first OSGeo heritage project could also be completed in time for FOSS4G 2021 (to be announced at this years Sol Katz award).<br class=""><br class="">This wiki page summarizes the OSGeo incubation requirements met by the MOSS heritage project, including links to documents of interest in the MOSS codebase, hosted at OSGeo@GitHub:<br class=""><a href="https://wiki.osgeo.org/wiki/MOSS_incubation_overview" class="">https://wiki.osgeo.org/wiki/MOSS_incubation_overview</a><br class=""><br class="">The current OSGeo requirements for project incubation are extended and augmented by the MOSS project with best Open Science practices for open access publication, long term preservation and due credit by scientific citation for initial authors, coders and code maintainers. It would be awesome if OSGeo Incubation would embrace and foster these Open Science concepts.<br class=""><br class="">Best,<br class="">Peter<br class=""><br class=""><peter.loewe@gmx.de><br class=""><br class=""><br class=""><blockquote type="cite" class="">Gesendet: Donnerstag, 19. August 2021 um 17:53 Uhr<br class="">Von: incubator-request@lists.osgeo.org<br class="">An: incubator@lists.osgeo.org<br class="">Betreff: Incubator Digest, Vol 169, Issue 5<br class=""><br class="">Send Incubator mailing list submissions to<br class=""> incubator@lists.osgeo.org<br class=""><br class="">To subscribe or unsubscribe via the World Wide Web, visit<br class=""> https://lists.osgeo.org/mailman/listinfo/incubator<br class="">or, via email, send a message with subject or body 'help' to<br class=""> incubator-request@lists.osgeo.org<br class=""><br class="">You can reach the person managing the list at<br class=""> incubator-owner@lists.osgeo.org<br class=""><br class="">When replying, please edit your Subject line so it is more specific<br class="">than "Re: Contents of Incubator digest..."<br class=""><br class=""><br class="">Today's Topics:<br class=""><br class=""> 1. Re: Initiating the process for R-Spatial to become an OSGeo<br class=""> community project (Jody Garnett)<br class=""><br class=""><br class="">----------------------------------------------------------------------<br class=""><br class="">Message: 1<br class="">Date: Thu, 19 Aug 2021 08:52:50 -0700<br class="">From: Jody Garnett <jody.garnett@gmail.com><br class="">To: Edzer Pebesma <edzer.pebesma@uni-muenster.de><br class="">Cc: OSGeo-incubator <incubator@lists.osgeo.org>, Robin Lovelace<br class=""> <r.lovelace@leeds.ac.uk>, "Roger.Bivand@nhh.no" <Roger.Bivand@nhh.no><br class="">Subject: Re: [Incubator] Initiating the process for R-Spatial to<br class=""> become an OSGeo community project<br class="">Message-ID:<br class=""> <CAOhbgAnAYXoqWN8+_MTYo-+gkAH107YzDpH9Guj8h3SAxmVtmA@mail.gmail.com><br class="">Content-Type: text/plain; charset="utf-8"<br class=""><br class="">I was more thinking if you can get a move on you could make the deadline<br class="">for the conference....<br class=""><br class="">Let's look at the timeline:<br class=""><br class="">1. If you do the work today ...<br class="">2. We make a motion Friday August 20th<br class="">3. The motion would close Friday September 3rd<br class="">4. I would recommend the project be accepted into osgeo for the board<br class="">meeting at the last monday of the of the month .. Monday September 27th<br class="">5. Then joining OSGeo could be announced during the conference...<br class=""><br class="">Does that make sense from a planning perspective?<br class="">--<br class="">Jody Garnett<br class=""><br class=""><br class=""><blockquote type="cite" class="">On Tue, 17 Aug 2021 at 03:16, Edzer Pebesma <edzer.pebesma@uni-muenster.de><br class="">wrote:<br class=""><br class="">Hi Jody thanks for getting back; participation is planned:<br class=""><br class="">https://callforpapers.2021.foss4g.org/foss4g2021/talk/VYRV77/<br class=""><br class="">On 17/08/2021 00:35, Jody Garnett wrote:<br class=""><blockquote type="cite" class="">Wanted to check back in Edzer, we have our foss4g conference coming up<br class="">and it would be great to see R part of the party.<br class="">--<br class="">Jody Garnett<br class=""><br class=""><br class="">On Thu, 8 Jul 2021 at 14:57, Jody Garnett <jody.garnett@gmail.com<br class=""><mailto:jody.garnett@gmail.com>> wrote:<br class=""><br class=""> Edzer:<br class=""><br class=""> I have setup "edzer" with "project author" permissions to create a<br class=""> project on the osgeo website, when you have something ready (or need<br class=""> any assistance figuring out wordpress) let us know. The page for<br class=""> service providers<br class=""> <<br class=""></blockquote>https://www.osgeo.org/community/getting-started-osgeo/add-service-provider/<br class=""><blockquote type="cite" class=""><br class=""> is a good example of how everything is broken into tabs.<br class=""><br class=""> Having a dual license (MIT and GPL-2) is just fine and can really be<br class=""> used to reflect your participants values etc.... Indeed a dual<br class=""> license approaches can be very valuable as each encourages a<br class=""> different balance of responsibility and assurances.<br class=""><br class=""> Examples for your team:<br class=""><br class=""> * The JTS project has a dual license (LICENSE.md<br class=""> <https://github.com/locationtech/jts/blob/master/LICENSES.md>)<br class=""> of BSD (permissive license promoting wide adoption) and Eclipse<br class=""> License (promoting some projection against patents and so<br class=""> forth). This is a good example of how to do a dual license.<br class=""> * When you have a dual license approach some care is needed in<br class=""> accepting contributions from others: As an example we have run<br class=""> into the GeoServer project which as GPL (with a small exception<br class=""> allowing some eclipse license code). Normally we collect a CLA<br class=""> for all contributions (so we have the ability to donate code to<br class=""> other projects like GeoTools and JTS). Recently some folks<br class=""> collected some code that was abandoned and the original authors<br class=""> were no longer available to sign a CLA. The result is our<br class=""> codebase now has some extensions with LICENSE.md files in<br class=""> specific directories.<br class=""> * It can also be a challenge to communicate what is going on when<br class=""> working with a codebase that has collected influence from<br class=""> different sources. I just updated the GeoTools codebase with<br class=""> its core LGPL LICENSE.md<br class=""> <https://github.com/geotools/geotools/blob/main/LICENSE.md>,<br class=""> followed by a clear notice<br class=""> <<br class=""></blockquote>https://github.com/geotools/geotools/blob/main/licenses/README.md<br class=""><blockquote type="cite" class="">describing<br class=""> listing all the individual licenses<br class=""> <https://github.com/geotools/geotools/tree/main/licenses> for<br class=""> content we have collected from the internet. As an example the<br class=""> project includes the EPSG database so EPSG.md<br class=""> <https://github.com/geotools/geotools/blob/main/licenses/EPSG.md<br class="">is<br class=""> there as a data distribution license.<br class=""><br class=""> While the authoritative place for distribution may be CRAN, the<br class=""> source code that generates the work is what would be reviewed when<br class=""> auditing a codebase. Having the license information alongside your<br class=""> code is consistent with the GPL-2 header "/You should have received<br class=""> a copy of the GNU General Public License along with this program/"<br class=""> snippet, and protects your ass-ets.<br class=""><br class=""> Licenses are all about communicating intent, by choosing github as<br class=""> your forge it is best to follow their conventions for communicating<br class=""> license information to avoid confusion.<br class=""><br class=""> Although we are focused on the source code (being an open source<br class=""> foundation), your distribution via CRAN<br class=""> (https://cran.r-project.org/web/packages/sf/index.html<br class=""> <https://cran.r-project.org/web/packages/sf/index.html>) is ...<br class=""> incomplete:<br class=""><br class=""> 1) link to LICENSE:<br class=""> https://cran.r-project.org/web/packages/sf/LICENSE<br class=""> <https://cran.r-project.org/web/packages/sf/LICENSE> is just a<br class=""> copyright declaration<br class=""><br class=""> /YEAR: 2016-2020/<br class=""> /COPYRIGHT HOLDER: Edzer Pebesma/<br class=""><br class=""><br class=""> 2) link to GPL-2: https://cran.r-project.org/web/licenses/GPL-2<br class=""> <https://cran.r-project.org/web/licenses/GPL-2> seems okay<br class=""> 3) link to MIT: https://cran.r-project.org/web/licenses/MIT<br class=""> <https://cran.r-project.org/web/licenses/MIT> has not yet filled in<br class=""> the MIT license (just has the template):<br class=""><br class=""> Based on http://opensource.org/licenses/MIT<br class=""> <http://opensource.org/licenses/MIT><br class=""><br class=""> /This is a template. Complete and ship as file LICENSE the<br class=""> following 2/<br class=""> /lines (only)/<br class=""> /<br class=""> /<br class=""> /YEAR:/<br class=""> /COPYRIGHT HOLDER: /<br class=""> /<br class=""> /<br class=""> /and specify as/<br class=""> /<br class=""> /<br class=""> /License: MIT + file LICENSE/<br class=""> /<br class=""> /<br class=""> /Copyright (c) <YEAR>, <COPYRIGHT HOLDER>/<br class=""> /<br class=""> /<br class=""> /Permission is hereby granted, free of charge, to any person<br class=""> obtaining/<br class=""> /a copy of this software and associated documentation files (the/<br class=""> /"Software"), to deal in the Software without restriction,<br class=""> including/<br class=""> /without limitation the rights to use, copy, modify, merge,<br class=""> publish,/<br class=""> /distribute, sublicense, and/or sell copies of the Software, and<br class=""></blockquote>to/<br class=""><blockquote type="cite" class=""> /permit persons to whom the Software is furnished to do so,<br class=""> subject to/<br class=""> /the following conditions:/<br class=""> /<br class=""> /<br class=""> /The above copyright notice and this permission notice shall be/<br class=""> /included in all copies or substantial portions of the Software./<br class=""> /<br class=""> /<br class=""> /THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,/<br class=""> /EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES<br class=""></blockquote>OF/<br class=""><blockquote type="cite" class=""> /MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND/<br class=""> /NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT<br class=""> HOLDERS BE/<br class=""> /LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN<br class=""> ACTION/<br class=""> /OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN<br class=""> CONNECTION/<br class=""> /WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE./<br class=""><br class=""> --<br class=""> Jody Garnett<br class=""><br class=""><br class=""> On Thu, 1 Jul 2021 at 13:35, Edzer Pebesma<br class=""> <edzer.pebesma@uni-muenster.de<br class=""> <mailto:edzer.pebesma@uni-muenster.de>> wrote:<br class=""><br class=""> Dear Jody, thanks for your efforts and positive response!<br class=""><br class=""> I'll try to answer your questions:<br class=""><br class=""><blockquote type="cite" class="">Q: What is the project license for sf? Can you clearly<br class=""></blockquote> indicate it in<br class=""> a LICENSE.md file? Or would that mess up your build?<br class=""><br class=""> The licence is MIT or GPL-2; I guess that that effectively means<br class=""> MIT,<br class=""> but trying to express appreciation when others share<br class=""></blockquote>modifications<br class=""><blockquote type="cite" class=""> they'd redistribute.<br class=""><br class=""> It wouldn't be a problem to add LICENSE.md, I didn't do that<br class=""> because the<br class=""> authoritative place for released versions is CRAN, which has a<br class=""> landing<br class=""> page for each CRAN package; the one for sf is:<br class=""> https://cran.r-project.org/web/packages/sf/index.html<br class=""> <https://cran.r-project.org/web/packages/sf/index.html> where<br class=""> you can see<br class=""> that the licenses are listed with to their corresponding texts.<br class=""> If I<br class=""> would add a LICENSE.md, it duplicates and could be one more<br class=""> source for<br class=""> confusion. This is also the reason we don't do github tags or<br class=""> releases,<br class=""> as CRAN archives all releases; look for "Old sources", which in<br class=""> this<br class=""> case points to all CRAN releases of sf:<br class=""> https://cran.r-project.org/src/contrib/Archive/sf/<br class=""> <https://cran.r-project.org/src/contrib/Archive/sf/><br class=""><br class=""> For most R developers, github is a convenience, but CRAN is the<br class=""> place<br class=""> where we release, and where information is complete.<br class=""><br class=""><br class=""><blockquote type="cite" class="">Q: What is your osgeo id? So you can be setup with website<br class=""></blockquote> access to<br class=""> make a project page<br class=""><br class=""> My osgeo ID is edzer<br class=""><br class=""> Many regards,<br class=""> --<br class=""> Edzer Pebesma<br class=""> Institute for Geoinformatics<br class=""> Heisenbergstrasse 2, 48151 Muenster, Germany<br class=""> Phone: +49 251 8333081<br class=""><br class=""><br class=""><br class=""> Previous message:<br class=""><br class=""> First up it is great to see such a strong R community, I have<br class=""> even seen<br class=""> presentations on the *sf* in my local university down "geogeeks"<br class=""> meetup<br class=""> (back when we could you know meet up).<br class=""><br class=""> I was checking in to see if you had made any progress towards an<br class=""> osgeo<br class=""> project page, and I did not see anything yet...<br class=""><br class=""> Checking your github repositories such as<br class=""> https://github.com/r-spatial/sf <https://github.com/r-spatial/sf<br class=""><br class=""><br class=""> 1 Be geospatial<br class=""> - README.md clearly spatial topic :)<br class=""><br class=""> 2. Have a free license or open source license<br class=""> - sf LICENSE <-- does not actually list an open source license<br class=""> (so you<br class=""> would trick github license detection)<br class=""> - mapview was clearly GPL<br class=""> - Searching the codebase shows<br class=""> https://github.com/r-spatial/sf/blob/master/DESCRIPTION#L50<br class=""> <https://github.com/r-spatial/sf/blob/master/DESCRIPTION#L50><br class=""> indicating some<br class=""> combination of MIT and GPL (what is your thought here?)<br class=""><br class=""> 3. Welcome participation and new contributors.<br class=""> - Well I have personally experienced your enthusiastic<br class=""> community, ... but<br class=""> this is a bit more focused on having a policy for things like<br class=""> pull requests.<br class=""> - Massive number of closed pull requests from a wide range of<br class=""> contributors<br class=""> - For sf I did not find a CONTRIBUTING.md file (shown to folks<br class=""> making a<br class=""> pull request) but the README has heading about contributing<br class=""> which is great<br class=""><br class=""> So this looks okay, but I have questions:<br class=""><br class=""> Q: What is the project license for sf? Can you clearly indicate<br class=""> it in a<br class=""> LICENSE.md file? Or would that mess up your build?<br class=""> Q: What is your osgeo id? So you can be setup with website<br class=""> access to make a<br class=""> project page<br class=""><br class=""><br class=""><br class=""><br class=""><br class=""><br class=""> --<br class=""> Jody Garnett<br class=""><br class=""><br class=""> On Mon, 22 Feb 2021 at 06:21, Robin Lovelace <rob00x at<br class=""> gmail.com <http://gmail.com>> wrote:<br class=""><br class=""><blockquote type="cite" class="">We would like to apply, as the 'R-Spatial' community, to<br class=""></blockquote> become an OSGeo<br class=""><blockquote type="cite" class="">affiliated organisation.<br class=""><br class="">We are a diverse group with a shared interest in developing<br class=""></blockquote> free and open<br class=""><blockquote type="cite" class="">tools for the reproducible analysis of geographic data. R is<br class=""></blockquote></blockquote>a<br class=""><blockquote type="cite" class=""> popular and<br class=""><blockquote type="cite" class="">rapidly growing language for statistical computing and 'data<br class=""></blockquote> science'. It<br class=""><blockquote type="cite" class="">is already part of the OSGeo ecosystem: the OSGeo Live<br class=""></blockquote> distribution ships<br class=""><blockquote type="cite" class="">with R<br class=""></blockquote> <https://github.com/OSGeo/OSGeoLive/blob/master/bin/install_R.sh<br class=""> <https://github.com/OSGeo/OSGeoLive/blob/master/bin/install_R.sh<br class=""><blockquote type="cite" class=""><br class="">and R integrates with established OSGeo projects such as<br class=""></blockquote> GRASS GIS<br class=""><blockquote type="cite" class=""><https://grasswiki.osgeo.org/wiki/R_statistics<br class=""></blockquote> <https://grasswiki.osgeo.org/wiki/R_statistics>>, SAGA<br class=""><blockquote type="cite" class=""><https://cran.r-project.org/package=RSAGA<br class=""></blockquote> <https://cran.r-project.org/package=RSAGA>> and QGIS<br class=""><blockquote type="cite" class=""><https://docs.qgis.org/3.16/en/docs/<br class=""></blockquote> <https://docs.qgis.org/3.16/en/docs/>>. R tutorials (which would<br class=""> benefit<br class=""><blockquote type="cite" class="">from being updated) are listed on the tutorials listed on<br class=""></blockquote> OSGeo's old<br class=""><blockquote type="cite" class="">website <http://old.www.osgeo.org/educational_content<br class=""></blockquote> <http://old.www.osgeo.org/educational_content>>. We would like<br class=""></blockquote>to<br class=""><blockquote type="cite" class=""><blockquote type="cite" class="">update existing content and create new OSGeo-affiliated<br class=""></blockquote> tutorials for<br class=""> using<br class=""><blockquote type="cite" class="">R-Spatial software. Many R-Spatial projects have support<br class=""></blockquote> from the R<br class=""><blockquote type="cite" class="">Consortium <https://www.r-consortium.org/<br class=""></blockquote> <https://www.r-consortium.org/>>, opening the possibility of<br class=""><blockquote type="cite" class="">stronger links between R and OSGeo at an organisational<br class=""></blockquote></blockquote>level.<br class=""><blockquote type="cite" class=""><blockquote type="cite" class=""><br class="">After a discussion on our GitHub Organisation at<br class=""></blockquote> github.com/r-spatial <http://github.com/r-spatial>, it<br class=""><blockquote type="cite" class="">is clear that closer links could be mutually beneficial.<br class=""></blockquote> Collaboration is<br class=""><blockquote type="cite" class="">at the heart of open source software and the R community has<br class=""></blockquote> a long<br class=""><blockquote type="cite" class="">history. The history of R-GRASS GIS bridges, for example,<br class=""></blockquote> covers more<br class=""> than 20<br class=""><blockquote type="cite" class="">years <https://doi.org/10.1016/S0098-3004(00)00057-1<br class=""></blockquote> <https://doi.org/10.1016/S0098-3004(00)00057-1>> and goes in<br class=""></blockquote>both<br class=""><blockquote type="cite" class=""><blockquote type="cite" class="">directions. R interfaces enable a wide range of people to<br class=""></blockquote></blockquote>access<br class=""><blockquote type="cite" class=""><blockquote type="cite" class="">OSGeo-supported software from a reproducible command-line<br class=""></blockquote> interface.<br class=""><blockquote type="cite" class=""><br class="">Continued development and innovation in R-OSGeo links are<br class=""></blockquote> illustrated the<br class=""><blockquote type="cite" class="">qgisprocess <https://github.com/paleolimbot/qgisprocess<br class=""></blockquote> <https://github.com/paleolimbot/qgisprocess>> package, which<br class=""><blockquote type="cite" class="">motivated positive changes in the QGIS source code (see<br class="">github.com/paleolimbot/qgisprocess/issues/21<br class=""></blockquote> <http://github.com/paleolimbot/qgisprocess/issues/21>). The<br class=""> R-Spatial community<br class=""><blockquote type="cite" class="">relies on the OSGeo projects GDAL, PROJ and GEOS for data<br class=""></blockquote> access and<br class=""><blockquote type="cite" class="">geographic operations. Core R-Spatial packages sf, raster<br class=""></blockquote> and terra use<br class=""><blockquote type="cite" class="">bindings to the libraries for much of the heavy lifting and<br class=""></blockquote> many<br class=""> thousands<br class=""><blockquote type="cite" class="">of people using R for spatial research (often without<br class=""></blockquote> knowing) run OSGeo<br class=""><blockquote type="cite" class="">support code every day. We would like to support the ongoing<br class=""></blockquote> work of<br class=""> these<br class=""><blockquote type="cite" class="">vital components of the wider community that is represented<br class=""></blockquote> by the<br class=""><blockquote type="cite" class="">OSGeo-affiliated conference series FOSS4G. We also anticipate<br class=""></blockquote> benefits from<br class=""><blockquote type="cite" class="">being part of the wider OSGeo community and would like to be<br class=""></blockquote> more active<br class=""><blockquote type="cite" class="">members of the wider movement advocating free and open source<br class=""></blockquote> software for<br class=""><blockquote type="cite" class="">geospatial.<br class=""><br class="">'R-Spatial' can be loosely defined as the ecosystem of code,<br class=""></blockquote> projects and<br class=""><blockquote type="cite" class="">people using R for working with and adding value to spatial<br class=""></blockquote> data. A<br class=""><blockquote type="cite" class="">manifestation of the wider R-Spatial community is the<br class=""></blockquote></blockquote>friendly,<br class=""><blockquote type="cite" class=""> vibrant and<br class=""><blockquote type="cite" class="">diverse range of voices using the #rspatial<br class=""><https://twitter.com/search?q=%23rspatial<br class=""></blockquote> <https://twitter.com/search?q=%23rspatial>> tag on Twitter. For<br class=""></blockquote>the<br class=""><blockquote type="cite" class=""><blockquote type="cite" class="">purposes of OSGeo supported *software* projects however, we<br class=""></blockquote> define<br class=""><blockquote type="cite" class="">R-Spatial as the packages found at<br class=""></blockquote> https://github.com/r-spatial/ <https://github.com/r-spatial/><br class=""></blockquote>(which<br class=""><blockquote type="cite" class=""><blockquote type="cite" class="">includes sf, stars, mapview, gstat, spdep and many other<br class=""></blockquote> popular packages<br class=""><blockquote type="cite" class="">for working with spatial data) and<br class=""></blockquote> https://github.com/rspatial/ <https://github.com/rspatial/><br class=""></blockquote>(which<br class=""><blockquote type="cite" class=""><blockquote type="cite" class="">includes packages raster and terra). A (possibly incomplete)<br class=""></blockquote> list with R<br class=""><blockquote type="cite" class="">packages that directly link to OSGEO libraries is found here<br class=""><br class=""></blockquote> <<br class=""></blockquote>https://github.com/r-spatial/discuss/wiki/R-packages-that-use-the-OSGEO-stack-in-System-Requirements<br class=""><blockquote type="cite" class=""> <<br class=""></blockquote>https://github.com/r-spatial/discuss/wiki/R-packages-that-use-the-OSGEO-stack-in-System-Requirements<br class=""><blockquote type="cite" class="">:>.<br class=""><blockquote type="cite" class="">Thousands of R packages depend on these packages one way or<br class=""></blockquote> another.<br class=""><blockquote type="cite" class=""><br class="">We would like to initiate the process needed for R-Spatial<br class=""></blockquote> to eventually<br class=""><blockquote type="cite" class="">become an OSGeo community project, by achieving the first<br class=""></blockquote> two of the<br class=""> three<br class=""><blockquote type="cite" class="">steps as outlined on the Incubation Committee web page<br class=""><br class=""></blockquote> <<br class=""></blockquote>https://wiki.osgeo.org/wiki/Incubation_Committee#Step_1:_Add_OSGeo_Website_Project_Page<br class=""><blockquote type="cite" class=""> <<br class=""></blockquote>https://wiki.osgeo.org/wiki/Incubation_Committee#Step_1:_Add_OSGeo_Website_Project_Page<br class=""><blockquote type="cite" class=""><blockquote type="cite" class=""><br class="">:<br class=""><br class=""> - We would like to create an OSGeo web page with<br class=""></blockquote> information about key<br class=""><blockquote type="cite" class=""> packages in the 'R-spatial stack', including how they<br class=""></blockquote> relate to OSGeo<br class=""><blockquote type="cite" class=""> projects<br class=""> - We would like to become an OSGeo Community Project<br class=""><br class=""></blockquote> <<br class=""></blockquote>https://wiki.osgeo.org/wiki/Incubation_Committee#Step_2:_Join_Community_Projects_Program<br class=""><blockquote type="cite" class=""> <<br class=""></blockquote>https://wiki.osgeo.org/wiki/Incubation_Committee#Step_2:_Join_Community_Projects_Program<br class=""><blockquote type="cite" class=""><blockquote type="cite" class=""><br class=""><br class="">All the best,<br class=""><br class="">R-Spatial developers and contributors, including: Robin<br class=""></blockquote> Lovelace, Roger<br class=""><blockquote type="cite" class="">Bivand, Edzer Pebesma, Tim Appelhans, Robert Hijmans, Jakub<br class=""></blockquote> Nowosad, Nick<br class=""><blockquote type="cite" class="">Bearman, Emmanuel Blondel, Andy Teucher, Marynia Kolak,<br class=""></blockquote> Timoth?e Giraud,<br class=""><blockquote type="cite" class="">Ahmadou Dicko, Andrea Gilardi, Lorena Abad, Martijn Tennekes<br class="">_______________________________________________<br class="">Incubator mailing list<br class="">Incubator at lists.osgeo.org <http://lists.osgeo.org><br class="">https://lists.osgeo.org/mailman/listinfo/incubator<br class=""></blockquote> <https://lists.osgeo.org/mailman/listinfo/incubator><br class=""><blockquote type="cite" class=""><br class=""></blockquote> _______________________________________________<br class=""> Incubator mailing list<br class=""> Incubator@lists.osgeo.org <mailto:Incubator@lists.osgeo.org><br class=""> https://lists.osgeo.org/mailman/listinfo/incubator<br class=""> <https://lists.osgeo.org/mailman/listinfo/incubator><br class=""><br class=""></blockquote><br class="">--<br class="">Edzer Pebesma<br class="">Institute for Geoinformatics<br class="">Heisenbergstrasse 2, 48151 Muenster, Germany<br class="">Phone: +49 251 8333081<br class=""><br class=""></blockquote>-------------- next part --------------<br class="">An HTML attachment was scrubbed...<br class="">URL: <http://lists.osgeo.org/pipermail/incubator/attachments/20210819/e049c7d7/attachment.html><br class=""><br class="">------------------------------<br class=""><br class="">Subject: Digest Footer<br class=""><br class="">_______________________________________________<br class="">Incubator mailing list<br class="">Incubator@lists.osgeo.org<br class="">https://lists.osgeo.org/mailman/listinfo/incubator<br class=""><br class=""><br class="">------------------------------<br class=""><br class="">End of Incubator Digest, Vol 169, Issue 5<br class="">*****************************************<br class=""><br class=""></blockquote>_______________________________________________<br class="">Incubator mailing list<br class="">Incubator@lists.osgeo.org<br class="">https://lists.osgeo.org/mailman/listinfo/incubator<br class=""></blockquote></div></div></blockquote></div><br class=""></body></html>