Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

New Maintainer Wanted #62

Closed
maelle opened this issue Jan 6, 2023 · 18 comments
Closed

New Maintainer Wanted #62

maelle opened this issue Jan 6, 2023 · 18 comments
Labels
help wanted

Comments

@maelle
Copy link
Member

maelle commented Jan 6, 2023

Or new maintainer team. 😸

The following issues would need to be solved

If you're interested, please comment in the issue.
For more info, see

Cc @andysouth @ropensci/admin @z3tt
@maelle maelle mentioned this issue Jan 6, 2023
Closed
@khufkens
Copy link
Member

khufkens commented Jan 6, 2023

Will look into #60 as I use the package too often and I'm doing the same for a number of my packages.

Won't take over maintenance as this is soulless task which provides little or no credit or joy for that matter.

FYI. ropensci should invest more in this instead of the user facing component IMO. No maintainer = no software = no users

@PMassicotte
Copy link
Contributor

I do not mind giving a hand :)

@opus1993
Copy link

opus1993 commented Jan 6, 2023

How can I help?

@maelle
Copy link
Member Author

maelle commented Jan 10, 2023

@khufkens thanks a lot for #63!

@PMassicotte @opus1993 Thank you! Do you want write access to the repository to review and merge @khufkens' PR to begin with? Does one of you want to become the maintainer (you could be co-maintainers as well)?

@maelle
Copy link
Member Author

maelle commented Jan 10, 2023

@defuneste thanks for your contribution in #63! Are you interested in contributing further?

@PMassicotte
Copy link
Contributor

I do not mind being a maintainer or being part of the maintainer team :)

@defuneste

This comment was marked as off-topic.

Sign in to view
@maelle

This comment was marked as off-topic.

Sign in to view
@andysouth
Copy link
Contributor

Hi @PMassicotte @defuneste @khufkens @maelle

Many thanks for your help and offers. Apologies I have been quiet. I haven't been working in this area for a little while and I was struggling to keep up. Also my package workflows are rusty !

@PMassicotte would you like to take over as primary maintainer and I can help out as needed ? It would be much appreciated.

@andysouth
Copy link
Contributor

Hello @mps9506 You've been really good at responding to issues (better than me). I wonder if you might want to contribute to package maintenance in future and be mentioned as such ?

@PMassicotte
Copy link
Contributor

Hi @andysouth that would be a great pleasure! Let me know how you want to make it work :)

Cheers,
Phil

@andysouth andysouth mentioned this issue Jan 12, 2023
Closed
@andysouth
Copy link
Contributor

Thanks @PMassicotte Philippe,
Would you be OK to take on the submission to CRAN ? I can indicate you as the maintainer and perhaps @maelle can give you write access to the repo ?
Andy

@maelle
Copy link
Member Author

maelle commented Jan 12, 2023

@andysouth I've even given admin access to @PMassicotte as we do these days for maintainers. :-)

@andysouth
Copy link
Contributor

Many thanks @maelle :-)

@PMassicotte
Copy link
Contributor

PMassicotte commented Jan 12, 2023 •
edited
Loading

Should we first submit the current version as it solve broken URLs?

@andysouth
Copy link
Contributor

Seems like a good idea :-) Unless people come back strongly and quickly with responses to #65. I'm just about to merge the PR.

@defuneste
Copy link

@andysouth No need or me and thx for the package!

PMassicotte added a commit that referenced this issue Jan 12, 2023
@PMassicotte
New maintainer (see #62).
adc07b7
andysouth added a commit that referenced this issue Jan 12, 2023
@andysouth
Merge pull request #66 from ropensci/new-maintainer
465a020 
New maintainer (see #62).
@mps9506
Copy link
Contributor

mps9506 commented Jan 12, 2023

@andysouth happy to assist as needed. 👍🏽

netbsd-srcmastr pushed a commit to NetBSD/pkgsrc that referenced this issue Nov 28, 2024
(geography/R-rnaturalearth) updated 0.1.0 to 1.0.1
70abef3 
# rnaturalearth 1.0.1

# rnaturalearth 1.0.0

## Breaking changes

This is a breaking changes release that ends support to `sp` object in
favour of more modern interfaces (`sf` and `terra`). Although that
`sp` is still available on CRAN, it is no longer being actively
developed (https://geocompx.org/post/2023/rgdal-retirement/). This is
the main reason that motivated the choice to transition toward `sf`
(the default) and `terra`.

Users can choose either get an `sf` or `SpatVector` using the
`returnclass` argument:

```
ne_countries(returnclass = "sf")
ne_countries(returnclass = "sv")
```

Affected functions are `ne_countries()`, `ne_coastline()`,
`ne_states()`, `ne_load()` and `ne_download()`.

If changing the return type to `sf` creates too many problems to your
existing code, you can still convert it back to `sp` :

```
countries <- ne_countries(returnclass = "sf")

# option 1
sf::as_Spatial(countries)


# option 2
as(countries, "Spatial")
```

More information about the retirement of `rgdal`, `rgeos` and
`maptools`: https://r-spatial.org/r/2022/04/12/evolution.html

## Bugfix

- Correctly downloading and reading raster object (#96, closes #52).

# rnaturalearth 0.3.4

- This is a maintenance release that document/use the new special sentinel "\_PACKAGE".

# rnaturalearth 0.3.3

- Using `lifecycle` to indicate that support of `sp` object will be
  eventually dropped. Users should now use `ne_download(returnclass =
  "sf")`, instead of `ne_download(returnclass = "sp")`.

- `terra` is now included in the Imports section.

# rnaturalearth 0.3.2

- Added new maintainer and contributors ([#62](ropensci/rnaturalearth#62)).
- Using terra over raster ([#63](ropensci/rnaturalearth#63))

  - See
    <https://r-spatial.org/r/2022/04/12/evolution.html#packages-depending-on-sp-and-raster>
    and
    <https://r-spatial.org/r/2022/12/14/evolution2.html#deprecations-in-retiring-packages>

- Fixes broken data download links.  Now using Amazon hosted URLs as
  - the primary source for downloading data
  - ([#48](ropensci/rnaturalearth#48),
  - [#64](ropensci/rnaturalearth#64)).

# rnaturalearth 0.3.0 2021-10-11

- fix rnaturalearthhires installation #47 thank you Ian Taylor for #43

# rnaturalearth 0.2.0

- add to river options in ne_download() by adding to
  data_list_physical.csv fixing
  [#23](ropensci/rnaturalearth#23)

- update data to new version [Natural Earth
  v4.1](https://www.naturalearthdata.com/blog/miscellaneous/natural-earth-v4-1-0-release-notes/)
  released May 2018.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
help wanted
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
7 participants
@khufkens @andysouth @PMassicotte @maelle @mps9506 @defuneste @opus1993