[Incubator] Initiating the process for R-Spatial to become an OSGeo community project - Update

Nick Bearman nick at geospatialtrainingsolutions.co.uk
Wed Aug 31 00:47:27 PDT 2022


Hi Jody,

Thanks for your email. Sorry if I jumped the gun a bit with R-Spatial - 
from my understanding of what I read and what we walked about, I though 
it was ok to post the page live. I think the previous review got lost 
with the handover to me, so apologies for having to make you type it out 
again!

On 8/30/22 21:45, Jody Garnett wrote:
> Okay so let me try the review again:
>
> Website page feedback (and some edits since it is already live):
>
> 1. The logo - do you have one? I guess I see the same thing on your 
> website ...

The logo is the image here - 
https://www.osgeo.org/wp-content/uploads/logo-14-370x206.png - with 
variations on a theme here - 
https://github.com/r-spatial/r-spatial.org/blob/gh-pages/images/logo.png.

> 2. The description includes a lot of raw URLs, I edited to make these 
> text and easier to read
Thanks. I'd already tidied these up a bit, so thanks for catching the 
other ones.
> 3. Is it possible to make a screen snaps showing a code example or or 
> a visual result (it is important for folks to have an idea of what the 
> program looks like even if it is only analysis)
Yes - we can add this
> 4. The license part is understandably hard to follow, can I just ask 
> if all of the libraries are open source or free software (the example 
> you cite is GPL-2 or MIT). I added a footer with your explanation and 
> left the license part simple showing a list of licenses I saw (you 
> perhaps know more)
I will check and confirm
> 5. You have some links to user blog and twitter, but no developer 
> links to source code or build instructions. I added some but perhaps 
> you have more?
These are all by project, so I think what you have is fine. I will check.
> 6. The projects (https://r-spatial.org/projects/) are a challenge, 
> with the ESRI one not being open source. Would it be smart to list 
> licenses on that page?
I will check about this. We might rearrange to a more logical layout 
(OSGeo R-Spatial Project libraries, and links to other libraries).
> 7. Core contributors ... are there any R-Spatial service providers 
> available?
We have a range of individuals - can we add these similar to the 'Who's 
involved' list? Or do they have to be added to OSGeo as an explicit 
Service Provider? I will also be adding myself as a service provider.
> 8. Changed the description to say "open source project" while we wait 
> for incubation committee and board motion
Ok, thanks. I wasn't clear on the process.
>
> Project review: This is a challenge since there are several projects 
> in one family; we can limit the check to the ones listed on the 
> website page or the projects <https://r-spatial.org/projects/> page of 
> your website. (The https://r-spatial.github.io/sf/ page is so cute 
> with little mascots).

Thanks :-)

Yes, makes sense to limit this to the ones listed on the website. We 
might rearrange this page as per #6.

>
> 1. geospatial
> - geospatial: https://github.com/r-spatial/sf/blob/main/README.md - 
> geospatial
> - user docs or quickstart: https://r-spatial.github.io/sf/ and 
> https://r-spatial.github.io/sf/ <-- the cheatsheet is great
> 2. free or open source
> - https://github.com/r-spatial/sf/blob/main/LICENSE <-- this is not 
> complete
We can work on this
> - checking headers:
> - https://github.com/r-spatial/sf/blob/main/R/RcppExports.R - generated
> - https://github.com/r-spatial/sf/blob/main/R/bind.R - no header applied
> - https://github.com/r-spatial/sf/blob/main/src/bbox.h - no header
> - https://github.com/r-spatial/sf/blob/main/src/gdal_read.cpp - no header
> 3. Participatory
> -
> CONTRIBUTING.md - do not see this (file shown when making a pull request)
Yes, this is something we can add
> - https://github.com/r-spatial/sf/pulls can see a lot of successful 
> pull requests so that is great
> 4. code of conduct
> - https://github.com/r-spatial/sf/blob/main/CONDUCT.md - great
>
> So it looks like for the *sf* module there is some work to do on 
> headers; I am going to hold off checking any more.

Thanks. I'll get back to you with the more detailed stuff in due course.

>
> Jody


Many thanks,

Nick.

-- 
Nick Bearman
+44 (0) 7717745715
nick at geospatialtrainingsolutions.co.uk

Due to my own life/work balance, you may get emails from me outside of normal working hours. Please do not feel any pressure to respond outside of your own working pattern.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/incubator/attachments/20220831/7668b12f/attachment-0001.htm>


More information about the Incubator mailing list