On Wed, Aug 7, 2013 at 11:58 AM, Herbert Valerio Riedel <[email protected]> wrote: > Hello Jason, > > We'd need a new "git.haskell.org" CNAME pointing to ghc.haskell.org for the > new Git(olite) setup. When could you register such a CNAME?
Apologies for taking so long to respond. I've been traveling for the last week without good Internet access. A few questions: Is "git" the name we're going to want to keep indefinitely for this? Once you create a URL (and consequently a domain name) it's nice to keep it around so that anyone using it can still use it. Even if that means keeping the (sub)domain for years. Perhaps a more generic name would be more suitable, for example "scm" (for source code management)? If we use something that is tool/technology specific then we need to update the (sub)domain when the tool/technology changes, lest we sound silly. Will GHC's source be the only repository? I think we should only do our own hosting when it's necessary. When GHC switched to darcs, hosting services didn't support darcs so it was necessary to roll our own. Now that there are good free git-based hosting services (github, bitbucket, sourceforge, and probably others), is there a reason GHC can't use an existing service? If GHC really needs a homegrown service, who is volunteering to keep it running smoothly and for how long? What is the plan for phasing it out once it's no longer needed or the maintainer disappears? I have access to the haskell.org DNS account to be able to add the domain, but I would prefer to delegate to one of our volunteer sysadmins. Hence, I've CC'd the haskell-infrastructure list. Who wants to be in-charge of the ghc.haskell.org domain? Thanks, Jason _______________________________________________ haskell-infrastructure mailing list [email protected] http://community.galois.com/mailman/listinfo/haskell-infrastructure
