Open iamjoshfrank opened 4 years ago
nightingale.com TAKEN nightingalehealth.com TAKEN nightingaleapp.com TAKEN nightingaletracing.com AVAILABLE nightingale.io AVAILABLE (premium domain; $50 offer on GoDaddy)
@iamjoshfrank, @prehnRA, @thomasknoll and @jeremybrady. Tagging y'all here to get your thoughts on the suggested domains above. Could obviously keep searching, but maybe there's a winner here, or you guys have other thoughts?
Keeping in mind the audience for this landing page is key.
Also, keeping in mind that "Nightingale" may or may not be the name of whatever apps/web apps/other resources we release to the public...
My overall opinion is that "Nightingale" is the name of the Open Source project, and that any other naming/branding considerations for individual product(s) may or may not follow that naming.
And, since we're working on multiple problem/solution sets beyond tracing, we shouldn't include tracing in the domain name.
If we think about the landing page being primarily for contributors and sponsors and less about end users, then I think we have lots of leeway about what domain we pick.
For instance, for a general audience of potential end users, I don't think I'd choose a .io
domain. But if/since we're focused right now on contributors/sponsors, it's probably fine - so I think nightingale.io
is a good potential option.
If I were going to offer other suggestions, I might peruse the availability of things like "Project Nightingale" or "Nightingale Project," since, again, the Nightingale name is really only attached at this point to the collective Open Source efforts that we are leading through the Revelry Foundation (and, again, not necessarily going to be used for the product(s) themselves).
IMHO:
@thomasknoll, I think that's a wise move given all the context. No need to spend money we don't have to.
Making the call here that we're going to proceed with http://nightingale.revelry.co
.
No arguments from me.
Can I get somebody to update the DNS in DNSimple? I need an "A" record that points nightingale.revelry.co to 35.239.66.235
@bit-herder Any chance I could get you to assist with the DNSimple bit above?
I just want to confirm that we're pointing nightingale.revelry.co to 35.239.66.235 and that this IP is not the application server currently hosted in the nightingale cluster?
@vaxinate Correct. that IP is only for the website, not for the app.
job's done!
@vegasgeek, I believe we're good to shuttle this little baby along, huh?
@westonmcwhorter too late, we're already done! Site is live at: https://nightingale.revelry.co/
Probably good to close this for now unless a different domain is planned in the future.
Sick. Pushing along to QA/UAT.
this is extremely nitpicky, but i'm seeing .org as opposed to .co, which is what was prescribed above. i'm going to go ahead and say this passes, as i don't think this is a big deal, but calling it out that there's a discrepancy.
@georgiapetagna that is NOT nitpicky and if you see a discrepancy in URLs, always point it out!
In this case, it just so happens that this change was on purpose. the AC should be updated to reflect the use of nightingale.revelry.org
Background
We have initial approval on the landing page for Nightingale. Now, we need an appropriate URL to point to.
Scenario: Project Domain Name
Given I am working on the Landing Page milestone,