= phenomenon =
The Community Blog's default subdomain should be "commblog.fp.o".
= background analysis =
After discussions on the Marketing / CommOps mailing lists, it was determined that it would be easier for the upcoming Community Blog to have a shorter subdomain. The agreed subdomain would be "commblog.fp.o" with "communityblog.fp.o" as an alias that would redirect to the default subdomain.
= implementation recommendation =
As mentioned prior, both subdomains should still be valid, but the default subdomain should be "commblog.fp.o".
Plesae note that this needs changing in the wordpress instance.
Also, note that you should probably wait with announcing it until after the freeze (Fedora 23 release), since after then we'll be able to make sure it has HTTPS (for the people that havve HSTS entries for fedoraproject.org cached).
I couldn't find the relevant discussions on the marketing@ or commops@ lists, URL would be welcome.
What's the purpose of this shortening? It seems needlessly unparseable and jargonish to me, especially when most people reach our current-content sites like the Magazine through other links like social media.
Correct me if I'm wrong, but can't we do both?
Keep http://communityblog.fedoraproject.org, but also get a CNAME pointer, or a redirect, or somesuch websorcery for http://commblog.fedoraproject.org?
Even if it eventually resolves to the longer URL when it is displayed, it will save the typing for folks who want to get all jargonish about it (myself included), but still keep the full identity once you arrive?
Sure, there's no problem with having them both. But as said, I will set that up once we get out of freeze, unless this is absolutely critical?
Also note that I would strongly advice against going live with this until we get the proxy part setup. As said, otherwise a lot of people that have cached our HSTS entries (which have cache durations of up to 6 months and are very hard to clear) will be unable to visit it.
Note that if you really, REALLY, want to go live before, we can get a freeze break. But my suggestion would be to just wait a bit.
Replying to [comment:2 pfrields]:
I looked back through my inbox and I was mistaken, pretty sure this was a (brief) discussion in the marketing IRC channel at some point. In retrospect, I jumped the gun on this - it definitely could have used more discussion. Will make sure to do more searching next time before citing things based off of memory too.
I couldn't find the relevant discussions on the marketing@ or commops@ lists, URL would be welcome. What's the purpose of this shortening? It seems needlessly unparseable and jargonish to me, especially when most people reach our current-content sites like the Magazine through other links like social media.
I have to agree with Paul here. it introduces some ambiguity -- does "Comm" mean community or communication? I still get these confused with CommOps TBH.
For us that write for the blog, i understand that a smaller string is easier to type in emails etc, but for the users (i.e readers) of the blog, IMHO having abiguity and jargon-ness is not worth it for 5 letters.
So, was there any consensus or decision here?
Replying to [comment:8 kevin]:
So, was there any consensus or decision here? This ticket can probably be closed. The CommBlog launched a couple of weeks ago, and I don't ''personally'' see much value in having the shorter subdomain added at this point. My vote is to close the ticket.
This ticket can probably be closed. The CommBlog launched a couple of weeks ago, and I don't ''personally'' see much value in having the shorter subdomain added at this point. My vote is to close the ticket.
Not sure what others' thoughts are about still adding in the alias shorter subdomain?
ok, feel free to re-open if you want us to alias things.
Login to comment on this ticket.