[erlang-questions] Erlang 3000?
Thu Nov 20 16:43:34 CET 2008
As for code review, I like the dvcs way way:
create a branch for your bug or feature, and after you've fixed it
commit it to a code host (launchpad, bitbucket, github) and send an
email detailing your changes and ask for your branch to be merged.
I do like launchpad, there the code review can use the web frontend with
voting or the one-shot mini-mailing-list created around the merge. See
Launchpad also does bug, enhancement requests (blueprints) and question
tracking, has mailing lists and faq-building tools and has features for
team/role responsibilites. Main problem: speed of the web ui.
Launchpad can also handle a project staying with svn for the main
developers by importing the svn trunk once and then updating it every
few hours, see https://code.launchpad.net/~vcs-imports/drupal/main for
an example and
https://help.launchpad.net/VcsImports for documentation.
This way commiters who like to use bzr could it and launchpad for
changes and code review and once approved their changes to the main bzr
branch could be merged back to svn (see
So, if we're to build a community around erlang, a more complete service
like this seems the better solution to me than hosting our own code
Am Freitag, den 21.11.2008, 00:40 +1100 schrieb damien morton:
> Youre right about the license issue - and they seem to have a go-slow
> on adding new licenses, for example there are requests from 2007 for a
> "Public Domain" license which havent been implemented yet.
> I think, in principle, the goal should be to find and use existing
> tools where possible.
> I found, on google-code, some review software which seems to have
> similar features to google-code itself:
> http://www.review-board.org/users.php - unfortunately, it doesnt
> appear to support git.
> On Fri, Nov 21, 2008 at 12:22 AM, Vlad Dumitrescu <> wrote:
> > Hi,
> > On Thu, Nov 20, 2008 at 14:03, damien morton <> wrote:
> >> I guess the question is more about code review tools than SCM tools.
> >> I took a look at github, and they have a wiki feature, but not the
> >> detailed code review features of google-code.
> > One possible problem with google-code is that they only allow a
> > limited selection of OSS licenses, and the Erlang license isn't
> > amongst them.
> > regards,
> > Vlad
> > _______________________________________________
> > erlang-questions mailing list
> > http://www.erlang.org/mailman/listinfo/erlang-questions
> erlang-questions mailing list
More information about the erlang-questions