Bitbucket
https://bitbucket.org/account/signin/?next=/
Username: reg360
I did a lot of research for how to publicly manage and archive specialized data like programming code, probably more than necessary given the casual nature of my precious trinkets. The following[1] is what sold me on the Mercurial approach of version|revision control, and why I chose it for my default in Bitbucket. I understood the theoretical basis for what the author was saying about retaining the "family history" of a project. I am one of the mentioned novices trying to reduce any future confusion for anyone reviewing my work, most importantly my future self. Usually I avoid adopting a viewpoint about which I have no supporting background to help me understand it. So I can't even grasp what the heck is the diff between Git's merge and rebase. All I know is that I don't want my evolving code to have that controversy to begin with. Yep, I fell for the presented FUD: "Git creates complexity and solves it. Mercurial avoids the complexity all together." But what do I know? I haven't figured out--as of this writing--how to even do the most elementary Mercurial pull request and merge back into the main trunk! But SourceTree as a GUI frontend does seem helpful enough. (Why should I use Hg via command-line? Bah, what is this, Unix?)
As for why Atlassian's Bitbucket for my DVCS? Well I read it was Python (via Django), so I was immediately favorably biased. Then, they have a free service tier which includes some private space. They also make that pretty SourceTree client to hold my hand. Also, I do appreciate that Bitbucket does provide a choice between Mercurial or Git. These other comparison reviews[2,3] provided a giggle, and indirectly lent some credence to a characterization of Git users that I focused on (speaking only for myself) from the JHW post I first mentioned.
Overall, I'm not prodigious enough to be a religious zealot for any of Git vs. Mercurial, or GitHub vs. Bitbucket. For the former, I'm happy if a methodology can be useful without too much "fiddly rules and secret handshakes." For the latter, if NASA's JPL uses a bunch of any company's development tools--even if not including the specific one I'm using--then that's still a nice toolset to be associated with!
[1] Why I Like Mercurial More Than Git
Mar. 29th, 2011
http://jhw.dreamwidth.org/1868.html
[2] GitHub and BitBucket
http://mitsuhiko.pocoo.org/github-vs-bitbucket/bitbucket.html
[3] GitHub vs. BitBucket: Shifting Value Propositions
2012-06-13
http://blog.ssokolow.com/archives/2012/06/13/github-vs-bitbucket-shifting-value-propositions/