Re: [Python-markdown-discuss] the wiki

[Waylan L. <wa...@gm...>]

I may not be exactly right here, but my understanding is that
Mercurial, git and BZR are all 'distributed', while, of course, SVN is
not.  Mercurial and git, however, have a very different way of working
(or at least different commands/workflow/api) than SVN/CSV. BZR, while
more similar to Mercurial and git under the hood, offers commands and
workflow that SVN users will feel more comfortable with. I see it as a
nice middle ground. And if you want, you can use BZR in a remote
server type situation as well. The best of both worlds. I should
mention, this is all based upon very little time with  Mercurial and
git which I currently do not even have installed. However, I am
happily using both bzr and svn and don't really care which way we go.

On 11/7/07, Yuri Takhteyev <qar...@gm...> wrote:
> Well, unfortunately Trac installation turned out to be a nightmare due
> to zillion unsatisfiable dependencies.  I had to give up on it.
> Bazaar is still on the table, but I've exhausted my time quota for
> playing with random new software and will have to take a break for few
> weeks.
>
> I think I am convinced theoretically about advantages that Bazaar
> might offer over SVN, but it seems like there are a few other tools
> competing in that space, e.g. Mercurial, git, etc.  I've been
> wondering what the advantages and disadvantages are between those.
>
>   - yuri
>
> On Nov 7, 2007 11:49 AM, Ben Wilson <da...@gm...> wrote:
> > On 10/30/07, Yuri Takhteyev <qar...@gm...> wrote:
> > > I am curious if anyone else has opinions on that?
> > >
> > > First, on Bazaar vs. SVN.  I don't personally don't have much invested
> > > in SVN and don't care that much.  What I worry about is: will moving
> > > to Bazaar raise the bar for other people who want to check out?  In
> > > theory, it seems, Bazaar is specifically designed to make it easier
> > > for new people to join in.  On the other hand, I am wondering if
> > > people might be turned off by having to install a new VCS.
> > >
> > > Second, any comments on Roundup and Launchpad?  Lauchpad seems to have
> > > a nice community thing going, so if we want to switch to Bazaar this
> > > might be a nice option.
> >
> > For my two cents, I have played both with Bazaar and SVN. I like both.
> > If you are going to have multiple trusted developers, BZR is a great
> > option because it offers distribution of the repository. SVN is good
> > if you want to retain maximum control of the source code, IMO. BZR
> > works best with ASCII/ISO text; SVN handles binary a bit better. SVN
> > also has the advantage of being around for a while longer, but at the
> > expense of having the RCS/CVS mentality about repository management.
> >
> > Regarding tools, Trac is a nice Python tool. It has an integrated wiki
> > for all tickets, etc. The only weakness I perceive in Trac is the
> > inability to customize the wiki syntax. Otherwise, it would be great
> > to integrate Markdown with Trac and then be able to tout eating one's
> > own dog food. I'm presently stalled on development (curse of the
> > newborn and that whole family responsibility thing), but I was using
> > Trac with BZR.
> >
> > Having offered some feedback, I'm generally a lurker and know the
> > community will make the right choice. :-)
> >
> > --
> > Ben Wilson
> > "Words are the only thing which will last forever" Churchill
> >
>
>
>
> --
> Yuri Takhteyev
> Ph.D. Candidate, UC Berkeley School of Information
> http://takhteyev.org/, http://www.freewisdom.org/
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Python-markdown-discuss mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/python-markdown-discuss
>


-- 
----
Waylan Limberg
wa...@gm...