FYI pants.build now redirects to <pantsbuild.org>
# general
h
FYI pants.build now redirects to pantsbuild.org
🙌 3
❤️ 1
🤘 1
👖 3
🤩 2
🤘🏽 1
h
Thoughts on it going the other way?
pants.build
is easier to remember imo
p
migrating domains is a lot more work I suspect. But
pants.build
is definitely "cooler" 😉
💯 1
h
That's more work than it's worth, and the redirect means it doesn't matter what you remember
h
Counterpoint is what link do we want others sharing on the project's behalf, e.g. when sending a link to a coworker? It's fine for core Pants contributors to use pants.build in talks etc, but users will probably copy and paste what they see in the domain bar pants.build is more memorable and shorter
p
Depending on how you have it hosted, you can make
pants.build
and
<http://pantsbuild.org|pantsbuild.org>
both show the same content (CNAME instead of redirecting). But put a header that says the canonical url is
pants.build
. Then down the road, look at redirecting the other way.
1
b
I prefer pantsbuild.org which signals that it's a nonprofit project. Also, in my experience there is always someone who instinctually tries to tack on ".com" to a domain like these. So we'd wind up having to deal with pants.build.com too and we don't own build.com so...
h
That's fair. It is very important to the community that Pants is independent and not owned by a particular company
b
It's fine that pants.build and pantsbuild.org both exist and there's a redirect. Between coolness and accuracy, I prefer whatever gets people to the intended resource reliably.
👍 1
I see also that another problem is that a domain name like pants.build isn't reliably autoformatted/linked as a URL, for instance by Slack. 😆
3