I'm using everything Launchpad, including Bazaar, for my project. That said,
I'm still learning DVCS and Bazaar, but I like all the support tools that
Launchpad provides, and that they're all in one place, and that there's
money behind development.

On Sat, Nov 1, 2008 at 12:15 PM, Yarko T <[EMAIL PROTECTED]> wrote:

> DVCS is nice - and lightweight on a potential contributor's local machine..
>
> Could we keep it python-ish, so that contributing platforms don't get in
> the way?
> The nice thing about SVN is is seems to run everywhere....
>
> mercurial too (but you need to compile "C" code if not);
> bazaar is all python;
>
> I'd vote for one of the later two (hg or bzr).  In fact, I've found a "most
> of what I need" bazaar site (launchpad), but not found a hosting place
> similarly configured for hg, so would be curious to hear what other people
> are using for hg source hosting, that includes (at least) a wiki and issue
> tracker.
>
> Thanks,
> Yarko
>
>
> On Sat, Nov 1, 2008 at 11:16 AM, Rok Garbas <[EMAIL PROTECTED]> wrote:
>
>>
>> On Sat, Nov 1, 2008 at 4:14 PM, Georg Brandl <[EMAIL PROTECTED]> wrote:
>> > So, I'm asking all of you: what would you prefer -- SVN at Google,
>> > with very liberal commit policies, or Mercurial?
>>
>> i'm not (yet) a contributor, but i'm working extensivly with sphinx
>> last month and will continue in the future. it would be nice to see
>> DVCS. could git be possible option?
>> (http://git.or.cz/gitwiki/GitBenchmarks)
>>
>>
>> (my intention is not to get into "best dvcs war" here, i'm just proposing
>> git)
>>
>> --
>> Rok Garbas
>> http://sharbas.blogspot.com/
>>
>>
>>
>
> >
>


-- 
Bruce Eckel

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"sphinx-dev" group.
To post to this group, send email to sphinx-dev@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/sphinx-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to