On Oct 10, 7:32 am, Rudy Lattae <
rudylat...@gmail.com> wrote:
> I'll support the move to any of launchpad (lp) or github. I've used
> them both through bzr and git and they are robust. Also since they are
> web fronts for dvcs'es the workflow is more intuitive -- i.e. make
> local commits as you go along and push "bundles" of changes up to the
> server. I like launchpad's project management tools (code, bugs,
> blueprints, releases) more than github's. Also lp has great group (and
> sub group) management and sharing across projects. However, I have to
> agree with Emile about lp's cumbersome UI. They have not yet settled
> on a particular look and feel yet and that makes it more difficult to
> "get used to it". I like github's clean layout.
>
> They both have excellent code review/merge tracking capabilities and
> so far I see less spam on the projects on lp and github (even
> gitorious) than on google code.
I've spent last week trying to like git, but I've given up. There's a
few concepts I like about git, and I realize it's ahead of the others
in functionality and mindshare, but it has a few warts that I
currently just can't tolerate, so git is out. I've tried Mercurial for
a bit, and it's working out for me; from what I've read, bzr is pretty
similar in concept. Which leaves us with launchpad for bzr, or
googlecode, kenai or bitbucket for hg. I know sourceforge offers hg,
but the new sf ui is ridiculously cluttered and ugly, so that's out.
Googlecode has the pro that it doesn't require much change, but I
would need to have (co-) control of the mailinglists; I've mailed the
owner (no idea who he or she is), if that works out I'll probably keep
stuff here, and set up a google group where issue tracker changes get
mailed to. If I can't get co-ownership, and given the fact that I'm
currently the only active project member, googlecode is out. Also, I
need to find a solution for the problem that stuff I mail to
googlegroups gets bounced, I need to use the web-ui for everything. If
I can't fix that, googlecode is out.
I have no experience with bitbucket or kenai. Kenai offers jira, which
I've heard very good things about.
> Since I'm not an actual contributor (code-wise) to the project, I'm
> not really sure how much of an effort the migration itself would need.
> i.e. moving the discussion threads, wiki pages etc.
The discussion threads would not be migrated. Wiki pages are easy,
since they live in subversion. Moving the repo over is easy (done it
before at work).
> Also your group
> members would have to setup new accounts
That's true, and it's a pity. There's not too many currently, however,
so I don't consider that to be a blocking issue.
> and contributors would have
> to create secure keys to sign code commits actually that's a major
> plus in terms of trusting external code contributions.
Realistically, I'm the only active comitter right now. I'd love for
that to change, but I don't see that happening anytime soon.
Emile