Repositories moved to bitbucket
Ian Bicking
FormEncode, Paste*, WebOb, and other libraries, I have moved
everything to bitbucket. You can see the repositories here:
http://bitbucket.org/ianb/
Or, more specifically FormEncode
(http://bitbucket.org/ianb/formencode/) and a bunch of Paste-related
libraries:
http://bitbucket.org/ianb/paste/
http://bitbucket.org/ianb/pastedeploy/
http://bitbucket.org/ianb/pastescript/
http://bitbucket.org/ianb/webob/
http://bitbucket.org/ianb/webtest/
http://bitbucket.org/ianb/scripttest/
http://bitbucket.org/ianb/tempita/
http://bitbucket.org/ianb/wsgiproxy/
I'd like to use these repositories somewhat similarly to how
Subversion is used: most development should happen in these specific
repositories. If you have (and use) commit to one of these projects
in Subversion, I'd like to give you write access to the main
repository. If that's the case, PLEASE EMAIL ME (off list) with your
bitbucket username and the projects you'd like access to. I'm
generally pretty open to giving commit access to people who have been
around and I know (even if only online), since I've found most people
to be appropriately self-limiting (e.g., anyone should feel
comfortable fixing a typo in a docstring, but API changes require
discussion).
If you want to do something experimental, or something you might do in
a branch in Subversion, I'd prefer these be forks. Mercurial branches
are appropriate for maintenance branches (e.g., bug fixes on a stable
branch), but otherwise I don't think they are as convenient as a fork,
and they are more error-prone.
I have not definitively decided what to do with issue trackers. There
is an issue tracker on bitbucket, and it is functional though not
really anything special (though it requires very little maintenance).
FormEncode uses SourceForge, while the others all use a single trac
instance. I don't want to split issues between multiple systems, so
I'd only want to switch to bitbucket if existing (open) tickets were
moved over. So... mostly I'm just throwing this out there as an
option, if someone is up to doing the work to migrate tickets. If
someone was willing to setup a rig to do distributed issue tracking,
that would also be of interest to me (at least to experiment with).
--
Ian Bicking | http://blog.ianbicking.org | http://topplabs.org/civichacker
Jon Nelson
>
> In an effort to make it easier to contribute and manage patches to
> FormEncode, Paste*, WebOb, and other libraries, I have moved
> everything to bitbucket. You can see the repositories here:
> http://bitbucket.org/ianb/
>
> Or, more specifically FormEncode
> (http://bitbucket.org/ianb/formencode/) and a bunch of Paste-related
> libraries:
>
> http://bitbucket.org/ianb/paste/
> http://bitbucket.org/ianb/pastedeploy/
> http://bitbucket.org/ianb/pastescript/
> http://bitbucket.org/ianb/webob/
> http://bitbucket.org/ianb/webtest/
> http://bitbucket.org/ianb/scripttest/
> http://bitbucket.org/ianb/tempita/
> http://bitbucket.org/ianb/wsgiproxy/
I must admit to being a little bummed about this move.
While I'm the farthest thing from a fan of subversion, at least I
could make use of git-svn to use git with the (old) svn repos. The
reality is, I suspect, some people use svn but lots of people use
something that can talk to svn. I'm not aware of similar hg <-> git
software, and for whatever reason, I can't make hg do what I want.
Maybe I need to spend more quality time with it.
Since this is already done, please consider this a minor complaint and
nothing more.
--
Jon
Paul Davis
---------- Forwarded message ----------
From: Paul Davis <paul.jos...@gmail.com>
Date: Fri, Feb 19, 2010 at 3:39 PM
Subject: Re: [Paste] Repositories moved to bitbucket
To: Jon Nelson <jne...@jamponi.net>
There's an hg-git plugin that would allow you to mirror them directly
to a git repository.
HTH,
Paul Davis
> --
> Jon
>
> --
> You received this message because you are subscribed to the Google Groups "Paste Users" group.
> To post to this group, send email to paste...@googlegroups.com.
> To unsubscribe from this group, send email to paste-users...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/paste-users?hl=en.
>
>
Jon Nelson
> I fail again at no reply-to.
If anybody is at PyCon, I'd love to get a quick how-to-make-$this
(where $this is hg-git or hg) work tutorial.
--
Jon
Alice Bevan-McGregor
>> In an effort to make it easier to contribute and manage patches to FormEncode, Paste*, WebOb, and other libraries, I have moved everything to bitbucket. You can see the repositories here: http://bitbucket.org/ianb/
:(
> I must admit to being a little bummed about this move.
I agree. With Hg, I’m limited to using Hg to access the repository. I don’t use Hg in my day-to-day life, so this is just another alien SCM system for me to learn. I advocate Git/Github due to the fact that if people want to use Hg, they can. It’s more… compatible, shall I say?
> While I'm the farthest thing from a fan of subversion, at least I could make use of git-svn to use git with the (old) svn repos.
> The reality is, I suspect, some people use svn but lots of people use something that can talk to svn. I'm not aware of similar hg <-> git software, and for whatever reason, I can't make hg do what I want. Maybe I need to spend more quality time with it.
Same situation here, though I have heard of Hg users making use of Git repositories fairly easily. Just not the other way around. :/
> Since this is already done, please consider this a minor complaint and nothing more.
Same. I’ll get used to it. ;) Time to update references…
— Alice.
Mike Orr
http://wiki.pylonshq.com/display/pylonscookbook/Mercurial+for+Subversion+Users
Mercurial for Subversion Users
--
Mike Orr <slugg...@gmail.com>