Mercurial repos to Bitbucket
Hi everyone, There've been lots of problems with the hg server on hg.enzotools.org. It's time to move from there to somewhere else. I propose going to Bitbucket. This enables many things: forking, easier collaboration, pull reports, code review, and so on and so forth. Additionally, it will eliminate the timeouts that have plagued the hg.enzotools.org server. Bitbucket allows for domain redirection, so all the existing paths should continue to work, they will just be served by a different server. Can I get [+-][01] on going to Bitbucket? I'm trying to get us the 'yt' username, but haven't had luck yet. If the yt username is unavailable as of Sunday night, we'll need a backup name. I'd like to put this up for a vote: yt_analysis ytanalysis yt_astro ytastro [other] Can I get a vote on that, or any other suggestions? The upshot here is that we'll have hg.enzotools.org point to the user page for whatever we end up with (so it will still be http://hg.enzotools.org/yt/ to get to the yt repo, yt-doc for yt-doc, etc etc), but we also need a username. So if you go to BitBucket itself, rather than hg.e.o, you will see bitbucket.org/[username]/[project] . In addition, if you are reading this, can you email me off list with your BitBucket username so that I can add you to the access control list? For now I think it will be better if we ease ourselves into the BitBucket workflow and avoid being too free with Pull Requests, and so I'd like to add people to the write list for whatever repo we end up with. You can get a BitBucket username simply by logging in with your Google username, if you like, or create a new one. I'm MatthewTurk, for what it's worth. Thanks, Matt
Hi Matt, On Feb 24, 2011, at 9:28 AM, Matthew Turk wrote:
Hi everyone,
There've been lots of problems with the hg server on hg.enzotools.org. It's time to move from there to somewhere else.
I propose going to Bitbucket. This enables many things: forking, easier collaboration, pull reports, code review, and so on and so forth. Additionally, it will eliminate the timeouts that have plagued the hg.enzotools.org server. Bitbucket allows for domain redirection, so all the existing paths should continue to work, they will just be served by a different server.
Can I get [+-][01] on going to Bitbucket?
I'm trying to get us the 'yt' username, but haven't had luck yet. If the yt username is unavailable as of Sunday night, we'll need a backup name. I'd like to put this up for a vote:
yt_analysis ytanalysis yt_astro ytastro [other]
Can I get a vote on that, or any other suggestions?
My vote is 0, but I would ask if there is any benefit to having YT on Google Code, since that's where Enzo is. I don't know if there are any cross-project features that could be taken advantage of. --Rick
+1
Regarding the user name, I'd go 'yt_analysis', since for political reasons
you might want to avoid appending 'astro' (the subtle point there being that
yt would ONLY be useful for astro, and it may drive away people, consciously
or unconsciously.
B
On Thu, Feb 24, 2011 at 12:28 PM, Matthew Turk
Hi everyone,
There've been lots of problems with the hg server on hg.enzotools.org. It's time to move from there to somewhere else.
I propose going to Bitbucket. This enables many things: forking, easier collaboration, pull reports, code review, and so on and so forth. Additionally, it will eliminate the timeouts that have plagued the hg.enzotools.org server. Bitbucket allows for domain redirection, so all the existing paths should continue to work, they will just be served by a different server.
Can I get [+-][01] on going to Bitbucket?
I'm trying to get us the 'yt' username, but haven't had luck yet. If the yt username is unavailable as of Sunday night, we'll need a backup name. I'd like to put this up for a vote:
yt_analysis ytanalysis yt_astro ytastro [other]
Can I get a vote on that, or any other suggestions? The upshot here is that we'll have hg.enzotools.org point to the user page for whatever we end up with (so it will still be http://hg.enzotools.org/yt/ to get to the yt repo, yt-doc for yt-doc, etc etc), but we also need a username. So if you go to BitBucket itself, rather than hg.e.o, you will see bitbucket.org/[username]/[project] .
In addition, if you are reading this, can you email me off list with your BitBucket username so that I can add you to the access control list? For now I think it will be better if we ease ourselves into the BitBucket workflow and avoid being too free with Pull Requests, and so I'd like to add people to the write list for whatever repo we end up with. You can get a BitBucket username simply by logging in with your Google username, if you like, or create a new one. I'm MatthewTurk, for what it's worth.
Thanks,
Matt _______________________________________________ Yt-dev mailing list Yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
+1.
yt_analysis
I think the underscore helps readability.
On Thu, Feb 24, 2011 at 9:33 AM, Rick Wagner
Hi Matt,
On Feb 24, 2011, at 9:28 AM, Matthew Turk wrote:
Hi everyone,
There've been lots of problems with the hg server on hg.enzotools.org. It's time to move from there to somewhere else.
I propose going to Bitbucket. This enables many things: forking, easier collaboration, pull reports, code review, and so on and so forth. Additionally, it will eliminate the timeouts that have plagued the hg.enzotools.org server. Bitbucket allows for domain redirection, so all the existing paths should continue to work, they will just be served by a different server.
Can I get [+-][01] on going to Bitbucket?
I'm trying to get us the 'yt' username, but haven't had luck yet. If the yt username is unavailable as of Sunday night, we'll need a backup name. I'd like to put this up for a vote:
yt_analysis ytanalysis yt_astro ytastro [other]
Can I get a vote on that, or any other suggestions?
My vote is 0, but I would ask if there is any benefit to having YT on Google Code, since that's where Enzo is. I don't know if there are any cross-project features that could be taken advantage of.
--Rick
_______________________________________________ Yt-dev mailing list Yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
On Thu, Feb 24, 2011 at 12:33 PM, Rick Wagner
Hi Matt,
On Feb 24, 2011, at 9:28 AM, Matthew Turk wrote:
Hi everyone,
There've been lots of problems with the hg server on hg.enzotools.org. It's time to move from there to somewhere else.
I propose going to Bitbucket. This enables many things: forking, easier collaboration, pull reports, code review, and so on and so forth. Additionally, it will eliminate the timeouts that have plagued the hg.enzotools.org server. Bitbucket allows for domain redirection, so all the existing paths should continue to work, they will just be served by a different server.
Can I get [+-][01] on going to Bitbucket?
I'm trying to get us the 'yt' username, but haven't had luck yet. If the yt username is unavailable as of Sunday night, we'll need a backup name. I'd like to put this up for a vote:
yt_analysis ytanalysis yt_astro ytastro [other]
Can I get a vote on that, or any other suggestions?
My vote is 0, but I would ask if there is any benefit to having YT on Google Code, since that's where Enzo is. I don't know if there are any cross-project features that could be taken advantage of.
I'm not sure that there are any benefits to GC. One additional issue is that we can't have Google Code handle any domain redirections, but Bitbucket will. BB is also much more baked-in in terms of support for DVCS, with things like pull requests, a clearer specification of clones/forks, and a bit better viewing of divergences between forks. Each project lives under a username, as well, so we can have many projects affiliated with whatever our final username is, not just the primary repo -- much like we do on hg.e.o now. I also think the user and developer communities behind Enzo and yt are different, and I think BB is better suited to our mode of operation. -Matt
--Rick
_______________________________________________ Yt-dev mailing list Yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
participants (4)
-
Brian O'Shea -
j s oishi -
Matthew Turk -
Rick Wagner