From: David G. <go...@py...> - 2014-01-23 15:25:40
|
There is definitely an advantage to a distributed VCS. Being able to commit, branch, roll back — experiment incrementally — on your local system, and only produce a patch or "pull request" once your changes are fully realized and polished, is a great tool. A distributed VCS allows developers to commit as often as they like without affecting other developers — it's "commit often" on steroids. I haven't used Git much in earnest, but I've had good results from Mercurial and Bazaar. I'm open to such a change, but I have no desire (let alone time) to implement the change myself. So my vote is +0. Maybe it's short-sighted but for me, the pain of making the switch to another VCS outweighs the benefit we'd see, at least in the short term. But I'm used to SVN and not doing much active development on Docutils these days. I don't see SVN as much of a pain point. The group of active developers and project "admins" has to make any such decision, but it requires a champion (or a group) who care enough to push through the group's inertia, convince the others, and implement the change. An absolute requirement, for me, is that such a change be complete. We can't lose any data or have to refer to the old system as an "archive". So all the SVN history, all branches, and the full sandbox need to be converted at the same time. My 2¢. -- David Goodger <http://python.net/~goodger> On 23 January 2014 02:21, engelbert gruber <eng...@gm...> wrote: > hello, > > subversion does the job, so why change it . > > considering the premize "release often" translated for developers "commit > often" , distributed vcs are an excuse. > (considering that people check their facebook every 5 minutes, what is the > problem with a centralized vcs) > > daily vcs usage with svn is svn update, svn diff, svn commit, git doubls > this so where is the advancement ? > > cheers e > > > > On 21 January 2014 23:41, Tony N <rai...@gm...> wrote: >> >> Greetings all, >> >> I wanted to get a status report on where things stand with VCS and a home >> for docutils. >> >> To begin, I have a few issues with source forge: >> >> I don't find the interface friendly. It's inconsistent. I am not up to >> date with it, because everyone else is using something else. >> >> The good things with source forge: >> >> 1. The good news is sourceforge may allow docutils to bind with >> advertisements, with DevShare, we can hook into setup.py and monetize >> docutils development. For more information, you can see >> http://sourceforge.net/blog/advertising-bundling-community-and-criticism/. >> >> 2. Also source forge benefits from being funded by Dice Holdings, Inc. You >> can read more about them at http://www.diceholdingsinc.com/. According to >> their front page, I see they announced as $50 million Stock Repurchase >> program. So while I'm ignorant of finance, we can get someone from numpy to >> confirm if fiscals are sound for 2014. SF could be around for a long time. >> >> 3. SVN is simple. Older versions have a folder in every sub-directory to >> maintain metadata. It has no upsides but it's cool when you get them tangled >> up. >> >> 4. The current work flow works. But, I don't think it's true. I think >> there are people who don't want to criticize, or people who just see >> docutils website and (sorry here) think it's a dead ghost town. That's my >> first impression when I see it. To people who used SF for a decade, this may >> not make sense, but this place honestly sucks. To other people who are newer >> to python, they may not be talking, but it scares them off or confuses them. >> >> I have issues with subversion. Its positive is simplicity. On the other >> hand, it lacks many of the conveniences git has. It's actually nice to have >> a decentralized system. The workflow for branches is nice. It's fast. In >> 2014, I think it's safe to say many developers know how to use it. >> >> Many python projects make their home on github. Flask, Werkzeug, Tornado, >> Requests. Cython. Pandas. Numpy. IPython. >> >> I have a preference for github and git. I like their interface for >> browsing source, pull requests, issues. I think github's pull requests and >> issue system is very contributor friendly. >> >> Even SQLAlchemy moved from bitbucket to github. Here is their rationale: >> http://www.sqlalchemy.org/blog/2013/05/25/sqlalchemy-migrated-to-git/ >> >> For the sake of articulating it, who makes the choice if docutils were to >> move to a new place? What is the current feeling around here? >> >> >> ------------------------------------------------------------------------------ >> CenturyLink Cloud: The Leader in Enterprise Cloud Services. >> Learn Why More Businesses Are Choosing CenturyLink Cloud For >> Critical Workloads, Development Environments & Everything In Between. >> Get a Quote or Start a Free Trial Today. >> >> http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk >> _______________________________________________ >> Docutils-develop mailing list >> Doc...@li... >> https://lists.sourceforge.net/lists/listinfo/docutils-develop >> >> Please use "Reply All" to reply to the list. >> > > > ------------------------------------------------------------------------------ > CenturyLink Cloud: The Leader in Enterprise Cloud Services. > Learn Why More Businesses Are Choosing CenturyLink Cloud For > Critical Workloads, Development Environments & Everything In Between. > Get a Quote or Start a Free Trial Today. > http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk > _______________________________________________ > Docutils-develop mailing list > Doc...@li... > https://lists.sourceforge.net/lists/listinfo/docutils-develop > > Please use "Reply All" to reply to the list. > |