-
Notifications
You must be signed in to change notification settings - Fork 14
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
Proposal to rename the Repository #91
Comments
I'm in the middle of writing the README and fixing the CONTRIBUTING docs and I'm changing the references to just "Hurricane API". I am entirely on-board with renaming to something similar "hurricane-api" being the most obvious option, but I'm open to other options if anyone has something better suited. |
Definitely agree on this, and we should do now, so we can see the issues and fix them before GHC stuff starts and before we have another response event. We should also eventually change the database name to something more general too, but that can wait if it's too big a change. |
I'm fine with |
I think I used response at the time as we were discussing other disasters beyond hurricanes such as the earthquake drill. |
Reading the contributing docs @omnilord is updating, it definitely makes sense to go ahead & change the repo name now so can change the links now. I'm +1 on response-api but hurricane-api is fine with me. |
Let's go with |
We now have a new instance running on https://api.hurricane-repsonse.org from this repository.
I know there are still references to Harvey in the API but other than possibly breaking check outs and automated tools (important!) I'm not aware of any other negative effects of renaming, but would help clarify that this is the main on-going repository and not related to a 2018 storm.
The text was updated successfully, but these errors were encountered: