Search Results: "ag"

25 March 2007

Joachim Breitner: My Debian Project Leader Vote

The Debian project is having it s annual vote for the the post of the Project Leader, a mostly representative and medidative post. Here is my ballot:
[ 6 ] Choice 1: Wouter Verhelst
[ 7 ] Choice 2: Aigars Mahinovs
[ 5 ] Choice 3: Gustavo Franco
[ 1 ] Choice 4: Sam Hocevar
[ 3 ] Choice 5: Steve McIntyre
[ 2 ] Choice 6: Rapha l Hertzog
[ 4 ] Choice 7: Anthony Towns
[ 6 ] Choice 8: Simon Richter
[ 6 ] Choice 9: None Of The Above
I voted for Sam first because he has some fresh ideas and takes it not too serious after all, working on Debian should be fun. Next is Rapha l Herzog. He got the big plus of some good people on the prospective DPL board and I know he is doing some good stuff with regard to collaborative maintenance, e.g. in pkg-perl. I d then rank the current DPL and his Second in Charge equally. They didn t do anything particular bad (besides maybe the dunc-tank-experiment, but I m not blaming that failure entirely only on them), and continuity is normally a good thing. Well, just for fun, I ll give the advantage to Steve. Gustavo has a lot of ideas, and I m not sure how realistic they are. I ll still prefer him to nothing, so he is ranked next. I don t know enough about Simon and Wouter to really vote for or against them. Aigars plans though, despite knowing him personally, are not the right for a DPL post, so sorry, that puts him below NOTA.

Russell Coker: google-bank

Currently many people have Google advertising on their web sites, it may even be that a majority of the serious Internet users host Google advertising. Given that Google is already writing a cheque every month to many people, it wouldn't be difficult for them to change the amount in response to a funds transfer request. Depositing a cheque in a foreign currency can incurr $25 in bank fees (that's what the Commonwealth Bank of Australia charges me), this is a great impediment to international trade in small values. When Google already has an office in a country and writes cheques in the local currency it would be very easy to have that cheque include funds transfers too.

One significant advantage of Google payments would be the fact that Google doesn't write cheques for less than $100, so someone who earns $2 per month through Google adverts will be waiting a long time before they get a cheque - but if someone has an item that costs a small amount of money (EG an online service that costs a few dollars a month) then the user would be enticed to use it.

Currently many people don't place Google adverts because they believe that it would take them an unreasonably large amount of time to reach $100US. But if they could spend the money in small increments on other online services then it would be more enticing.

It seems to me that Google is the only organization that is both capable of running an International online small-payments system and which would be trusted by most people.

If you like this idea please post a comment.

24 March 2007

Amaya Rodrigo: Strawberries and champagne

Strawberries and champagne to celebrate his DD account.

Theodore Ts'o: Git and hg

John Goerzen recently posted about Git, Mercurial and Bzr that I found interesting, especially since I used to be in the hg camp, but have been gradually using git more and more, even to the point making minor improvements to the git documentation and writing the git mergetool, since being able to automatically fire up a graphical merge tool was one of the features which I missed from hg. So while I haven't yet converted the primary SCM repository for e2fsprogs to use git (yet), I've reached an opposite concolusion from John, and yet, I can't really argue with his observations.

The main reason why I've come out in favor of git is that I see its potential as being greater than hg, and so while it definitely has some ease-of-use and documentation shortcomings, in the long run I think it has "more legs" than hg, and with the release of git 1.5.0, it became clear that the git community was willing to work on these particular shortcomings, which is why I started working on it and making plans to migrate e2fsprogs to use git. The main reasons why I think git is more powerful is that not just that it supports lightweight branches inside a single repository (although I really do like that a lot since it makes it a lot easier to run multiple experiments in parallel and switch back and forth between them), but also because git is much more Unix-like; there are lots of tools that enable scripting for either new git extensions or for ad-hoc shell pipelines that you can't really easily do in hg without breaking into Python.

But git definitely does have shortcomings, and John is on the mark with most of them. Git's documentation is very poor. Part of the problem stems for tutorials that were written to work with older versions of git (don't try using anything older than git 1.5 if you are a git newbie; git 1.4.x is far more user-hostile) or were written for use with systems built on top of git 1.4.x, such as Cogito. (I don't recommend Cogito, since git 1.5 is significantly more usable, and I've always found Cogito to be more confusing that just using stack git.) The tutorials that are distributed with git 1.5 are much better, but they clear do need more work.

It is true that the many of the man pages in git are lacking, and John's criticism of the fact that many man pages do not list all of the options that they take, but rather refer to other man pages is on point and accurate. It has gotten better (take a look at the git-diff man page from the git 1.4.x days, and laugh or cry, depending on your point of view) but there is still much work to be done. In practice, the better way to use the git man pages is to skip past the options section, and take a look at the Examples section. This shows a number of ways that a particular command might be used, just as a Unix master might say, "Grasshoper, see how you can use awk to do all of these amazing things."

I do take issue with John's assertion that git's philosophy has been to make life easy for the central maintainer, and not to pay much attention to the needs of individual contributors. That may have been Linus's development priorities but with Junio having taking over maintenance, there have been a lot of improvements in git 1.5.0 to make life easier for people who are tracking remote repositories and making changes, in particular the git remote command.

The most interesting observation which John made was the non-intuitive semantics of git-format-patches, and I did find it interesting that one commenter posted a solution which made perfect sense given other git commands, and yet didn't work. Obviously the person who posted the comment didn't bother to try it first, probably because in most other places git is actually pretty consistent; but git-format-patch is one of the places where most painfully is not. I view this as a bug that should be fixed, and fortunately I think it can be fixed without breaking the git-format-patches is currently being used. (The problem is that it doesn't use the standard notation so it is more convenient in the common case of how it is normally used, where the end point is not specified and is always the the tip of the current branch. I believe we can avoid the UI surprise by making git-format-patch use the standard revision range parsing if parameter contains the ".." or "..." operators. I'll have to try to prepare a patch which does this and see whether it gets accepted.)

So basically git does have short-comings, yes, but people will come out in different places about which tools is best for them, and that's OK. Actually, I think the ultimate solution for this problem is to build a bidrectoinal hg/git gateway. There are tools that will export from hg to git, and vice versa, and they are actually pretty sophisticated. I don't think it should be that painful to create a tool that does incremental exports in both directions, maintaining state so that the right thing happens when a commit gets made on the git side, and gets exported into hg, or vice versa. Ultimately I think that's the best solution, since that way people can use whatever tool they want, and still contribute and development as first class citizens. This is the main reason why I've held off on converting e2fsprogs to git (although I have made some private test repositories which I'll use to take advantage of git's superior annotation and query/log utilities); I don't want to make a git repository of e2fsprogs public until I'm sure that a bidrectional gateway tool won't require me to make any changes that affect the commit-id's, since that would invalidate any work that people have done that was based on a clone of the coverted git repository.

I have a rough design for how to do the bidirectional gateway, but the issue is finding time to implement it. Anyone with free time looking for a project? If so, contact me. I probably should have written this up as a potential Google Summer of Code project, but it's too late for this year. Oh, well.

Neil Williams: Emdebian repository layout

OK, after a long time and a few reshuffles, emdebian has a 'logical' SVN repository layout with a clear division between current and superceded code, clear module separation and updated documentation.
[ wiki docs ]
[ website docs ]
[ repository browser ]

To check out the current code:
svn co http://buildd.emdebian.org/repos/current/

A full check out of even just the current code can easily be over 20Mb and is likely to increase as more packages are emdebianised. See the list of modules available.

Adrian von Bidder: The DPL Vote

Whee, I actually managed to vote in the DPL race. Out of 5 votes I sent, 3 were rejected and 2 where ack'ed (theser were 5 different variants of MUA's, gpg usage and character set stuff.) Now I just hope that I actually voted the way I intended. (for those who are interested: my ballot is roughly the one I announced.)

Russell Coker: images for a web site

When I first started putting pictures on my web site I used to delete the originals (at the time I only had a 3.2G hard drive in my main machine and used CDs for backup so I didn't feel inclined to waste too much space). The problem is that I optimised the images for viewing on displays of the day (when 1024x768 was high resolution and I tried to get pictures down to 800x600 or less whenever possible). Also the program I was using at the time for scaling the images didn't do it nearly as well as the Gimp does now.

Now when putting pictures on my web site I keep the original JPEG's in a safe place so that if there are future changes to common display technology, net connection speed (particularly the speed of my server) or of technology for scaling and compressing images then I can re-do them to get a better result.

When saving images with Gimp I enable "Advanced Options", this allows me to set a floating-point DCT method this saves about 400 bytes on disk and apparently gives a better image quality too - it's not noticably slow on a Pentium-M 1.7GHz so they should probably make it the default. The next "Advanced" option to change is to turn off "Save EXIF data" (saves 1.9K) and "Save thumbnail" (can save almost 5K depending on the image).

The next thing to do when saving a JPEG is to enable the "Show Preview in image window" setting. This allows you to adjust the image quality while seeing the resulting image as well as the size, so you can determine which combination of file size and image quality is best for you. This is much easier than saving
a file and then running an image viewing program to inspect it!

As an aside, it would be convenient if the Gimp would reposition it's "Save as" dialogue to not occlude the image window and would enable the preview option by default on machines with reasonably fast CPUs.

Erich Schubert: Please, think of the animals formerly known as kittens...

(Title stolen from Holger Levsen) Whenever I see this image [mozilla open Standards], I want to make a spoof of it titled: Every time you make an Ajax app, god kills a firefox. But I would certainly be violating Mozilla trademarks by doing so (their artwork, logos and trademarks such as "firefox" are not OpenSource). Anyway: AJAX is a hackaround, in particular it is not an open standard. Please use it only where it's really needed. Granted, there is worse (e.g. Flash; prepare for incompability hell now that the first opensource plugin can playback youtube videos - as you might be aware, many Linux distributions can not ship Adobe Flash, so they'll likely start shipping this plugin as soon as it's somewhat working sufficiently; or ActiveX which only works with MSIE...), but that's not really a good excuse for this abuse of Javascript that is called AJAX. On a side note, since I already mentioned flash - I can really recommend the Flashblock mozilla extension. A must have: you can view any flash if you need to by just clicking on it, but they won't be loaded automatically anymore. So you can easily access youtube (just one extra click!), but won't be bothered by flash ads and such stuff. Oh, and Adobe. They're probably the biggest blocker for a widespread Linux adoption judging by this article [computerworld.com], which is already very positive on Linux ("Unlike many of the applications included on new Windows systems, these don't seem to come with annoying self-launching advertisements, such as the irony-challenged Trend Micro Anti-Spyware pop-up upgrade pleas that plagued my HP system at home."): maybe his biggest issue is that he couldn't just run his Adobe Photoshop Elements on Linux. Of course there are application trying to offer the same functionality; starting with Gimp, digiKam and Krita (and I'm not sure he tried Krita and digiKam as well; they are probably more similar to Adobes product), but I can understand his wish to be able to continue using the same applications. (My personal recommendation: start using Opensource applications on Windows, e.g. Firefox, Thunderbird, Inkscape (great vector graphics program!) (and it's using open standards: SVG), Gaim (multi-protocol instant messenger and tons of others. They're free, so even if you don't use them every day, you didn't waste money on them... and if you happen to like them: you can be sure that they'll be working the same if you do the switch to Linux at some point in the future. Be prepared for when Microsoft says you PC is too old.

23 March 2007

Lars Wirzenius: Random hacks: Finnish .ics files

I abandoned paper calendars in 1997. For a few years I used various Palm devices, then Evolution. For the most part, this has worked fine. One of the drawbacks is that I have not had any info in my calendar about official holidays in Finland. That would be useful so that I would know when other people are going to be responding to e-mail slowly, and get annoyed if I call them on business. Evolution can deal with several calendars at the same time, and can import calendar files in various formats. A couple of years ago I found an iCal file with Finnish holidays, and imported that to Evolution, but it's out of date by now. This week I decided to look for a new one, but before I did, Droidy, the fastest interface to search engines, found one for me. Unfortunately, it was severly lacking, and did not even include Midsummer Eve, the biggest summer festivity in Finland. I then decided to make my own. I skimmed the web pages of The Almanac Office at University of Helsinki. They used to have the monopoly on making calendars in Finland (and what a silly anachronism that was), and they still have the copyright on name days, but that stuff doesn't interest me. The list of holidays is uncopyrightable, and that's the info I extracted from their pages. I also looked at the list of times when food stores are allowed to be open. That's actually more important to me than holidays. I ended up making two .ics files: aukiolot2007.ics for opening hours, and suomi2007.ics for the holidays. They're probably riddled with errors: if you find any, e-mail me and I'll fix and update. I hope they're of some use for someone. (I realize that someone is going to tell me about a complete and officially supported .ics file with all the above data as a response to this log entry. Good.)

Martin F. Krafft: Epiphany and vertical tabs

Firefox is becoming totally unusable, and even though some extensions I need/want do not exist for Epiphany (like Web Developer and Firebug, Live HTTP headers, Stealther, UrlParams, Cookie Button, and plenty of the features of Tab Mix Plus (among others)). The single biggest obstacle keeping me from switching are vertical tabs. I usually have a browser window for each task I work on, and on average, I'll have 15 tabs open in it. With Firefox, I hacked the UI to make the tabs line up vertically on the left side of the window. That way, I can easily keep track of 30 open tabs, and I gain vertical space for the payload at the expense of window width. Dear lazyweb: do you know of a way to move the Epiphany tab bar to the left of the window and have it fill with tabs top-down? Please let me know! NP: 65daysofstatic / The Fall of Math Update: Lazyweb, you're aweseome! Rodney Jokerst referred me to his Epiphany extension, which does just what I want. Update: due to popular demand, here's the Firefox hack I use in chrome/userChrome.css:
#content > tabbox  
  -moz-box-orient: horizontal;
 
.tabbrowser-strip  
  -moz-box-orient: vertical;
  /* note: you can set this to -moz-scrollbars-vertical instead,
  but then the scrollbar will *always* be visible. this way
  there is never a scrollbar, so it behaves like the tab bar
  normally does */
  overflow: -moz-scrollbars-none;
 
.tabbrowser-tabs  
  -moz-box-orient: horizontal;
  /* min-width: 50ex; */ /* >1680 pixels screens */
  /* min-width: 40ex; */ /* =1680,1600 pixels screens */
  /* min-width: 35ex; */ /* =1440 pixels screens */
  /* min-width: 30ex; */ /* <1440 pixels screens */
  min-width: 20ex; /* 1280 pixels screens */
  /* min-width: 17ex; */ /* this is almost the minimum to go down to on small screens */
  -moz-box-align: start;
 
/* Background for tabbrowser strip */
tabs.tabbrowser-tabs  
  background-color: grey !important;
 
.tabbrowser-tabs > stack > vbox > hbox > hbox  
  -moz-box-orient: vertical;
  -moz-box-align: stretch;
 
.tabbrowser-tabs > stack > vbox > hbox > hbox > tab  
  -moz-box-align: start;
  -moz-box-orient: horizontal;
 
/* to put the tabs on the right un-comment this line
  (not needed if using Tab Mix Plus) */
#content > tabbox  -moz-box-direction: reverse; 
Even though the origins of this code are IRC channels and other forms of random pasting back and forth, of which I was a part, I took the above from this page.

Erich Schubert: Google Summer of Code

Applications are still open until March 26th. Note: the following is my personal opinion; I'm not the coordinator of the Debian GSoC project, and others might disagree. Debian has received a couple of applications, but there were rather few among them I found really convincing. :-( What I usually dislike in applications: So if your application is really Debian-related, invest a few hours in writing the application and your chances are pretty good at being accepted! Of course Debian could be an Umbrella for e.g. another network configuration GUI, a tool to configure traffic shaping etc.; however I don't think that should be our focus. In fact, Google itself could mentor these topics maybe as good as we can. So please don't just submit a proposal to us because you happen to be a Debian user, or submit it to all mentoring organizations. Instead try to find an appropriate mentoring organization. (On a side note, the mentoring organization is supposed to provide you with a mentor which can actually help you on the topic). Debian is a good choice when it comes to integrating software, software management, system administration and such. Thats what we do: collect existing software and try to make it work together as good as possible. And build infrastructure and tools to make this task easier. This of course touches e.g. porting to different architectures and writing new administration frontends, however we try to avoid reinventing the wheel. One of the suggested topics, where I'm really surprised to not having seen a proposal yet is CRMI; which matches what I sometimes call a "per package wiki for metadata". Or a Debtags related project. Or a SELinux project. These are both pretty interesting technologies, which offer substantial benefits when actually used. When properly integrated in the distribution.

Holger Levsen: little details again

Marc, fwiw imo LCD-displays and RAM-memory are much more fun :-) ymmv.

Gustavo Franco: Us and Them

There's a lot going on, since we're getting closer to the International Free Software Forum 8.0 that will be held in Porto Alegre, Brazil. Sacix new website is online at: www.sacix.org.br (sorry Portuguese only yet), and we've received a impressive amount of new subscribers to the related mailing lists.

Paulo and I managed to add usbfloppy support into ltspfs that I've forward to Vagrant from pkg-ltsp in Debian, Oliver (ubuntu/edubuntu) and upstream. It was just a detail for many but a huge step for us, considering that more than 100.000 end users are using their floppies into a usbfloppy drive so we really needed that in time for Sacix next release (Sagui).

Quick notes:
* My new car has a week of life
* Developers, please vote for DPL!

I'm now warming up for Roger Waters gig. See you!

Alastair McKinstry: Preparing for Daylight Savings Time

While computers mostly handle the Daylight Savings Time changeover automatically, sometimes work is required. In our case at ICHEC, arranging for some jobs to run at set times, means changing the scheduler at the changeover. We use PBS and Maui to schedule what jobs run when on our cluster. Mostly jobs get run according to priorities: the scheduler (software) decides which what the priority jobs are and when; it collects free nodes until it has sufficient free CPUs to run the jobs at hand. It can do backfilling: when it's e.g. trying to run a large 128 node job but has only 10 nodes free, it will reserve nodes as they become free until it has all the resources needed to run the job. If by looking at the remaining time left on running jobs it realises that it won't get nodes free for the large job for say 2 hours, it can run small jobs with runtimes of less than two hours on the nodes it had reserved. Clever. The fun issue comes when you need to set reservations: say you need to run a job at 2am every day on 32 nodes, as we do: the scheduler needs to plan accordingly. The scheduler needs to really have 32 nodes free at that time. Thats 2am local time, of course: but next Sunday, at 2am, the clock changes... So, working out the consequences, and preparing for the change, I sympathise with our American friends who've moved three weeks early to save energy. Thus causing lots of midnight oil to be burned around the world by sysadmins and programmers updating software. Hmmm. Note to Self: When Posting a blog entry asking for help on getting blog comments to work with openid, try leaving the comments setup on the blog working, so people can leave replies. Fixed now.

Evan Prodromou: 2 Germinal CCXV

It's Germinal, finally! Out of the months with the hatted o's. That's nice on my URLs. We're leaving Surfside today on our way to Las Vegas for the IASummit. It should be pretty fun -- a good way to wind up our trip to the USA for this spring. We all took a dip in the Gulf this morning, and I'm pretty sad we're going already. I've grown pretty fond of the Gulf Coast (Texas) and we're trying to figure out a way to spend more time down here. We've got a late afternoon flight, but we have to be gone by noon, so we're going to try to look around in Houston a couple of hours before we leave. I'm a little bummed that the Orange Show is only open on weekends this time of year. It's the main thing I want to see in town. tags:

Holger Levsen: Please think of the animals formerly known as kittens

Pretty please!

Wouter Verhelst: Crap

Rule #1: don't do "svn commit" in a working directory of my blog when there are some unfinished and ill-worded blog posts still in that directory. Or, in other words, my previous post shouldn't have gone out yet, it wasn't ready; it was way too convoluted and thus failed to bring across the intended message. Revisiting this post before posting it, is something that's been on my list of things to do for a fair while, but it just never happened. I guess the cat's out of the bag now, so I might as well clarify it here and now. Let me make clear that I did not mean to say that people should just be Cc'ing everyone, whether or not they're on the list, in violation of the stated list policy. Instead, what I meant to say is that I do not believe that a policy on whether or not you should send Cc's to people is the right solution to this kind of thing. Instead, I think we should have our mail clients support this kind of thing by themselves. There are really two types of "reply" in a mail client: one is a "public" reply, where everyone who read the original mail can also read any follow-ups, and the other is a "private" reply, where you only send your reply to the person who sent the mail you're replying to in the first place. There should not be a difference on the UI level between "reply to the list" or "reply to each and every email address that's in the 'To', 'Cc' and 'From' headers"; MUA software should be smart enough to notice when you're mailing to a mailinglist, and pick the right option out of the latter two all by itself. And if someone really wants a private copy of the mail, adding a header to do that is already possible today. With that in place, there shouldn't be a need for a code of conduct to state that you should not randomly Cc people. QED. Then again, obviously mailinglists suck and usenet is much better. But that's another discussion for another time.

Wouter Verhelst: Etch and glibc

Thomas mentions that Etch will release with glibc 2.3 rather than glibc 2.4, and wonders why that is. There are two simple reasons for this:
  1. AIUI, glibc 2.4 drops support for non-NPTL kernels (i.e., 2.4 and earlier Linux kernels). Since sarge's default kernel was still a 2.4-based kernel, upgrading to a glibc 2.4 will immediately break everything on your system, since at that point your libc suddenly refuses to cooperate with your kernel. Not providing an upgrade path for users who run a supported kernel of our previous release is not an option.
  2. Etch will have official support for 11 architectures: i486 and later intel-compatibles, SPARC, Alpha, PowerPC, ARM, big- and little-endian MIPS, PARISC, ia64, S/390 and AMD64. If we want to migrate to glibc 2.4 or later and still release, then it has to work on all those architectures. Since NPTL requires some architecture-specific support and since that architecture-specific support is not available for some of our current architectures, this is not the case (also see the above). It may be possible that Debian "lenny" will drop some architectures because the most recent version of glibc still does not support them, but ultimately that decision will be up to the release managers.
So, while I'll agree that it kindof sucks that Debian will release with a somewhat outdated version of glibc, it's not as if there isn't a valid reason.

Martin F. Krafft: Managing SSH's known_hosts database

Yoe wonders how to manage SSH's known_hosts database. Here is how I do it: In ~/.ssh/config:
Host *
  StrictHostKeyChecking yes
  CheckHostIP yes
  [...]
[...]
Host wall   wall.madduck.net
  CheckHostIP no
  [...]
This causes SSH to refuse connections unless the host fingerprint is already in the known_hosts database. For the host wall, which has a dynamic IP, I don't bother checking the IP every time I connect. To be able to connect to new hosts, or to hosts that I'll only use once or twice, I make use of two shell functions:
sshtmp ()  
  ssh -o "StrictHostKeyChecking no" -o "UserKnownHostsFile /dev/null" "$@"
 
sshnew ()  
  ssh -o "StrictHostKeyChecking no" "$@"
 
The first of the two effectively disables the known_hosts database and lets me connect to any host. The second function, sshnew, I use to connect to new hosts, which I would like to add to the known_hosts database. This works alright. I would still much more prefer to be able to use something akin to ~/.ssh/known_hosts.d/ or another method that makes it easier to keep known_hosts synchronised across various hosts. NP: Emerson, Lake & Palmer / Tarkus

John Goerzen: bzr, again

I've talked a lot lately about different VCSs.

I got some interesting comments in reply to my most recent post. One person took issue with my complaint that nobody really understood how to specify a revision to git format-patch, and proceeded to issue an incorrect suggestion. And a couple of people complained about my comments about bzr, which generally came down to the released version of bzr didn't have anything compelling and also didn't support tags.

So I went into #bzr, asked them what bzr has that git, Mercurial, and darcs don't. And gave bzr the benefit of the doubt that 0.15 will be out soon and will be stable. What I got back were these general items:

  1. Renaming of directories (not in hg, git)
  2. 2-way sync with Subversion (not in hg, darcs)
  3. Checkouts (not in any others by default)
  4. No server-side push requirement


Let's look at these in more detail.

1. Renaming of directories

All of them can rename files and (excepting git) completely accurately track back the file's history. But consider this: if person A commits a change to branch A that adds a file, and person B then renames the directory that the file is in on his branch, will a merge cause person A's file to appear in the new directory name? In darcs and bzr, yes. In Mercurial and git, no.

So yes, this is a nice thing. But I have never actually had this situation crop up in practice, and even if it did, could be trivially remedied. I would say that for me, I don't really care.

[Update: Current stable releases of Mercurial can do this too. I'm not quite sure how, but it does work. So git is the only one that can't do that.]

2. 2-way sync with Subversion

This is a really nice feature and is present in both git and bzr. I haven't tested it either place, but if it works as advertised -- and properly supports tracking multiple related svn branches and merges -- would be slick. That was enough to make me consider using git, but in retrospect, I so rarely interact with people using svn that it is not that big a deal to me.

Still, for those that have to work with svn users, this feature in bzr and git could be a big one.

Better yet would be to get all those svn holdouts over to DVCS.

3. Checkouts

A bzr checkout is basically a way to make local commits be pushed to the remote repo immediately, as with svn. This is of no utility to me, though I can see some may have a use for it. But it can be done with hg hooks and probably approximated with scripting in others.

4. No server-side process necessary for pushing repos

bzr has built-in support to push to a server that has sftp only, and doesn't require a copy of itself on the server. While I believe that none of the other three have that, it is possible to rsync (and probably ftp) darcs and Mercurial repos to a server in a safe fashion by moving repo files in a defined order. Probably also possible with git. All four can pull repos using nothing but regular HTTP.

What bzr still doesn't have

Integrated patch emailing. The big thing is that it has no built-in emailing of patches support. darcs is extremely strong in this area, followed by hg, and git is probably third. "darcs send" is all it takes to have darcs look at the remote repo, figure out what you have that they don't, and e-mail a bundle of changesets to them. I posted an extension and later a patchset that does all this for Mercurial except for automatically figuring out what default email address to do (that'll come in a few days, I think). One feature Mercurial has had for awhile that Darcs hasn't is sending multiple textual diffs as a thread, with one message per changeset. bzr doesn't have any support for emailing patches yet, which is disappointing. Because of the strong support for this in darcs and Mercurial, people running those systems feel less of a need to publish their repos.

[Update: There is a plugin for bzr that seems to address some of this. I haven't tested it, and it's not in bzr core (so doesn't quite meet my very friendly for a newbie requirement), but this does exist, though apparently not as advanced as Mercurial]

Performance. Supposedly 0.15 is supposed to be better on this, but even if bzr achieves the claimed doubling of performance, most benchmarks I have seen would rate it as still being significantly behind git and Mercurial, though it may overtake darcs in some tests.

Extensive documentation. I would say that bzr's docs are better in some ways than git's (its tutorials especially), but lack depth. If you want to know some detail about how the repository works on-disk, it's not really documented. Darcs still has David's excellent manual, and Mercurial has the hg book which is still great as well.

Merging not as advanced. darcs is pretty obviously way on top here, but of the others, Mercurial does a pretty good job with its automatic handling of renames and automatic resolving of different branches that commit the same change (even if that same change is a rename, or an add of the same content). bzr can't resolve as much automatically.

Summary

Well, I'll say that bzr still doesn't look compelling enough for my use cases to use, and the lack of an easy-for-a-newbie-to-use automated email submission feature is a pretty big disappointment. Though I did appreciate the time those on #bzr spent with me, and if I needed to sync with svn users frequently, I'd probably choose bzr over git.

For now, I'm happy with sticking with darcs for my code and hg for my Debian work.

But all four communities are aggressively working on their weaknesses, and this landscape may look very different in a year.

Next.

Previous.