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

could we rename the package to all lowercase? #163

Open
maelle opened this issue Mar 21, 2024 · 18 comments
Open

could we rename the package to all lowercase? #163

maelle opened this issue Mar 21, 2024 · 18 comments

Comments

@maelle
Copy link
Collaborator

maelle commented Mar 21, 2024

@salvafern Any thought? Lowercase is easier to type. Now is a good time to rename the package (as opposed to after a first CRAN release for instance)

https://devguide.ropensci.org/pkg_building.html#naming-your-package

@maelle maelle added this to the rOpenSci submission milestone Mar 21, 2024
@maelle
Copy link
Collaborator Author

maelle commented Apr 16, 2024

@salvafern said yes

@maelle
Copy link
Collaborator Author

maelle commented Apr 22, 2024

I am having second thoughts! "emodnetwfs" is probably not great for screen-reader users. What about "emodnetWFS"? or "emodnetfeatures"? Who else could we ask for a third opinion?

@maelle
Copy link
Collaborator Author

maelle commented Apr 22, 2024

emodfeat

@maelle
Copy link
Collaborator Author

maelle commented Apr 22, 2024

what I have no doubt about is that the current name is hard to type.

@maelle
Copy link
Collaborator Author

maelle commented Apr 22, 2024

maybe emodnet.wfs since we'd have emodnet.wcs

@maelle
Copy link
Collaborator Author

maelle commented Apr 22, 2024

emodnet.features

@maelle
Copy link
Collaborator Author

maelle commented Apr 22, 2024

maybe even better would be an acronym

@maelle
Copy link
Collaborator Author

maelle commented Apr 22, 2024

pufferfish = has P like package, f like feature, e like emodnet, s like service. and it inflates the amount of data you have.

@maelle
Copy link
Collaborator Author

maelle commented Apr 22, 2024

starfish in honor of the EU flag

@maelle
Copy link
Collaborator Author

maelle commented Apr 22, 2024

I still think we should get an opinion from others. A name related to the ocean, with a paired name for EMODnetWCS would be really nice.

@maelle
Copy link
Collaborator Author

maelle commented Apr 22, 2024

or a boat name starting with f for WFS, one starting with c for WCS.

https://en.wikipedia.org/wiki/Category:Boat_types

@maelle
Copy link
Collaborator Author

maelle commented Apr 22, 2024

  • ferry (feature service for emodnet, in R)
  • coble (coverage service for emodnet)

@maelle
Copy link
Collaborator Author

maelle commented Apr 22, 2024

althought it might seem insulting than one of those boats is clearly smaller.

@maelle
Copy link
Collaborator Author

maelle commented May 10, 2024

@salvafern thoughts?

@JoBeja
Copy link

JoBeja commented May 17, 2024

Hey, I think that it would be good to clearly identify the packages as EMODnet... If I have any ideas I'll put them through

@salvafern
Copy link
Collaborator

Love the brainstrom :)

As a simple solution I would choose emodnetwfs: easy to write, remember, straight to the point.. and indeed no upper case. Not a big fan of those myself.

Or something that reflects that one serves vector and the other raster

I will drop more creative ideas as they come

@maelle
Copy link
Collaborator Author

maelle commented May 21, 2024

@JoBeja that's a good point. Now, could it be enough to state this clearly in the documentation and metadata?

The problem with emodnetwfs is that it could at first look hard to pronounce and remember.

@JoBeja
Copy link

JoBeja commented May 21, 2024

@maelle no I don't think it is enough. As I see it, it's mainly a matter of branding. I think our R packages don't have a lot of visibility and using a name that immediately identifies them as EMODnet is important.
Acronym pronounciation varies across the globe, some countries read each letter separately, others read it as if it was a word, we're not going to please everyone, whatever choice we make.

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

3 participants