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.

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

Renaming to RavenWPS #379

Open
cjauvin opened this issue Apr 15, 2021 · 9 comments
Open

Renaming to RavenWPS #379

cjauvin opened this issue Apr 15, 2021 · 9 comments
Assignees

Comments

@cjauvin
Copy link
Collaborator

cjauvin commented Apr 15, 2021

To avoid confusion, everything named raven in this project should be renamed to RavenWPS:

  • The conda environment (as defined in environment.yaml)
  • The repo itself (if possible)
@Zeitsperre
Copy link
Contributor

The how of doing this is pretty easy (we can migrate using the GitHub renaming functions) but we'll need to be careful as to when we decide to do this. Ideally, not before any big presentations. I imagine that the repercussions to the PAVICS stack will be significant.

@tlvu Is there a list off the top of your head of other projects/configurations that would need to be addressed ?

@tlvu
Copy link
Contributor

tlvu commented Apr 23, 2021

@tlvu Is there a list off the top of your head of other projects/configurations that would need to be addressed ?

Quickly on the top of my head:

All the automation stuffs like builds and release (DockerHub, RtD, ...) and rename in all documentation content. If we want to take it further to be 100% consistent: a massive find/replace "Raven" -> "RavenWPS", this would also impact the code.

Basically depending on how far we want but definitively more than just the repo name and the conda environment name.

@huard huard closed this as completed Apr 23, 2021
@huard huard reopened this Apr 23, 2021
@Zeitsperre
Copy link
Contributor

Perhaps we can open a PR to perform these changes within the library after #389 is merged.

@SarahG-579462
Copy link

Was discussing this with @Zeitsperre recently, a suggestion I had for the problem is to:

  • rename this repo/module to raven-wps
  • create a new python module called raven
  • the new module raven is simply a wrapper for raven-wps that issues a deprecation warning on import raven, telling users to change their import statement to ravenwps
  • eventually (say, in 1 year?) remove the raven module.

@Zeitsperre
Copy link
Contributor

Given that we've removed all components related to Raven, I think if we were to rename this, we should go much further and make a clean break from Raven entirely. We could brainstorm some new bird names!

@SarahG-579462
Copy link

My vote goes for Eastern Whip-poor-will (Engoulevent bois-pourri en Français)!

@Zeitsperre
Copy link
Contributor

Ouranosinc/scarlet-macaw

image

@SarahG-579462
Copy link

water bird for water models: magpie-goose, crane, rail

@Zeitsperre
Copy link
Contributor

Zeitsperre added a commit that referenced this issue Oct 18, 2024
## Overview

Changes:

* Added the cruft configuration back in.
* Fast-forwarded changes.
* Modified existing documentation to remove mentions of RavenPy.

## Additional Information

The library still relies on the older approach to testing data
management. I'd like to update this both here and in RavenPy, as
(despite their complete separation) they use the same testing data sets.

Like `finch`, perhaps we can add this to PyPI as well? I've updated the
PyPI name to `birdhouse-raven` but seeing as this project no longer is
associated with RavenPy, I still feel like the proposal in #379 should
be considered.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants