Search Results: "ag"

8 August 2007

Neil Williams: Requesting adoption of glipper

RFA: glipper -- A clipboard manager for GNOME #436550.

Glipper is currently my package in Debian at 0.95.1-3 and that version
is written in C and uses a binary data file which has raised one bug
(#436078 - wishlist severity). It currently has no other bugs.

There is now a
new release
that closes this bug, my problem is that
v1.0 is a ground-up rewrite in Python! Essentially, glipper v1.0 is a
completely different package internally. (Previous translations have
also been lost.)

I have no python experience, no python packages and no ability to do
anything if (when) python code goes wrong. I don't want to have to
learn python just for glipper (don't have time).

So - I don't see what I can do except request adoption of glipper, it
just seems so weird to leave a package which is active while I am also
active.

Anyone fancy taking on glipper?

I don't think there's any point retaining the old C package - that code
is already dead upstream.

Currently, there is no RCS for the debian packaging for glipper - I was
using CDBS and the current watch file needs editing to look for a
tar.bz2 instead of the previous tar.gz.

There are two issues with migrating from 0.95.1 to 1.0:
  1. the ~/.glipper directory needs to be removed.

  2. Glipper v1.0 is also now GNOME only, support for other window managers
    has not been implemented in the python version.


Lars Wirzenius: Random thought: bzr uncommit

One of the things that occasionally happens to me is that I mistakenly commit too much. I use Bazaar (bzr) as my version control tool of choice, and tend to do "microcommits": every time I make a change that is a useful, if very small, step in its own right, and "make check" still passes, I commit, even if it is only a one line change. This means that usually all the changed files need to be committed. Sometimes, but rarely, I make unrelated changes in several files at the same time, and then I need to commit each change separately. But then I forget to specify the files on the command line. With CVS, I would just shrug and continue. With Bazaar, I do "bzr uncommit", which removes the latest commit from the branch, and then re-commit with the proper files. This is a small, but important, change from CVS, for me. It makes me happy. "Ha! Foiled you again, you stupid over-eager Enter key." I have no idea whether other modern version control tools have the same thing; this entry is not to advertize Bazaar, but share my joy in victory over Enter.

Andrew Pollock: [opinion] Everybody hates Mark

So Mark doesn't like the SPI board election results and has decided to call the largish whack of people who didn't vote for him and tell him ahead of time or something "cowards". Personally, I'm of the school of thought that if you haven't got anything nice to say about someone, don't say anything at all, but, well, here we are... I forgot whether I put him last, but he was certainly ranked towards the back of the pack. Why? I don't like rabid people. Rabidly anything shows a lack of balance to me. Mark's rabidly anti-Google (amongst other things) (sure, I work for them, but I liked them before I went to work there, otherwise I wouldn't have gone to work there) and frankly, it irritates me. Almost as much as someone else I know being rabidly anti-Microsoft/pro-Linux irritates me sometimes. Balance is good, and I'd rather have people on the board that I know, and I know in a positive light, over people that I don't know, or known I don't like. So I ranked my ballot in reverse order of people I knew I didn't like, then people I didn't know, then people I knew, then people I knew I liked. Simple as that. Oh, and I'm not a big fan of debian-legal, or anyone who purports to be an armchair lawyer on that list. Sorry if that damages your precious ego, Mark. Now get back to bashing my employer, Debian UK, and pontificating about what's allowed to be in Debian. (Oh, and I don't object to you having your own opinion, I object to you restating it over and over and over again. But it's your blog, and you're free to portray yourself to others however you please, just bear that in mind when you go standing in elections.)

Andrew Pollock: [life] Oh, baby!

Today we went to see our new obstetrician. Ironically, he was our second preference (our current, third preference, who hasn't been all that endearing anyway, is going to be out on sabbatical when the baby's due). I think we'd already decided we liked him better before we even met him, but he did come across as a bit more calm and less alarmist. That said, he is currently of the opinion that the baby should be delivered at 36 weeks, which is September 14, which is a few weeks earlier than the date we were throwing around, of October 8 (Sarah's Mum and Aunty arrive on October 6). So that's going to make things interesting. We're seeing him again next week, which is after Sarah's had another echo-cardiogram to see if her aneurysm is still stable. The results of that will help firm up the delivery date. He also said that because the 28-32 week mark is when the heart's working the hardest, we're really in the danger zone now. It looks like we won't be going camping next week after all. The doctor didn't think being 6 hours by car away from home was a terribly good idea.

John Goerzen: Disasters happen

It's been one of those days.

It started with me forgetting my laptop bag at home. Then I had to work with an attorney on some things. He's a nice guy, and does a good job, but you know, it's not what I'd really like to spend my day doing.

Then in the middle of the afternoon, I hung up the phone and checked my email. About 50 messages from Samba telling me that processes with various PIDs had crashed unexpectedly. Uh-oh. I think we still have some 80ish people using that.

About a minute later, a coworker says, "John, I've been bad." "Is that why I just got 50 emails from Samba?" "No. Well, yes. Well, maybe. I don't know."

It turned out he was working on a restore from tape that, out of necessity, grabbed more data than he needed. He meant to type rm -r ./var but typed rm -r /var instead. Oops. He hit Ctrl-C halfway through, so /var was still there enough to send email but not enough for Samba (or, apparently, NFS) to work.

As he dashed off to pull yesterday's tapes from offsite storage, I prepared the restore and made a plan. We hadn't installed any software since yesterday, so I restored var to a temporary location, took the server down into single-user mode, overwrote the /var that still existed, and rebooted the Xen instance in question. Everything back to normal. Except, that is, for the potentially dozens of users that will require assistance running SCANPST.EXE because their Outlook PST, being the fragile heap of garbage that it is, will have somehow been corrupted by this little incident.

So, what did we learn from this?

John Goerzen: I suppose this means I'm a geek

I work in an open-plan office. Normally I like to listen to some of my iPod's music, or NPR or something, at some point during the day. It helps me tune out distractions when I'm coding or concentrating on something. My iPod, and my nice Etymotic headphones, get transported to and from work each day in my laptop bag. Today I forgot the laptop bag at home.

What to do? I could just work without headphones. I'd be fine, but you know, I've got standards here. My job involves working with computers, so I ought to be able to come up with a workaround, right?

So lesse... what do I have? One binaural (mono sound, but speakers for each hear) telephone headset. One Polycom SIP phone, connected to our corporate Asterisk system. One workstation with sound capabilities. One installation of Asterisk on this workstation for testing purposes. And, a pre-existing path from the corporate system to the workstation system for testing Asterisk. (Very handy that, and used a lot when we were doing active Asterisk work.)

So in less then five minutes I had music going via my telephone headset. Lo-fi, and not noise-dampening like the Etymotics, but I enjoyed it for the simple fact that it was being played *over the phone* at no cost to anyone. My desk phone supports multiple "lines", so I still could place and receive calls just fine.

Should anyone care to look, they'd find a 5-hour call from me to myself deep in the Asterisk logs. My own workstation logs will show that I put myself on hold for 5 hours (since I used Asterik's music-on-hold feature to play my own selections).

IP telephony is fun. So is Asterisk.

Matthew Palmer: Just so I'm not accused of being a coward...

Since MJ Ray seems to think that anyone who doesn't vote for him but doesn't tell him why is a coward, I'm going to be up-front about it so I can't be accused of cowardice. Elections are all about everyone making their own decision, for their own reasons, in the hope that the aggregate of those decisions will produce a useful and workable result. (Whether that happens in reality is a whole other issue). The individual's decision is a statement of their opinion, nothing more. Adding confidentiality to the voting process is meant to remove any pressure from the voter to make a decision on any basis other than their own opinion. Complaints about it like this from a candidate is pretty weak:
There seem to be some 30 or 40 voters who really dislike me, but didn't tell me that straight, preferring to be silent then vote me down. Are you cowards, or what?
Given this outburst, I'm hardly surprised that people weren't keen on telling Mark upfront that they weren't going to vote for him. (As a disclaimer, I didn't vote in the SPI election, because I don't have a specific opinion on any of the candidiates' suitability for office on the SPI board.)

7 August 2007

Evan Prodromou: 19 Thermidor CCXV

I'm on the plane down from Vancouver to San Francisco this morning. My flight from Taipei hit Vancouver around 8PM last night, so I stayed at the Fairmont Hotel at the airport. It was definitely a special treat -- the Fairmont's pretty pricey -- but this trip has been really low-budget and I needed a lot of rest and recharge. I had a good room with a view of the airport and the city beyond. My flight over was uneventful -- sleep, eat, Spiderman 3 -- which was good since I'd had such a big last day in Taipei. In the morning, I'd gone out to see Taipei 101, which claims to be the tallest building in the world by some standards. I think there are lots of ways to slice the "tallest building" category -- the CN Tower has a strong claim, but that's only counting the huge antenna on top. And there's an unfinished tower in Dubai that's already close to, or taller than, Taipei 101. Regardless, Taipei 101 is a real interesting site. The elevators are the fastest in the world -- 38 seconds to go from floor 5 to floor 87. The windowed observation deck is interesting, and there's an outdoor deck two flights above it. The outdoor deck is racked by Taipei's scorching heat -- when I was there, it was 31C, up above the city's protective smog belt. The sun and empty sky make for an otherworldly experience. After 101, I took Taipei's local subway, the MRT, to the National Palace Museum. I've found the MRT easy to get around on -- most of the information was available in English as well as Chinese -- but I got a little lost looking for the museum. I was disappointed that the information booth in the Taiwan Main Station had so little tourism information, and all of it in Chinese. (Yeah, I forgot to print out the Wikitravel Taipei guide before leaving the hotel. My bad.) But I managed to wend my way out to Shilin Station and took a cab to the museum. It was worth the search. When the Chinese Nationalists left the mainland for Taiwan, they took with them many of the treasures of the Imperial Palace (much to the chagrin of the victorious Communists). These form the core of the museum's collection, and they're really quite amazing -- articles in bronze, ivory and gold from the Neolithic era to the modern day. While Western culture has gone through so many distinct and discontinuous phases -- Egypt and Mesopotamia, Greco-Roman, Medieval and Modern -- China's has varied much more smoothly and continuously. It's a little disconcerting to see artistic themes from 4000BC that are echoed in items for sale in the stores today. I had to get back to the Wikimania site -- by then almost empty -- to do a GChat conference with Niko. There were a passel of Wikimaniacs still around after the conference looking around Taiwan like I was, and after consulting Wikitravel we decided to go to Taipei's most famous restaurant, Din Something Something. It's got a short menu of delicious steamed dumplings -- pork, veggie, crab and shrimp. The shop's claim to fame is the elastic skin that keeps a pocket of hot broth inside the dumplings. Hey: if you do something well, why vary the menu? It was the best meal I've had in a long time. The dumplings themselves were incredibly good -- moist and rich with complex flavors. But the company was even better -- about 14 Wikimedians from all continents and walks of life, some of the most fascinating and important people on the planet. We were a big enough group to be stowed in our own party room, and with basket after basket of steamed dumplings piled onto the table, washed down with shared bottles of the ubiquitous Taiwan Beer, we had a crazy chaotic and fun time. I'm so glad I took an extra day after the conference to see a bit of the city. I think there's a lot more that I missed, but I'm glad that I got a taste. tags:

Wikimania 2008 Inevitably the conversation at Din Something Something turned to Wikimania 2008 and possible venues for it. Right now, the only serious bid is from Alexandria, Egypt, home of the Biblioteca Alexandrina. This is a modern reconstruction of the famous Library of Alexandria, centre of learning for the ancient world and repository of all of its knowledge. The bid is to use the sleek, glamourous conference centre attached to the Biblioteca -- offered to us free of charge. You couldn't put together a more powerful metaphor -- Wikimedia being itself a project to capture the world's knowledge and share it with all humanity. Having our event on the African continent would also send a great message about the Foundation's commitment to making free information accessible to the developing world. North Africa is definitely the most accessible part of the continent for Europeans and North Americans -- many of whom balked at the price and distance of travel to Taipei. The big problem with planning Wikimanias (Wikimaniae?) in the past has been the short time-frame. Typically bids for the event don't start until after the previous one, and the bidding process takes several months. By the time a venue is selected, there may be only 6-8 months of planning time available. For an international conference of several hundred people, this is a stressful, breakneck schedule. The idea was floated to do a little stutter-step and put Wikimania on a more long-term planning schedule. The event committee would short-circuit the bidding process this year, and declare Alexandria the site for Wikimania 2008 unless other groups insisted on bids for other cities. Then, bidding for Wikimania 2009 would start in September or October, with a decision made by the end of 2007. This would give 20 months for the Wikimania 2009 organizing team to prepare. Most importantly, they'd be able to shadow the 2008 team, learn how the job is done, attend the 2008 conference, and present about their venue for the next year. I think this is a really good idea. The Biblioteca conference centre staff will be able to provide us some professional services, making the shorter schedule (still about 11 months) a lot easier. There are some concerns about fairness of the process, or appearance of same, but my guess is that if the 2009 bid process starts soon after, people won't have a big beef. There are two major concerns with going to Alexandria, though. First is Egypt's worrying problem with human rights -- specifically gay rights. Homosexual Egyptian men are subject to arrest, and the laws are occasionally enforced. One foreigner was arrested in 2002. That's enough to put Egypt on a no-visit list with some gay-rights groups. Depressing as it is, I think it might be too much to hope for a venue in a country with an absolutely spotless human rights record. Maybe parts of Scandinavia...? There's a cruel calculus needed to evaluate which national human rights abuses can be reluctantly overlooked, and which are unacceptable. It's also clear that my personal judgment might be clouded, since this particular human rights issue is not one I would be directly targeted by. My hope is that an official statement by the Foundation would make it clear to the Egyptian government that this kind of policy is not conducive to attracting overseas business and tourism. The second concern is that Egypt and the Arab world in general have only embryonic local Wikimedian communities. While there are many people who contribute to Arabic Wikipedia, there is not a Wikimedia chapter in Egypt, nor are there regular meetups in the country or region. This might be a chicken-and-egg problem: choosing Alexandria would probably kick-start local groups. I hope that ar: Wikimedians pick up the mantle of leadership that the world Wikimedia community is offering them. tags:

Adrian von Bidder: Fun with virtualisation

Since I seem to be the last person these days who doesn't run his servers inside Xen, Vserver, kvm, lguest or whatever, I decided to finally evaluate Xen. Not having spare hardware and not wanting to really touch my main workhorse, I started with Qemu. Installing etch inside a Qemu (why can't qemu have working tun/tap setup scripts by default?), then xenifying this according to Ganneff's excellent slides, I was stopped while booting into the Xen kernel with a hard freeze in the boot process (Inside Qemu, so no harm done.) Talking to some people in #xen resulted in me disabling kqemu, and a few minutes later I had a working dom0. Debootstrap is slooooooowwww (well, inside a non-accelerated Qemu machine...)! So I decided to use cdebootstrap instead. Sadly, xen-create-image has debootstrap hardcoded, so I had to "ln -sf /usr/bin/cdebootstrap debootstrap". (I decided to do this when debootstrap was still calculating dependencies after several minutes.) After that, creating and booting a domU Just Worked(tm). Having a running Xen environment, I finally wanted to play around with live migration (mostly I was just curious how robust this Qemu + Xen setup is...) So, just clone the qemu disk and boot them both. Whereupon the two qemu machines have the same MAC address, hence networking is not reliable. Change the MAC of the second Xen dom0, curse udev for thinking that now the network interface should be eth1 (persistent device naming is a good thing, generally. I'm not sure there is a sane solution possible that can cover all/most cases. Computers with only one network interface might warrant some special logic ... Oh well.) Having restored the networking setup, enabling the relocation service in the Xen configuration is trivial. After thinking about using plain files on NFS and seeing a Novell tutorial which uses iSCSI, I decided that I should try AoE because it should be much simpler to set up. And by installing the 'vblade' package, it is indeed possible to have an AoE server running within a few minutes (the vbladed command doesn't take the -m option, though.) And the client side is just as simple, just install the aoetools package, and /dev/etherd is automagically created and lists all available devices. That's how SANs should work! (Note: I had the AoE devices in the dom0 and passed them to the domU. A next experiment would obviously be to pass AoE directly to the domU as root devices. Not sure what the implications would be, though.) Ok, after all this, I have two dom0 machines and a domU. Just for fun, I've installed xdaliclock inside the domU and started a live migration. Result: it works stable (modulo some scary kernel messages popping up when booting the domU. I didn't experience any crashes in this light test), xdaliclock stops for a mere 20s (yes, seconds, not milliseconds. Remember, this is two layers of virtualisation without hardware support.) Normal migration (pausing the domU), the migration takes roughly 2 min (both dom0 have 384M RAM assigned in Qemu, the domU has 128M in Xen, the host is a 3GHz P4 with 1G physical ram. There is some swapping going on (I use KDE, so some of the RAM is lost there. I also didn't stop beagle for this experiment.) The full live migration takes about twice as much time. But this said, if you're using Xen inside qemu, timing values are not what you're after... I was, frankly, astonished at how well this worked. Hmmm. I wonder, if I can stack some other virtualisation layer somewhere in there? Just to see how silly it might get.

Sergio Talens-Oliag: Lifestyle, Resignations and the Peter Principle

I'll be 0x24 (hex) or pow(6,2) (dec) years old next Sunday and it is becoming obvious that I need to change my lifestyle. On the physical side I'm sure that I have to loose between 20 and 30 Kg. if I don't want to have health problems in the future. The plan is to change my eating habits and do sport regularly. The basic idea is to do a diet seriously and keep part of the rules more or less forever (that's the habits change); the other important thing is to do some exercise, I've never liked sports too much, but I'm sure I can try to walk some days and swim others (I've been going once a week to the swimming pool during the last months and I'll be doing it twice a week starting this September). On the mental side, I need to reduce my obligations and care less about the work problems in and out of the office. To reduce my obligations and have more free time I decided a couple of months ago that I was going to leave the Uni, as it was taking away a lot of time that I can use for more important things; I notified it and after this September I won't be working for the Universitat de Val ncia anymore. Initially my idea was to keep my main work and use some hours each week to work on my PhD Thesis, but the truth is that I'm not interested anymore; I don't have anything specially interesting to say and my main motivation for getting a PhD has also disappeared (at some point I thought about becoming a full time University professor, but after three and a half years I've had enough, at least for a looong while). This leaves me with my work at the ITI as my main and only work, but after some months I'm seriously considering leaving it also. My main problem there is that I believe that I'm starting to suffer the Peter Principle or something similar; almost all my professional career I've been working as a technician, first as a programmer and sysadmin and lately as analyst and team leader or technical manager, but now, as it seems to happen always in the Spanish IT companies, I'm being forced to move to a pure project management work and, to be fair, I don't like it. I don't know if that means that I'll get to my level of incompetence, but if that is the case I think I'll have to try the Peter's Parry, that basically means to refuse a promotion (I've already done it asking to get a place under my theoretical level, although not on a convincing manner, it seems) or use the Creative Incompetence technique, that is, give the impression that you have already arrived to your incompetence level (probably it is too late to do that at my current place, but maybe on the next one I'll be able to do it). Maybe this is not the last level of the Peter Principle, as I'm sure that I can and will do this work (I'm thinking about moving, but I will not do it until I have a plan for the future, and that will probably mean a new job), but I'm also sure that I will never do it as well as I can do technical tasks because I don't have any real motivation to do it and while I plan to get the skills needed, they are not attractive to me. I understand that on the current IT world we need to have project managers, and I really hate bad managers, but that does not mean I like to become one, I prefer to be a team leader and work only on one or two projects at a time, instead of having more than five and not do real work in any of them; my main problem is that the challenges and tasks a manager has to do have nothing in common with the things I like from computer science and I'm too perfectionist to handle people that does not care about how things are done in a lazy way (a team leader with a couple of projects can handle technical people, when you are a manager with multiple projects you miss the day to day perspective and problematic people is more difficult to handle). Oh well, we will see how things evolve. The good thing is that I believe that one way or another I'll end up having a better life and, if I'm able to care less about my own work (and the one done by others) maybe I'll be able to stay at an acceptable level on the hierarchy without getting burn out and maybe some day I'll be able to work again on the things I like and keep my promises.

Miriam Ruiz: How to make a Debian package without using a helper reviewed

My old tutorial “How to make a Debian package without using a helper” seems to be getting a lot of clicks, so I’ve decided to upgrade it a bit and put it up to date. There are not many changes anyway, but just in case someone is interested in downloading it: roaddemo_1.0.1-2.dsc, roaddemo_1.0.1-2.diff.gz and roaddemo_1.0.1.orig.tar.gz are available.

Andrew Pollock: [debian] Doing random repository things with Python APT?

Dearest Lazyweb, I want to write a program that I can point at a standard repository, and an in-house one, so I can track version differences between common packages. I wanted to write this in Python, so python-apt sprang to mind, however the documentation is somewhat lacking, and none of the examples include retrieving a package list from anything other than the local APT cache. The documentation in libapt-pkg-doc is also rather lacking. So before I go giving up on using a "proper" library for the task, I thought I'd reach out. Love, and sloppy kisses, Andrew

Neil Williams: translation support script

Just a little script that I've found useful when working out which packages contain translations needing an update - WITHOUT regenerating the POT file unnecessarily and thereby messing up CVS/SVN/RCS status of the PO files themselves. (You still need to regenerate the POT file when the strings actually change but this script is useful when receiving updated PO files.) The script checks each PO file and omits those that are up to date.

Add your own set of working directories.


#!/usr/bin/perl -w
use strict;

print "emdebian-tools\n";
chdir "/opt/working/emdebian/svn/current/host/trunk/emdebian-tools/trunk/debian/";
&check
print "deb-gview\n";
chdir "/opt/working/deb-gview/";
&check
print "pilot-qof\n";
chdir "/opt/working/pilot-qof/";
&check

sub check

opendir (PO, "po") or die ("Cannot open po directory. $!\n");
my @files = grep(/\.po$/, readdir PO);
closedir (PO);
foreach my $po (@files)

my $msg= msgfmt -c --statistics po/$po 2>&1 grep "[fuzy]" ;
print "$po: $msg" if ($msg ne "");
undef($msg);

unlink ("messages.mo");


Wouter Verhelst: Blog slightly fixed

I spent some time fixing some outstanding issues with my blog. The LiveJournal import on my blog had the wrong timestamp. I had some old ruby script that I'd written two years ago when I still believed ruby would someday become my language of choice (it didn't) which converted the livejournal XML exports into something that blosxom would grok, but it didn't work anymore. Apparently ruby's XML library API changed slightly between then and now. Read /usr/share/doc/libxml-ruby/README, updated the script, ran it again, and it worked. So now the blog items are dated on the date they were actually written, rather than 2005-02-17. Since a few weeks, I've been offering a myrss version of my blog feed, which contains a saner version of a link to the item (linking to the path that I wrote it in, rather than some date-based ugly stuff). Liferea choked on it, though, as did the feed validator. Turns out I managed to enter a few minor typos. Fixed those. Apparently the typos weren't of the magnitude that planet would choke on them, but still. So now my blog is slightly improved. Isn't that great. I still wonder why I have this blosxom-writing-php-scripts-with-home-grown-comment-system rather than, say, drupal, but that's for another day. OTOH, drupal doesn't allow me to write a blog entry using a simple svn commit, with magic commit hooks fixing everything. Let's keep things as they are.

Eddy Petrișor: tilting at windmills - the NSLU2 issues

It turns out I was playing Don Quijote when I was trying to fix the reset issues I had with my slug.

Of course, I was suspecting the USB rack for the issues, but the issues never showed up on the laptop... until now.

I decied to temporary use a USB stick for the FS and started copying files over to the stick. During the copying the rack disconnected and everything became more clear. I was tilting at the windmills all the time.

BTW, be smarter than myself and just change the UUID to mach the old one instead of regenerating the initrd and reflashing it:

tune2fs -U the_uuid_of_the_previous_root_partition /dev/sda1


Oh, next on the agenda will be to use my ipod mini as a hdd for the slug in order to prevent ruining the stick... And another thing, total silence is really nice, even if the rack was not that noisy.

Jeff Bailey: ... and the packers descended

Our place this morning was so calm and peaceful. Angie was cooking muffins. Then the packers showed up at 8am. It's 2.5 hours later, and we're now surrounded by boxes. In another 24 hours, the computers will be shut down, the cable modem returned, and the moving trucks will show up.

Two weeks ago when we left Montr al for visiting family and going to UbuntuLive, we knew that we only had a couple days left back here, but the reality is now setting in. From here we'll go to Opus, the Unitarian Universalist young adult conference at which we're two of the four cooks. From there, we head south, fetch a rental car, and start our one-way drive out to California.

Crazyness!

Junichi Uekawa: muse-el breakage or mine.

muse-el comment handling has silently changed, or rather, it was announced in one of its changelogs.I had several calculations hidden in ; notations, and every reference to the value defined within the comment turned into "Invalid Lisp Code".Apparently, it no longer evaluates what is within ; comment. Tokyo Area Debian Meeting announcement page has been broken for a few days due to this problem.Apologies to those who were affected by this breakage.

Russell Coker: Blog Memes

A common pattern in blog communication is referred to as a Meme. Here is one example of the commonly used definition of the term as applied to blogs. One common factor that doesn’t seem to get directly mentioned much when people define the term (but which always seems to be mentioned in passing) is the idea of tagging people. So the definition of a meme as applied to blogs seems to be a silly question that you answer in a blog post and then request that some other bloggers (usually 5) answer as well. At the end of this post I have included the dictionary definition of the term (here is the Wikipedia definition). I believe that it is incorrect to call a question such as “which superhero do you most identify with” a meme. Instead I think that there is a Memeplex associated with such posts. One meme is that when someone “tags” you (requests that you answer a question) it should be considered an honour (someone in the blog-sphere likes you enough to ask you random questions in a public forum). Another meme is that such discussion is a good thing (although an increasing number of people in the more serious part of the blog-sphere oppose this). A final one that is apparent to me (I’m sure that there are others) is that so-called memes and lazyweb posts are the same thing (I believe this to be wrong). I believe that lazyweb posts if written about interesting topics can contribute significantly to the community knowledge base. I also believe that chain lazyweb posts (here is a link to the only such post I’ve made so far) can also contribute if created in a sensible manner. Chain posts that don’t require any thought or input from the person re-posting them (EG “please post this message to all your friends so that they can know of the terrible war/famine/earthquake/whatever in some foreign part of the world”) are of course quite useless (you can make a post of links once a month if you want to spread the news about such things). Now I agree that some amount of conversation among bloggers in a community that is personal and not directly related to the main topics of discussion is good for building the community. From Jargon File (4.4.4, 14 Aug 2003) [jargon]: meme
/meem/, n. [coined by analogy with gene’, by Richard Dawkins] An idea considered as a replicator , esp. with the connotation that memes parasitize people into propagating them much as viruses do. Used esp. in the phrase meme complex denoting a group of mutually supporting memes that form an organized belief system, such as a religion. This lexicon is an (epidemiological) vector of the hacker subculture’ meme complex; each entry might be considered a meme. However, meme is often misused to mean meme complex. Use of the term connotes acceptance of the idea that in humans (and presumably other tool- and language-using sophonts) cultural evolution by selection of adaptive ideas has superseded biological evolution by selection of hereditary traits. Hackers find this idea congenial for tolerably obvious reasons. PS This evening I had planned to go to a LUV meeting and see my friend Andy Fitzsimon (blog) give a talk about Inkscape (for which he is famous). I also had a day off work, so it was going to be a day of non-stop fun. But instead I got some sort of cold/flu, stayed in bed for much of the day, missed the meeting, and was late in my blog post. This sucks.

Andrew McMillan: Really Simple CalDAV Store - August 2007 Status

Having taken time out to go to the other side of the world to attend DebConf 7 in Edinburgh, and then after spending some time with my family, I have been somewhat distracted from things CalDAV for a wee while now. There are signs that I will be able to put a few more evenings and weekends into it in coming months. Current Status With the release of 0.8.0 I believe it is quite a usable application for shared group calendars. We use it at Catalyst for about 80 staff and, while we're not heavy calendar users, it manages without any noticeable performance problems. There have been an impressive number of downloads from Sourceforge, as well as substantial downloads from my Debian repository, and I believe that the program is in tens, if not hundreds, of installations. Future Plans In the immediate future I want to get the basic framework for querying properties about the owner of a calendar or a set of calendars. This will be used by Mozilla soon during their configuration of a new CalDAV source, and I think that Apple iCal probably uses them already. This is partly done, but it's implementation has been slowed by the necessity to refactor the handling of the REPORT method in general to make the code more modular and readable, and to support queries and properties in a more general manner. The refactoring of the REPORT method handling is in place now, so moving on to the handling of DAV:principal objects should become fairly straightforward. I may end up with a fair bit of quiet, undistracted time over the coming weekend so if I can get in the 'zone', it may get done, and we can start rolling towards a release 0.9. Release 0.9 will have a new name. One from the cast of thousands that have been submitted to me so far, or one that I will hastily think up in between, but the next released version will not be called RSCDS any longer. The main goals for further into the future are: Interoperability I think that RSCDS does fairly well on the interoperability front. Unfortunately I have no access to the preview of OS 10.5, with it's native CalDAV client (though I have been told that it works with RSCDS). Likewise, other commercial CalDAV clients aren't available to me for testing either, so I have concentrated my efforts on supporting the featureset used by the various free CalDAV clients. My initial work focused around supporting Evolution, in particular, but with the recent effort put in by the Mozilla Calendar team the primary interoperability challenge is to enhance RSCDS to support their areas of development. If I could see how the OS 10.5 client behaves, too, I believe that would help identify a few points to extend, as well as suggesting some future directions. The best place to review interoperability would probably be at the CalConnect Roundtable 10 but I think that without some sponsorship for airfares I probably won't be able to make that. Maybe next time. Specifications Compliance As I read, and reread, the CalDAV (and DAV, and HTTP, and ...) RFCs the compliance with the various specifications improves. Recently I have put a lot of work into the calendar-query report, in particular, which means it now supports querying against arbitrary properties much more comprehensively. This is important because some of the client software is starting to do arbitrary queries also, and it is inevitable that queries for the classification of events, or the percentage completion of todo items will become more common. And now I notice that there is a new version of DAV in RFC4918, though not too many changes as far as I can see. The intent of this release is mostly to clarify, and slightly to extend, primarily in order to improve client interoperability. Coverage of Related Specifications In terms of general calendaring activities, the biggest hole in the CalDAV specification at present is standardisation around the location of other people's schedules. The current draft of the Scheduling Extensions to CalDAV appears to address that, and a lot more besides. I expect to start working on parts of this at some point, but perhaps not sooner than I see a client which starts using it, or when it is ratified, whichever occurs soonest. Documentation The documentation is OK. The wiki, in particular, is a reasonable resource for resolving problems (I believe), but it would be good to have some documentation of other things. One area that could do with enhancement is some documentation of how to check out a copy of the code, and how to provide patches back to me. Even better if other people can maintain their own trees which I could pull patches from, since we're using a distributed version control system (Git) to start with. Configuration The administration interface for RSCDS is OK, but could do with a few improvements to make it more usable. Really there are not a lot of reasons to be in the administrative interface, so these improvements should be relatively few, and relatively easy. This would be a good area for someone interested in helping out to become involved, because it does not entail reading large reams of RFCs, or watching tcpdumps scroll past for the debugging. Installation One thing that I have done right, I believe, was to provide the software from the beginning in a packaged form to make the installation easier. Although the software is packaged for Debian, however, it has not yet been uploaded to the archive because I have been waiting for the webapps-common package to enter Debian so I can use that for configuration. I think I have waited long enough though, so I will upload the next version to Debian for use by a wider audience. Security Security has always been a focus for me and I have had the code reviewed for any obvious security flaws. If any particular vulnerabilities are found they will be addressed with appropriate haste. Retrospective I've been working on this for a little over a year now, and I think I have largely met my goals for the project. It has certainly been an educational experience for me, and the effect of this work on other projects that I also participate in has also been valuable. Any new open-source project is always at risk of the developer losing energy and interest, but I believe this one has made it to a state where the bulk of the infrastructure effort has been done, and there are enough interesting challenges in the future to continue to keep me (at least) working on it into the future. The scope of this project is good, in that it is not at risk of expanding to take over the world. The intention behind this is simply to provide a back-end service for client software which should be very much Someone Else's Problem. In reality there have been times when I have had to get to grips with some of that client software in order to resolve problems, but those have by and large been good experiences.

Antti-Juhani Kaijanaho: I am going to rank MJ Ray low from now on

MJ Ray writes:
There seem to be some 30 or 40 voters who really dislike me, but didn’t tell me that straight, preferring to be silent then vote me down. Are you cowards, or what?
This displays such an antipathy against secret ballots (which protect voters from social pressure, not to mention coercion of various degrees of severity) that I now consider MJ Ray an unacceptable candidate in any future election where I am enfranchised. By the way, since the election MJ Ray discusses had no None Of The Above option, there is no way to determine if his low rankings were due to dislike or just that there were better candidates. Added later on the same day:
MJR has responded to this post; his response is linked and reproduced in the comments section. MJR seems to have missed the subtle hint that his cowardice statement is a form of social pressure itself. In fact, he continues and elevates the pressure in his response, implying that if one is afraid of him, one should not vote (presumably, at least not ranking him low). That these statements are given after the vote has closed is a mitigating factor, but it does not absolve him, as the statements are applicable to any future elections where he is a candidate. I m now even more convinced that MJR belongs in the bottom of any ranked vote from me.

Next.

Previous.