-
Notifications
You must be signed in to change notification settings - Fork 4
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
Comments
@salvafern said yes |
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? |
emodfeat |
what I have no doubt about is that the current name is hard to type. |
maybe emodnet.wfs since we'd have emodnet.wcs |
emodnet.features |
maybe even better would be an acronym |
pufferfish = has P like package, f like feature, e like emodnet, s like service. and it inflates the amount of data you have. |
starfish in honor of the EU flag |
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. |
or a boat name starting with f for WFS, one starting with c for WCS. |
|
althought it might seem insulting than one of those boats is clearly smaller. |
@salvafern thoughts? |
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 |
Love the brainstrom :) As a simple solution I would choose Or something that reflects that one serves vector and the other raster I will drop more creative ideas as they come |
@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. |
@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. |
@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
The text was updated successfully, but these errors were encountered: