571415 - Rename hgpvt.m.o to shg.m.o

Status: RESOLVED WONTFIX

(mozilla.org Graveyard :: Server Operations, task)

Description

[Reed Loden [:reed]]

We'd like to get hgpvt.mozilla.org renamed to shg.mozilla.org (pronounced "shag"). If we could get this done soon before people start using or remembering the old name, that would be great.

Comment 1

[Al Billings [:abillings - ex-MoCo]]

Shagadelic, baby!

Comment 2

[Daniel Veditz [:dveditz]]

I care much more that we _have_ a repo than what we call it, but a couple of people have expressed concern about the implications of the name "private". I'm not entirely sure what the concerns are, one might be simply that we're doing things in private and hiding code. I strongly suspect that those people will object no matter what we call it and a name that hints more at "security" than generic "private stuff" won't mollify them.

Another objection might be that a more generic "private" name might attract more private projects in the future. I personally think we can rely on our culture to not abuse that. For instance, the recent WebM code was handled appropriately but still temporarily privately even though we didn't have a server with the name "private" in it.

Raising severity because we either need to resolve or WONTFIX this issue today -- it's blocking the next step of creating the builds scripts.

Comment 3

[Johnny Stenback (:jst)]

I'd say if we can fix this fast we should. If not, we can probably live with this but I'd rather not get stuck with this and regret it later. I can't say I feel super strongly either way though.

Comment 4

[Lucas Adamski [:ladamski]]

Yeah, I am a bit concerned that the naming might be misconstrued down the line.  Lets just make the change and git moving (har har).

Comment 5

[Mike Shaver (:shaver emeritus)]

Who is "we" in comment 0?  Why no reason given? Seems like bikeshedding, which shouldn't block solving actual problems. Pretty disappointing.

Private is fine, that's the purpose of it. If the server name causes more things to be private, we have problems that a hostname change won't fix.

Changing the name and scripts after also seems tenable if the world opens up and swallows something because of this DNS entry.

Please move ahead with all reasonable haste.