Search Results: "ag"

10 April 2007

Russell Coker: what is a BOF?

BOF stands for Birds Of a Feather, it's an informal session run at a conference usually without any formal approval by the people who run the conference.

Often conferences have a white-board, wiki, or other place where conference delegates can leave notes for any reason. It is used for many purposes including arranging BOFs. To arrange a BOF you will usually write the title for the BOF and the name of the convenor (usually yourself if it's your idea) and leave a space for interested people to sign their names. Even though there is usually no formal involvement of the conference organizers they will generally reserve some time for BOFs. Depending on the expected interest they will usually offer one or two slots of either 45 minutes or one hour. They will also often assist in allocating BOFs to rooms. But none of this is needed. All that you need to do is find a notice-board, state your intention to have a BOF at a time when not much else is happening and play it by ear!

My observation is that about half the ideas for BOFs actually happen, the rest don't get enough interest. This is OK, one of the reasons for a BOF is to have a discussion about an area of technology that has an unknown level of interest. If no-one is interested then you offer the same thing the next year. If only a few people are interested then you discuss it over dinner. But sometimes you get 30+ people, you never know what to expect as many people don't sign up - or have their first choice canceled and attend the next on the list!

To run a BOF you firstly need some level of expert knowledge in the field. I believe that the best plan is for a BOF to be a panel discussion where you have a significant portion of the people in the audience (between 5 and 15 people) speaking their opinions on the topic and the convener moderating the discussion. If things work in an ideal manner then the convener will merely be one member of the panel. However it's generally expected that the person running the BOF can give an improvised lecture on the topic in case things don't happen in an ideal manner. It's also expected that the convener will have an agenda for a discussion drawn up so that if the panel method occurs they can ask a series of questions for members of the BOF to answer. My experience is that 8 simple questions will cover most of an hour.

One requirement for convening a BOF is that you be confident in speaking to an audience of unknown size, knowledge, and temperament. Although I haven't seen it done it would be possible to have two people acting as joint conveners of a BOF. One person with the confidence to handle the audience and manage the agenda and another with the technical skills needed to speak authoritatively on the topic.

Some of the BOFs I have attended have had casual discussions, some have had heated arguments, and some ended up as lectures with the convener just talking about the topic. Each of these outcomes can work in terms of entertaining and educating the delegates.

But don't feel afraid, one of the advantages of a BOF is that it's a very casual affair, not only because of the nature of the event but also because it usually happens at the end of a long conference day. People will want to relax not have a high-intensity lecture. One problem that you can have when giving a formal lecture to an audience is nervous problems such as hyper-ventilating. This has happened to me before and it was really difficult to recover while continuing the lecture. If that happens during a BOF then you can just throw a question to the audience such as "could everyone in the room please give their opinion on X", that will give you time for your nerves to recover while also allowing the audience to get to know each other a bit - it's probably best to have at least one such question on your agenda in case it's needed.

Note that the above is my personal opinion based on my own experience. I'm sure that lots of other people will disagree with me and write blog posts saying so. ;)

The facts which I expect no-one to dispute are:

Peter Makholm: The iBook story

I took some days off-line so the iBook story hasn’t progressed very much. On the other hand I’ve spent some time with my family and finaly finished Neil Stephenson’s Quicksilver. Sound Had some problems with the internal soundcard. I’m not quite sure what the porblem was, but the right module is snd_powermac and not anything like snd_aoa. Probaly did something else wrong along the way too. The fun part would be playing music throug AirTunes. raop-play claims to solve this problem. They got debian packages for i386 and a nice debian/ in the source tar-ball. The build-deps is missing fluid and libglib2.0-dev but other than that it builds nicely — but no sound… Nearly giving up I looked at the alsapcm module not part of the debian package, just to see how it worked in theory. And suddenly I could play music with mplayer -ao alsa:device=hw=1.0 music.ogg. Problem is that raop-play isn’t endian safe, but the alsapcm module forces use of little endian somewhere before the real raop-play. Afterward I’ve tested raop-play on amd64 where it works nicely. Java Java seems to be a problem. None of the packages of ibm-jre packages I’m seem to be able to find is supported by java-package. My Bank uses java, so that is kind of a show stopper, but I havn’t really looked into it yet. Flash, Youtube and the like Flash isn’t really a showstopper, but it would be nice to be able to see all the funny video clips people are refering to. None of the free flash plugins seems to work (swfdec, libfalsh-mozplugin), but youtube-dl and mplayer do the job. Futher work… Java is a major show stopper. I can’t switch for real without java support in my browser. The other problems is something I can live with. I migth even prefer to use AirTunes from my amd64 server instead of my laptop so I will probally ITP raop-play soon. Some people have asked why I want to switch away from wonderfull OS X. I’ll try to wirte something up one of the days - and no it’s is not anything personal against mac fans.

Antti-Juhani Kaijanaho: Looking for dctrl-tools testcases

If you use grep-dctrl, sort-dctrl or tbl-dctrl, I’d like to see your use cases! I’m building a system test automaton for dctrl-tools, and I’d like to include as much real-world examples as possible so that any regressions get found before uploading. You can send example command lines (and preferably also a test file, unless it’s one of the standard Debian files like Packages) to me by email at <ajk@debian.org>, as a wishlist bug report against dctrl-tools or by a Darcs patch against the experimental repository (see instructions).

Evan Prodromou: 20 Germinal CCXV

I'm really excited this morning. Wikitravel has been nominated for a Webby Award in the Travel category. It's amazing to get this kind of recognition for the work that our community has done over the last four years. I think that Wikitravel has a good shot at winning the award. I also hope that the Open Source and Open Content community, as well as wiki enthusiasts, will turn out to vote for us in the People's Voice Awards (open to voting by the entire Web community). tags:

AboutUs.org has OpenID Looks like Portland (Oregon)-area startup AboutUs has implemented the OpenID extension for MediaWiki. Meaning that anyone can log into AboutUs with an OpenID! This moves AboutUs into a nice single-signon network with Wikitravel, Wikevent, and wikiHow, as well as a number of other OpenID-enabled sites. Great for them. tags:

Adam Rosi-Kessel: Running a Hospital

Running a Hospital is a blog actually written (not ghostwritten) by the CEO of a large Boston-area hospital, the Beth Israel Deaconess Medical Center. The blog covers hospital/health-care issues as well as some unrelated topics. The emergence of this sort of open and frank discourse from leaders (particularly in medicine) is a real sea change. Just a few years ago, this sort of relatively unedited discussion would have been shut down by the lawyers. It’s an interesting variation on the “medium is the message” concept. Of course, everything this CEO (and others) are writing doesn’t require the web or weblogs. The same content could easily have been provided in a printed newsletter (setting aside the minor cost issue). Weblogs have established new norms, however, that enable openness even in particularly liability-sensitive areas like medicine. For example, see this entry about fatal infections resulting from central lines. On a lighter note, should the hospital use cage-free eggs? (I said yes.) Technorati Tags: ,

Neil Williams: pilot-qof finally leaves NEW

One version of pilot-qof went into Etch (0.1.1-3) with 0.1.2-1 uploaded to unstable after the freeze and just migrated into Lenny. A new release had sat in the NEW queue for a month due to the final stage of the Etch freeze. Finally, it is moving into unstable. 0.1.3-1 separates the pilot-qof binary from the perl, XSL and documentation making four packages in all, three under the new title: datafreedom. See data-freedom.org.

Hopefully, splitting existing Debian packages will not require a spell in the NEW queue in future - or at least a reduced queue, after all these packages have been checked once already. (Hence Sam was my first choice as DPL - congratulations again, Sam.)

If you previously used the XSL stylesheets from pilot-qof, you will now need the datafreedom-qsfxsl package. Note that the location of the XML catalog (and the XSL stylesheets) has changed too. See NEWS.Debian in the pilot-qof package. (zless /usr/share/doc/pilot-qof/NEWS.Debian.gz).

The intention is that the datafreedom packages will now mature to support a wider range of small utilities like pilot-qof - there is already support for calcurse, contacts, dates, gpe-expenses, gpe-calendar and a few others - justifying the package name change.

The XSL is (predictably) limited to converting from XML so if XSL is used to convert to a non-XML format, you'll also need the datafreedom-perl package to support conversion of non-XML data back into XML for inclusion into pilot-qof or conversion to other formats via XSL. The perl scripts also include support for aggregating data sources to create new data sets, e.g. combining addressbook, expenses and contacts data sources into a simple invoice. If, like me, you enter new data into your Palm whilst travelling around on business, you can HotSync the Palm and generate all your invoices in one script!

The perl package includes a number of new scripts and brings in a few new perl module packages and this is where the majority of updates are likely to occur in future.

Enjoy!

Gerfried Fuchs: OpenBC/Xing is Closed Minded

I'm not sure if you have heard about Xing (formerly known as OpenBC) yet. It is meant to be a platform to keep in touch with your business contacts, by having them update their contact data on them own. It also offers additional services, including discussion groups, because since Orkut we know that such a platform won't work without. (But I don't want to rant about Orkut here, thanks for asking.) I stumbled upon a group called GayBC. I guess from the name of it everyone is able to find out what it's about. And it is a closed group, so people who are afraid of discrimination because of stating there preferences publically can feel save. I though that might be the group I'd like to join, having no real problem with my own sexuality of being Bi. (Although, I say it myself that my poem "Mermaids" isn't about the sexual part at all and people who seem to read this in it are not understanding it.) Given that there wasn't too much information on the group page about what they want in the join info I didn't provide too much informations and was rejected of course. I say of course, because that just gave me the impression that the moderators do really care. Alright, I told myself, I'll answer their mail with all informations I could provide. I'm not sure if my fault was that I did that offsite per email or what, but it was never responded to, at all. So I tried to look on the site again for the group page, only I wasn't able to find it anymore through the search. After some digging around through the system and other groups I found out the schema of how the URL has to look to see that I just see on the page that I was rejected. No informations on how to contact the moderators anymore, no information on if this is permanent or whatsnot. So I tried to contact the site support, asking if there is a timeout to such a reject and posibility to reapply, or any idea how to go on. Well, they first tried to tell me to contact the moderators (and ignored the other question). After I told them that that's not possible and teaching them about their own system, they finally forwarded a mail from me with more informations to the moderators. After a while I got a response from one of their moderators saying that as a Bi person I'm not gay enough to join the group... I was like... Uh! A group, that is about people facing discrimination in quite different ways is discriminating themself. I wasn't able to think straight for a while after I read that, trying to find out about what's going on... Well, I thought to myself, the group is German language, and doesn't want to have Bi people in it—so I thought I should turn the anger into something productive. Turning emotions into something productive/creative is the way quite a lot of conflicts can be avoided and good things happen. I applied for creating a group called LesBiGay with the intended purpose of being a closed group too, but not discriminating against Bi people and being English language, and explicitly stated in the comments that the existing GayBC group doesn't want Bi people amongst them. Guess once what happened. The staff from OpenBC rejected the request with the reasoning that GayBC exists already and that I should get in contact with them. Interestingly that message was sent in a way that doesn't allow a reply... The much I like the feature of having all the contact informations for the people available in a nice way and having them current the much I have to make you aware that the rest of the system stinks. Keep away from it, it works against you, doesn't offer minimal informations or features and flexibility. On a sidenote—a dear friend of me showed me Venus Envy after my last blog entry and it really made my last days. Read it all! :D It gives me quite a lot of strength, and there I found this beauty that I dedicate to the GayBC group on OpenBC. Enjoy.

Ingo Juergensmann: Upgrading to Etch considered harmful

Oh well... today I upgraded a server at my workplace from Sarge to Etch. This went fairly well EXCEPT that the machine was quite slow afterwards and Samba didn't work anymore. No problem, I thought, because during the upgrade the Samba was displaying a note that I'll need to change the passdb line, because it doesn't support chained backend lists anymore.
The problem was, that this didn't help. To make a long story short:
During the upgrade the file /etc/libnss-ldap.conf has been overwritten without any notification. There's even no /etc/libnss-ldap.conf.dpkg-old file.
Apparently the QA of the Etch release failed in this particular case. Am I the only one who's using LDAP?

Update:
Meebey hinted me to have a look at the config file. The problem is, that the config file has a Debconf header, which indicates that it is handled by debconf. I'm used to edit those files anyway, because usually debconf (or the package scripts) notices if the file was changed manually and gives a warning about this issue. Well, the libnss-ldap package seems to be rather dumb and doesn't recognize when something has been changed within its configuration file. So, removing the debconf header will prevent this from happening again. Thanks, Meebey!

Bastian Blank: pvmove still blocks sometimes

I thought the problems with pvmove was fixed with devmapper 1.02.12, but I just run into this problem again. Not sure if there was different fixes in later versions. pvmove suspends the devices and fails to reload tables under some conditions. This time it just blocked while the devices for /usr und /var was suspended. This means the system is dead. Update: It seems to be related to the number of LVs to move. Only one works all the time.

Stefano Zacchiroli: coq as a geek toy

Coq: Happy to See it as a Geek Toy Daniel, I'm really happy you defined Coq a geek toy. Usually such pieces of software are more seen as academic toys, seeing it promoted as a geeky software is a joy to me. I'm a developer of Matita, a concurrent system of Coq (yet less mature a of today). I'm happy to give some more info about Coq (and hence about Matita, which is based on the same logical foundation of Coq). Coq is not really a programming language (even if the CoqArt book says so, to attract the developer community), it is mainly a proof assistant; i.e. a software in which you give definitions, state theorems and prove them. The added value of the system wrt plain pen and paper is that it grants that you won't be able to produce incorrect proofs (of course you are still free to prove useless theorems :-) ). It is more expressive than predicate calculus, technically it is based on the Calculus of (Co)Inductive Constructions, but the most important differences are that you can give inductive definitions of predicates (or define recursive data structures) and the system will let you play with them freely automatically constructing recursors on these data types. You can even define infinite data structures (using co-induction) mimicking lazy types available in languages as Haskell. Regarding the synergy of Coq with OCaml: yes, you can prove in Coq the correctness of OCaml program, but actually not more than you can do with programs written in other programming languages (see for example Why, Krakatoa, and Caduceus for some practical tools to prove properties about Java and C programs). Yet the synergy with OCaml is even more than that: once you proved properties like the existence of, say, a prime number greater than a given prime number, you can ask Coq to generate for you (using a feature called extraction) an OCaml program which consumes as input a prime number and returns the next one. More generally you can extract programs from (suitable) proofs. Some info on the Debian side: thanks to smimou Coq has been in Debian for a long time now and Why/Krakatoa/Caduceus are coming soon. Happy hacking!

Bastian Blank: Not so funny kernel build failures

It happened again. The linux-2.6 2.6.20-1 release failed for arches which we don't build snapshots for. This means that none of them was ever built in the time after I commited the whole stuff. As this happens over and over again I consider this a real problem now. So the following arches needs new debian-kernel maintainers: alpha, hppa, and mips.

Andrew McMillan: Moved to a new (old) server

I've now moved lots of things to a new (old) server which should be noticeably faster than the old (old) 500MHz PIII-based server. Of course since Etch was released I'm now running on Etch. This also meant an upgrade to PHP 5.2, so I spent some time getting bitten by this bug with Drupal 4.7.4 and PHP 5.2 and had to upgrade to 4.7.6. Consequently there has been a wee bit of bouncing up and down today... In the process I have also upgraded my packages for eAccelerator so that they would work with Etch. Since Andrew Hutchings had taken them off me and played a bit further I have now taken his packages and built some newer ones, including a patch for 0.9.5 to work with PHP 5.2, and an additional build dependency. My new (old) server is still 32-bit, so these packages are only built for 32-bit as yet. I'm currently trying to find a 64-bit Etch box I can build them on as well, but everyone at work seems to have gone home. You should be able to fetch them from my package repository by adding it to your sources.list with:

deb http://debian.mcmillan.net.nz/debian etch awm
Naturally that repository is signed with my public key (8f068012), which is in turn signed by lots of people in the Debian community and should be readily identifiable - not that that implies trust, of course :-). Also, since my new (old) server is in a different location (and to ease the transfer) everything is on a new IP address (and a new IPv6 address). Hopefully the system's accessibility over IPv6 on http://ipv6.geek.nz/ will be slowly improving as we incrementally improve our IPv6 connectivity with the rest of the world.

Mike Hommey: Browser detection

Erich, the Gecko version number is pretty meaningless. With mozilla releases, the date reflects when the build was done. Which means if you build Firefox 1.5 today, it will get a Gecko/20070410 string. With Debian releases (except icedove), the date reflects the date for the client.mk in the source tarball, which is one of the last file upstream touches before a release. This helps having the same date for all 11 architectures (even after a binNMU) and is somehow more significant, but still not that much. There are, at the moment, 3 main branches for Gecko-based code: MOZILLA_1_8_0_BRANCH, MOZILLA_1_8_BRANCH and HEAD. The latter currently contains Gecko 1.9 alpha, Firefox 3.0 alpha, etc., and will eventually be branched to a MOZILLA_1_9_BRANCH or something similar when going in beta. The other branches are respectively for Gecko 1.8.0.x (Firefox 1.5.0.x, Thunderbird 1.5.0.x, Seamonkey 1.0.y, Xulrunner 1.8.0.x) and Gecko 1.8.1.x (Firefox 2.0.0.x, Thunderbird 2.0.0.x (not yet released), Xulrunner 1.8.1.x). [ In Debian Etch, we have Iceweasel 2.0.0.3 (Gecko 1.8.1.3), Iceape 1.0.8 (originally Gecko 1.8.0.10 but patched at version 1.8.0.11), Icedove 1.5.0.10 (Gecko 1.8.0.10 ; changes from version 1.8.0.11 didn’t make it, but they don’t affect the mailer code), and Xulrunner 1.8.0.11 (Gecko 1.8.0.11). The latter is used by kazehakase, galeon and epiphany. ] Whenever a new security release for Firefox 1.5.0.x and other products from the Gecko 1.8.0.x branch are done, the Gecko date obviously changes, and doesn’t reflect the fact that it’s an older Gecko than that of Firefox 2.0.0.x… Now if you take a closer look to the user agent string, you’ll see something that is actually more significant than the Gecko date, i.e. the Gecko revision, such as “rv:1.8.0.11″ in “Mozilla/5.0 (X11; U; Linux i686; ja_JP; rv:1.8.0.11) Gecko/20070324″

Bdale Garbee: Technical Committee Update

The Debian Technical Committee has recently decided three outstanding issues, and at least one question still before the committee is moot now that etch is released. So, I spent a little time this evening updating the committee's web page , and closing the bugs related to the issues decided so that we can better focus on the remaining open issues .

Evan Prodromou: 19 Germinal CCXV

We had a great time yesterday evening at the cabane sucre (sugar shack). It was about a 1-hour drive to the Sucrerie de la Montagne, a Quebec historic site near Rigaud, just a few kilometers from the Ontario border. We went with a group of friends, mostly anglophones, most of whom had never been to a sugar shack before. Late March and early April are when the maple trees are giving their sap for syrup, and the rableries (sugar farms) host big dinners at their farms for city guests. It's a great way to get a taste of traditional Qu bec culture. It was pretty cold when we got there -- we still have snow on the ground in Montreal so we all wrapped up as warm as we could. Poor Amita June fell in a puddle as we were walking across the parking lot, which caused not a small amount of crying, so Maj and I cleaned her up in the car. But the tears cleared up as we got close to the sucrerie. Amita called out, "BUCKETS!!" when she saw all the taps in the sides of the maples. There must have been 1000 tapped trees right near the main lodge. The sucrerie itself was a pretty impressive set-up. 4-5 buildings in an 18th-century rural style, hewn from logs, caulked with clay. There was a big outdoor fire with people sitting around, but we edged our way into the bakery, first thing, where we saw a few dozen loaves of bread baking in the stone oven. Then we went into the main dining hall -- dozens of tables laid out for guests. We were big enough to take our own table, and AJ took a high chair at the end. Each table had a quart bottle of maple syrup on it. The first course was split pea soup (a habitant classic), followed by a brunch-y meal of omelettes, mashed potatoes, beans, fresh bread, ham, sausage, meatballs, and torti re, the classic Qu becois meat pie. For dessert, we had coffee, maple sugar pie (you can feel the enamel of your teeth coming off), and... pancakes with maple syrup. All during dinner we were serenaded by a band playing classic Qu bec folk tunes on traditional instruments, including a saw. We waddled out of the cabin, and I wasn't looking forward to the walk to the car, which made me glad that there was a horse-drawn carriage waiting for us. The "carriage" was about the size of a flat-bed truck, pulled by two Clydesdales that must have been 3 meters tall at their ears. Amita loved seeing the horses and taking a ride, and I loved not having to walk. It's a good time -- I highly recommend it for anyone who hasn't had the experience. tags:

RoCoCoCamp I spent most of the day today sending out invitations to wiki people about RoCoCoCamp. RoCoCo is the Montreal version of RecentChangesCamp -- it's an "unconference" about wiki technology and wiki culture happening 18-20 May 2007 here. I've been pretty frantic about contacting people since I got involved in a serious way in RoCoCo in February. but I want to make sure that people who are involved in wiki, or more generally in technologies for community and collaboration, can make reasoned decisions about coming. We've got a really exciting group coming already, of course, and I don't mind anyone missing it because of schedule conflicts or lack of funds. But I'm torn up inside thinking there are people who want to come to RoCoCoCamp who just don't know about it. Please, reader: if you have any suggestions for wiki developers or practitioners, or other people who might benefit, Contact me and let me know. Or just pass along the RoCoCo URL to them, and make sure they know that they're invited. tags:

Montreal Tech Entrepreneur Breakfast Tomorrow morning is the third Montreal Tech Entrepreneur Breakfast, 9AM at Bistro Etc. on av Mont-Royal, corner of Chambord. This is the 3rd monthly MTEB, and I'm pretty excited about it. I missed the February event through ignorance, and the March event because I was in Austin. I'm determined not to miss this one! tags:

Erich Schubert: On System Init part 1

I thought I could write a multi part blog series about init systems (with the obvious goal of convincing some more people we should properly support other init systems as well). In the first step, I'll have short look at our current init. First of all, our init isn't really /sbin/init from the sysvinit. The real work is done by /bin/sh, so usuall bash or dash. Using the latter can already cut down boot time for you by a few seconds, according to some people. The init process is indeed used to kickoff the system, but it's in fact not doing much. Pretty much all it does is described by /etc/inittab. If you havn't ever had a look at this file, maybe you should now. During a typical system boot, init is doing three things:
  1. Start /etc/init.d/rcS
  2. Start /etc/init.d/rc 2
  3. Start the gettys (console logins)
other tasks it handles is pretty much waiting for Ctrl+Alt+Del and if someone triggers a shutdown. The actual shutdown work is again done by a shell script - /etc/init.d/rc 6 So my claim that our init system actually is /bin/sh isn't really far off, is it? Some random notes: Maybe tomorrow I'll write a bit about features of other init systems, and what benefits they offer. Maybe also on why the SELinux strict policy doesn't really like this way of starting and stopping services because of isolation issues. Or on that there are two types of things happening at init. [Update: next post in this series.]

Erich Schubert: On System Init part 1

I thought I could write a multi part blog series about init systems (with the obvious goal of convincing some more people we should properly support other init systems as well).In the first step, I'll have short look at our current init.First of all, our init isn't really /sbin/init from the sysvinit. The real work is done by /bin/sh, so usuall bash or dash. Using the latter can already cut down boot time for you by a few seconds, according to some people.The init process is indeed used to kickoff the system, but it's in fact not doing much. Pretty much all it does is described by /etc/inittab. If you havn't ever had a look at this file, maybe you should now.During a typical system boot, init is doing three things:
  1. Start /etc/init.d/rcS
  2. Start /etc/init.d/rc 2
  3. Start the gettys (console logins)
other tasks it handles is pretty much waiting for Ctrl+Alt+Del and if someone triggers a shutdown. The actual shutdown work is again done by a shell script - /etc/init.d/rc 6So my claim that our init system actually is /bin/sh isn't really far off, is it?Some random notes: Maybe tomorrow I'll write a bit about features of other init systems, and what benefits they offer. Maybe also on why the SELinux strict policy doesn't really like this way of starting and stopping services because of isolation issues. Or on that there are two types of things happening at init.[Update: next post in this series.]

Gunnar Wolf: Etch is done! Sarge is done once again! Sam rules! Yay for the weekend!

Wow, what a wonderful weekend was this for Debian. And, yet again, I managed to miss the live announcement and party on IRC.
So... We got a shiny, new, French DPL. Just after that, we got one last release for Sarge, and right away we got a stable Etch - Who says having a new DPL cannot speed up things? ;-) Anyway... I don't remember where I started the meme when Sarge was released (it was not on my blog, it seems)... But here it goes again:
What were you doing at...
Etch release? Having a nice time with Nadezhda, walking around this broken and dear city in my last day of vacations.
Sarge release? At my psychologist. Yes, Sarge drove us all nuts.
Woody release? Sitting at a lent workstation at Departamento de Seguridad en C mputo in my University. Of course, the announcement was broadcasted right away to everybody around me ;-) I was in NM by then, and was a bit disappointed because my work didn't appear in the release.
Potato release? Don't know... I was not yet involved with Debian by then.
[Update]: Thanks to Wouter, my old meme-starting message appeared - is he more patient than I am, or just more organized? :-) Anyway, boo for Jaws breaking old URLs (I upgraded 0.4->0.5->0.6->0.7 since then)

9 April 2007

Daniel Burrows: Latest Shiny Geek Toy: coq

So, one of the reasons I've been a bit uncommunicative the last few weeks is that I've been getting my head around Coq, maybe one of the most fascinating pieces of software I've played with in a long time.

What is Coq? I don't know if I understand it well enough yet to give a complete description (the Coq tome only arrived in the mail on Friday and I have yet to make it past the introduction, what with taxes and so on). Here's my best shot:

Coq is a programming language where you write proofs as functions taking proofs of their preconditions and producing proofs of their results. That is, a proof that "If X is an integer, then X-1 X" becomes a function that accepts a proof of "X is an integer" and produces a proof of "X-1 X".

You can manipulate logical expressions more or less the way you expect. For instance, if you have in your hands a set S of natural numbers and a proof that "forall nonempty sets T of naturals, T has a least element", then you can bang these together to produce the least element of S (or rather, a proof that it exists).

I don't think this describes the theoretical underpinnings of Coq, but it does describe my experience of actually using it to prove stuff.

To get the hang of Coq, I'm working my way through basic automata theory -- regexps are done, but I couldn't work out how to express some finiteness constraints on FSMs without generating a lot of extra typing; hopefully the Coq book will have some hints. Once that's done, I'm actually tempted to try something more ambitious. [snip long digression] We'll see ... watch this space :).

It was a real rush, though, to code up these theorems and watch the computer verify them. What really fascinated me was how close to being a practical tool this is. Coq isn't at all a toy -- without quite getting all the theory yet, my intuition is that it can probably cover anything you can express in the predicate calculus (with sufficient amounts of typing, anyway), and while there are a few shortcomings, it's almost (IMO) at the point where anyone who knows some formal logic and has a little patience can prove interesting stuff. Even more suggestive of possibilities, there's a project (which I sadly haven't had time to look at) that integrates Coq with OCaml, so you can have proofs about your OCaml code verified at compile-time!

I could go on and on ... anyway, this is a really cool tool and I'd encourage any mathematically-minded person to give it a spin. The only sad thing is that I doubt I'll ever have the opportunity to explore this stuff in my day job unless/until I go back to school :-(.

Shortcomings of Coq specifically and the whole concept of correctness proofs on programs generally have been moved to a future blog post that may never appear depending on how ambitious I'm feeling this week. Rest assured that I'm aware of (some of) them, I just hit my self-imposed length limit.

[0] the reason being that I could only prove correct the formal underpinnings of the resolver; in practice, a lot of the bugs are in the interface to apt, or in apt itself, and I can hardly prove that code correct.

Peter Van Eynde: gone is sarge

from my CL repositories I have at my p.d.o pages. I will now track etch (and will try to get the packages into backports.org too), sid and ubuntu's dapper and edgy. I expect to track feisty after it is released.

Hmm. No release party in Belgium planned yet...

Next.

Previous.