<div dir="ltr">I was more thinking if you can get a move on you could make the deadline for the conference.... <div><br></div><div>Let's look at the timeline:<br><div><br></div><div>1. If you do the work today ...</div><div>2. We make a motion Friday August 20th</div><div>3. The motion would close Friday September 3rd</div><div>4. I would recommend the project be accepted into osgeo for the board meeting at the last monday of the of the month .. Monday September 27th</div><div>5. Then joining OSGeo could be announced during the conference... </div><div><br></div><div>Does that make sense from a planning perspective?<br clear="all"><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div>--</div><div>Jody Garnett</div></div></div></div></div></div><br></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, 17 Aug 2021 at 03:16, 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">Hi Jody thanks for getting back; participation is planned:<br>
<br>
<a href="https://callforpapers.2021.foss4g.org/foss4g2021/talk/VYRV77/" rel="noreferrer" target="_blank">https://callforpapers.2021.foss4g.org/foss4g2021/talk/VYRV77/</a><br>
<br>
On 17/08/2021 00:35, Jody Garnett wrote:<br>
> Wanted to check back in Edzer, we have our foss4g conference coming up <br>
> and it would be great to see R part of the party.<br>
> --<br>
> Jody Garnett<br>
> <br>
> <br>
> On Thu, 8 Jul 2021 at 14:57, Jody Garnett <<a href="mailto:jody.garnett@gmail.com" target="_blank">jody.garnett@gmail.com</a> <br>
> <mailto:<a href="mailto:jody.garnett@gmail.com" target="_blank">jody.garnett@gmail.com</a>>> wrote:<br>
> <br>
> Edzer:<br>
> <br>
> I have setup "edzer" with "project author" permissions to create a<br>
> project on the osgeo website, when you have something ready (or need<br>
> any assistance figuring out wordpress) let us know. The page for<br>
> service providers<br>
> <<a href="https://www.osgeo.org/community/getting-started-osgeo/add-service-provider/" rel="noreferrer" target="_blank">https://www.osgeo.org/community/getting-started-osgeo/add-service-provider/</a>><br>
> is a good example of how everything is broken into tabs.<br>
> <br>
> Having a dual license (MIT and GPL-2) is just fine and can really be<br>
> used to reflect your participants values etc.... Indeed a dual<br>
> license approaches can be very valuable as each encourages a<br>
> different balance of responsibility and assurances.<br>
> <br>
> Examples for your team:<br>
> <br>
> * The JTS project has a dual license (LICENSE.md<br>
> <<a href="https://github.com/locationtech/jts/blob/master/LICENSES.md" rel="noreferrer" target="_blank">https://github.com/locationtech/jts/blob/master/LICENSES.md</a>>)<br>
> of BSD (permissive license promoting wide adoption) and Eclipse<br>
> License (promoting some projection against patents and so<br>
> forth). This is a good example of how to do a dual license.<br>
> * When you have a dual license approach some care is needed in<br>
> accepting contributions from others: As an example we have run<br>
> into the GeoServer project which as GPL (with a small exception<br>
> allowing some eclipse license code). Normally we collect a CLA<br>
> for all contributions (so we have the ability to donate code to<br>
> other projects like GeoTools and JTS). Recently some folks<br>
> collected some code that was abandoned and the original authors<br>
> were no longer available to sign a CLA. The result is our<br>
> codebase now has some extensions with LICENSE.md files in<br>
> specific directories.<br>
> * It can also be a challenge to communicate what is going on when<br>
> working with a codebase that has collected influence from<br>
> different sources. I just updated the GeoTools codebase with<br>
> its core LGPL LICENSE.md<br>
> <<a href="https://github.com/geotools/geotools/blob/main/LICENSE.md" rel="noreferrer" target="_blank">https://github.com/geotools/geotools/blob/main/LICENSE.md</a>>,<br>
> followed by a clear notice<br>
> <<a href="https://github.com/geotools/geotools/blob/main/licenses/README.md" rel="noreferrer" target="_blank">https://github.com/geotools/geotools/blob/main/licenses/README.md</a>> describing<br>
> listing all the individual licenses<br>
> <<a href="https://github.com/geotools/geotools/tree/main/licenses" rel="noreferrer" target="_blank">https://github.com/geotools/geotools/tree/main/licenses</a>> for<br>
> content we have collected from the internet. As an example the<br>
> project includes the EPSG database so EPSG.md<br>
> <<a href="https://github.com/geotools/geotools/blob/main/licenses/EPSG.md" rel="noreferrer" target="_blank">https://github.com/geotools/geotools/blob/main/licenses/EPSG.md</a>> is<br>
> there as a data distribution license.<br>
> <br>
> While the authoritative place for distribution may be CRAN, the<br>
> source code that generates the work is what would be reviewed when<br>
> auditing a codebase. Having the license information alongside your<br>
> code is consistent with the GPL-2 header "/You should have received<br>
> a copy of the GNU General Public License along with this program/"<br>
> snippet, and protects your ass-ets.<br>
> <br>
> Licenses are all about communicating intent, by choosing github as<br>
> your forge it is best to follow their conventions for communicating<br>
> license information to avoid confusion.<br>
> <br>
> Although we are focused on the source code (being an open source<br>
> foundation), your distribution via CRAN<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><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>>) is ...<br>
> incomplete:<br>
> <br>
> 1) link to LICENSE:<br>
> <a href="https://cran.r-project.org/web/packages/sf/LICENSE" rel="noreferrer" target="_blank">https://cran.r-project.org/web/packages/sf/LICENSE</a><br>
> <<a href="https://cran.r-project.org/web/packages/sf/LICENSE" rel="noreferrer" target="_blank">https://cran.r-project.org/web/packages/sf/LICENSE</a>> is just a<br>
> copyright declaration<br>
> <br>
> /YEAR: 2016-2020/<br>
> /COPYRIGHT HOLDER: Edzer Pebesma/<br>
> <br>
> <br>
> 2) link to GPL-2: <a href="https://cran.r-project.org/web/licenses/GPL-2" rel="noreferrer" target="_blank">https://cran.r-project.org/web/licenses/GPL-2</a><br>
> <<a href="https://cran.r-project.org/web/licenses/GPL-2" rel="noreferrer" target="_blank">https://cran.r-project.org/web/licenses/GPL-2</a>> seems okay<br>
> 3) link to MIT: <a href="https://cran.r-project.org/web/licenses/MIT" rel="noreferrer" target="_blank">https://cran.r-project.org/web/licenses/MIT</a><br>
> <<a href="https://cran.r-project.org/web/licenses/MIT" rel="noreferrer" target="_blank">https://cran.r-project.org/web/licenses/MIT</a>> has not yet filled in<br>
> the MIT license (just has the template):<br>
> <br>
> Based on <a href="http://opensource.org/licenses/MIT" rel="noreferrer" target="_blank">http://opensource.org/licenses/MIT</a><br>
> <<a href="http://opensource.org/licenses/MIT" rel="noreferrer" target="_blank">http://opensource.org/licenses/MIT</a>><br>
> <br>
> /This is a template. Complete and ship as file LICENSE the<br>
> following 2/<br>
> /lines (only)/<br>
> /<br>
> /<br>
> /YEAR:/<br>
> /COPYRIGHT HOLDER: /<br>
> /<br>
> /<br>
> /and specify as/<br>
> /<br>
> /<br>
> /License: MIT + file LICENSE/<br>
> /<br>
> /<br>
> /Copyright (c) <YEAR>, <COPYRIGHT HOLDER>/<br>
> /<br>
> /<br>
> /Permission is hereby granted, free of charge, to any person<br>
> obtaining/<br>
> /a copy of this software and associated documentation files (the/<br>
> /"Software"), to deal in the Software without restriction,<br>
> including/<br>
> /without limitation the rights to use, copy, modify, merge,<br>
> publish,/<br>
> /distribute, sublicense, and/or sell copies of the Software, and to/<br>
> /permit persons to whom the Software is furnished to do so,<br>
> subject to/<br>
> /the following conditions:/<br>
> /<br>
> /<br>
> /The above copyright notice and this permission notice shall be/<br>
> /included in all copies or substantial portions of the Software./<br>
> /<br>
> /<br>
> /THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,/<br>
> /EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF/<br>
> /MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND/<br>
> /NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT<br>
> HOLDERS BE/<br>
> /LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN<br>
> ACTION/<br>
> /OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN<br>
> CONNECTION/<br>
> /WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE./<br>
> <br>
> --<br>
> Jody Garnett<br>
> <br>
> <br>
> On Thu, 1 Jul 2021 at 13:35, Edzer Pebesma<br>
> <<a href="mailto:edzer.pebesma@uni-muenster.de" target="_blank">edzer.pebesma@uni-muenster.de</a><br>
> <mailto:<a href="mailto:edzer.pebesma@uni-muenster.de" target="_blank">edzer.pebesma@uni-muenster.de</a>>> wrote:<br>
> <br>
> 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<br>
> 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<br>
> 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<br>
> because the<br>
> authoritative place for released versions is CRAN, which has a<br>
> 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><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<br>
> you can see<br>
> that the licenses are listed with to their corresponding texts.<br>
> If I<br>
> would add a LICENSE.md, it duplicates and could be one more<br>
> source for<br>
> confusion. This is also the reason we don't do github tags or<br>
> releases,<br>
> as CRAN archives all releases; look for "Old sources", which in<br>
> 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>
> <<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<br>
> 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<br>
> 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<br>
> even seen<br>
> presentations on the *sf* in my local university down "geogeeks"<br>
> 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<br>
> osgeo<br>
> project page, and I did not see anything yet...<br>
> <br>
> Checking your github repositories such as<br>
> <a href="https://github.com/r-spatial/sf" rel="noreferrer" target="_blank">https://github.com/r-spatial/sf</a> <<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<br>
> (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><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>><br>
> 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<br>
> community, ... but<br>
> this is a bit more focused on having a policy for things like<br>
> pull requests.<br>
> - Massive number of closed pull requests from a wide range of<br>
> contributors<br>
> - For sf I did not find a CONTRIBUTING.md file (shown to folks<br>
> making a<br>
> pull request) but the README has heading about contributing<br>
> 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<br>
> 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<br>
> 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<br>
> <a href="http://gmail.com" rel="noreferrer" target="_blank">gmail.com</a> <<a href="http://gmail.com" rel="noreferrer" target="_blank">http://gmail.com</a>>> wrote:<br>
> <br>
> > We would like to apply, as the 'R-Spatial' community, to<br>
> become an OSGeo<br>
> > affiliated organisation.<br>
> ><br>
> > We are a diverse group with a shared interest in developing<br>
> 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<br>
> science'. It<br>
> > is already part of the OSGeo ecosystem: the OSGeo Live<br>
> distribution ships<br>
> > with R<br>
> <<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>
> <<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<br>
> GRASS GIS<br>
> > <<a href="https://grasswiki.osgeo.org/wiki/R_statistics" rel="noreferrer" target="_blank">https://grasswiki.osgeo.org/wiki/R_statistics</a><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><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><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<br>
> benefit<br>
> > from being updated) are listed on the tutorials listed on<br>
> 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><br>
> <<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<br>
> tutorials for<br>
> using<br>
> > R-Spatial software. Many R-Spatial projects have support<br>
> from the R<br>
> > Consortium <<a href="https://www.r-consortium.org/" rel="noreferrer" target="_blank">https://www.r-consortium.org/</a><br>
> <<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<br>
> <a href="http://github.com/r-spatial" rel="noreferrer" target="_blank">github.com/r-spatial</a> <<a href="http://github.com/r-spatial" rel="noreferrer" target="_blank">http://github.com/r-spatial</a>>, it<br>
> > is clear that closer links could be mutually beneficial.<br>
> Collaboration is<br>
> > at the heart of open source software and the R community has<br>
> a long<br>
> > history. The history of R-GRASS GIS bridges, for example,<br>
> 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><br>
> <<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<br>
> interface.<br>
> ><br>
> > Continued development and innovation in R-OSGeo links are<br>
> illustrated the<br>
> > qgisprocess <<a href="https://github.com/paleolimbot/qgisprocess" rel="noreferrer" target="_blank">https://github.com/paleolimbot/qgisprocess</a><br>
> <<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><br>
> <<a href="http://github.com/paleolimbot/qgisprocess/issues/21" rel="noreferrer" target="_blank">http://github.com/paleolimbot/qgisprocess/issues/21</a>>). The<br>
> R-Spatial community<br>
> > relies on the OSGeo projects GDAL, PROJ and GEOS for data<br>
> access and<br>
> > geographic operations. Core R-Spatial packages sf, raster<br>
> and terra use<br>
> > bindings to the libraries for much of the heavy lifting and<br>
> many<br>
> thousands<br>
> > of people using R for spatial research (often without<br>
> knowing) run OSGeo<br>
> > support code every day. We would like to support the ongoing<br>
> work of<br>
> these<br>
> > vital components of the wider community that is represented<br>
> 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<br>
> 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,<br>
> projects and<br>
> > people using R for working with and adding value to spatial<br>
> 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><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<br>
> define<br>
> > R-Spatial as the packages found at<br>
> <a href="https://github.com/r-spatial/" rel="noreferrer" target="_blank">https://github.com/r-spatial/</a> <<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<br>
> popular packages<br>
> > for working with spatial data) and<br>
> <a href="https://github.com/rspatial/" rel="noreferrer" target="_blank">https://github.com/rspatial/</a> <<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)<br>
> 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>
> <<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<br>
> another.<br>
> ><br>
> > We would like to initiate the process needed for R-Spatial<br>
> to eventually<br>
> > become an OSGeo community project, by achieving the first<br>
> 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>
> <<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<br>
> information about key<br>
> > packages in the 'R-spatial stack', including how they<br>
> 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>
> <<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<br>
> Lovelace, Roger<br>
> > Bivand, Edzer Pebesma, Tim Appelhans, Robert Hijmans, Jakub<br>
> Nowosad, Nick<br>
> > Bearman, Emmanuel Blondel, Andy Teucher, Marynia Kolak,<br>
> 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> <<a href="http://lists.osgeo.org" rel="noreferrer" target="_blank">http://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>
> <<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> <mailto:<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>
> <<a href="https://lists.osgeo.org/mailman/listinfo/incubator" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/incubator</a>><br>
> <br>
<br>
-- <br>
Edzer Pebesma<br>
Institute for Geoinformatics<br>
Heisenbergstrasse 2, 48151 Muenster, Germany<br>
Phone: +49 251 8333081<br>
</blockquote></div>