Search Results: "ag"

22 July 2008

Russell Coker: Bad Telstra

77020 packets transmitted, 18029 received, 76% packet loss, time 77049435ms
rtt min/avg/max/mdev = 20.026/130.848/2245.752/287.550 ms, pipe 3 Above are the ping results from pinging my server (hosted on a business DSL connection). Telstra stuffed up and appear to have entirely disconnected DSL for a few suburbs (based on reports from a client who has several clients in that region that all went offline simultaneously). It’s affected at least two ISPs (every DSL service uses Telstra’s backbone). The above ping results show almost 17 hours of outage, but it was really more like 18 (I didn’t start pinging until I realised it was down). Telstra’s response to the problem reports (which my client raised via two ISPs) was that it would take until the end of the next business day. The problem was reported at 10AM, so Telstra was apparently happy with two entire business days of outage. I think that the root cause of such problems is the terrible performance of Sol Trujillo [1] (or “Telstra’s Sole True Hero” as suggested in Crikey [2]). Under Sol’s leadership Telstra stock has not performed well (it’s a monopoly - it’s supposed to reap money), it’s lost market share in every area where competition is permitted and it hasn’t made it’s customers happy. Sol is taking an approach to business that works well for some big companies in the US (and for the mining and automative industries in Australia). He has been trying to force the government to extend the Telstra monopoly with the Fibre To The Node (FTTN) plan [3]. His idea was to have small Telstra boxes (nodes) spread around the suburbs with short copper runs to each home, each node would have absolutely no spare space for other ISP equipment and therefore the other ISPs would not be able to provide a service. The claim was that FTTN was needed for decent performance but ADSL2+ has been shown to work well in the areas where FTTN was proposed. Telstra even sent out brochures to stock-holders encouraging them to lobby members of Parliament on behalf of Telstra’s rent seeking [4]. However Australia is not like the US and this didn’t work, they couldn’t even get Telstra stock holders to support such plans. Speaking for myself, my interests as a Telstra stock-holder (and I own more Telstra shares than the median stock holder) are vastly outweighed by my interests as a consumer of telecommunications services. I would like to see the government nationalise the local loop and the exchange buildings and then provide fair and equal access to all telephone companies and ISPs (including Telstra). Then we can have true competition in this market and the companies that provide the best services will win. Currently Telstra resembles one of those inefficient Soviet monopolies. We need some capitalism in the telco industry!

Axel Beckert: Blosxom 2.1.0 released

Today I had the honour to prepare and announce the first Blosxom release after exactly two years and six days. The primary cause for the Blosxom 2.1.0 release date this week was to get our development efforts of the last two year into Debian Lenny with a nice version number (i.e. one without snapshot dates in the package version ;-). The second biggest cause was that it just was time. But Debian Freezes always give you a good kick in the ass. ;-) Rhonda plans to prepare an updated blosxom package for Debian during the day. (Update 25-Jul-2008: Packages are available.) So if Planet Debian is broken in a few days, you know whom to blame: Me and my last minute bug fixes. ;-) But since you seem to be able to read this, the release shouldn’t be too broken – because of course my blog already runs the very fresh Blosxom 2.1.0 release. ;-)

Jan Wagner: Alien 2.0 released

In case you missed it, alien 2.0 was final released (5 weeks ago).
alien alien2

Michal Čihař: Phone synchronisation, finally

One of long standing things on my todo list was to make synchronisation work from my cell phone (Sony-Ericsson K750i) to some PIM application on Linux side (as a GNOME user Evolution is the natural choice). I tried it several times but it never actually worked. Today I gave it yet another try and I finally succeeded on first attempt :-). As a first step I just wanted to make a backup of all things. Gammu can do it quite well and it's the tool I trust for this purpose:
gammu backup /tmp/phonebook.vcf
gammu backup /tmp/calendar.vcs
Now it's time to play with OpenSync. We will use setup guide and SyncML guide as a starting point. As I had in past problems with both sides - both phone and Evolution failed with some random errors, I wanted to go step by step. So I started with setting up phone to files synchronisation:
msynctool --addgroup file2phone
msynctool --addmember file2phone file-sync
msynctool --addmember file2phone syncml-obex-client
Now we need to configure file storage, just tell it where it should store the data:
msynctool --configure file2phone 1
And change path in your editor to something like:
<?xml version="1.0"?>
<config>
  <!-- directory path for file-sync -->
  <path>/home/foo/phone-backup/</path>
  <!-- should care of subdirectories (TRUE or FALSE) -->
  <recursive>FALSE</recursive>
</config>
Now the more tricky part comes, we need to set up phone end:
msynctool --configure file2phone 2
Fortunately we can use example from the SyncML guide and just fill in Bluetooth address (you can get it using hcitool scan) and channel (sdptool browse 00:b0:0b:fa:ce:00):
<?xml version="1.0"?>
<config>
  <bluetooth_address>00:b0:0b:fa:ce:00</bluetooth_address>
  <bluetooth_channel>7</bluetooth_channel>
  <identifier>Sony Ericss</identifier>
  <version>1</version>
  <wbxml>1</wbxml>
  <username></username>
  <password></password>
  <type>2</type>
  <usestringtable>0</usestringtable>
  <onlyreplace>0</onlyreplace>
  <onlyLocaltime>0</onlyLocaltime>
  <recvLimit>0</recvLimit>
  <maxObjSize>0</maxObjSize>
  <contact_db>Contacts</contact_db>
  <calendar_db>Agenda</calendar_db>
  <note_db>Notes</note_db>
</config>
And now we should be able to synchronise whole phonebook from phone to selected directory:
msynctool --sync file2phone
Okay, this works, let's try more complicated thing - include Evolution in the chain. The steps are the same, config file for phone is the same, Evolution plugin has sane defaults you usually don't have to touch:
msynctool --addgroup phone2evo
msynctool --addmember phone2evo evo2-sync
msynctool --addmember phone2evo syncml-obex-client
msynctool --configure phone2evo 1
msynctool --configure phone2evo 2
But now comes the tricky thing - Sony-Ericsson phones usually have something broken around notes (or it is broken in OpenSync, I don't care, simply synchronisation fails without this step) and we have to avoid synchronisation of them. This can be done by changing filter file in group we've created above (usually in file ~/.opensync-0.22/group2/filter.conf):
<?xml version="1.0"?>
<filter>
  <note/>
</filter>
And finally we can start the synchronisation and it should work:
msynctool --sync phone2evo
You can also GUI multisync0.90 to do the configuration and start synchronisation, but it is not much different, you also still have to edit XML files.

Stefano Zacchiroli: reminder: Homepage pseudo fields are GONE

go fix your ancient Homepage pseudo-fields, you lazy maintainer! ... or I'll kill a kitten for each homepage URL I found in long package descriptions. Homepage pseudo-fields are gone since long, the proper way to document upstream homepage is now to use a real Homepage field in the source stanza of debian/control. Still, as a page of mine has been documenting, we still have more than 1100 packages (dd-list) which are using the old pseudo-field which clutters the long description, is often badly rendered, and stays in the way of who works on long descriptions (e.g. translators). The transition from the old pseudo-field to the new field is being monitored on our wiki. Please, pretty please, take some time to convert your old pseudo-fields: it's quick, easy, and helpful.

Isaac Clerencia: Untangle yourself from ethics

A workmate called my attention today upon the fact that when you search for ‘ebox’ or ‘ebox-platform’ in Google you get some sponsored links from our fierce competitor, Untangle. Here is a screenshot of the ad:
Easier than eBox
You can see a full screenshot of the search too. On one hand, I am kind of honored about the fact that a California-based company which has raised almost 20 million dollars in venture capital and has over 30 employees is targeting us (a self-funded company) in such an explicit way, it must mean we are definitely on the good track :) On the other hand, this reminds me of the time when Ximian started to play with KDE keywords … yeah, we both are developing an open-source product, but one of us doesn’t care about ethics that much. BTW, we have a new shiny website :P

Tollef Fog Heen: Kernel patches and the TEMPer USB thermometer

Today, I submitted my two first patches to the kernel. One is fairly trivial (remove a USB ID from the pl2303 driver), the other is a fixup of a patch from some other guy, which adds support for DTR, RTS and CTS to the ch341 driver. Yay, hopefully they'll get accepted. The reason for this journey into kernel land is I got a TEMPer USB thermometer in the mail yesterday. After a fair bit of digging around, I found some source code to drive it from C# and Windows. I wanted to poke at it from Linux and C. After more poking, I found it's an I2C device connected to the USB serial adapter, where you talk to it by twiddling DTR, RTS and CTS. The C# code was fairly easy to port, so now I can get temperature readings from the command line. The code is a quick hack, but I guess it might be interesting to some people. Oh, and the calibration seems entirely off (but it was off in Windows too), so feedback on whether it's more accurate for other people would be appreciated.

MJ Ray: LugRadio Live Event Review


LUGRadioLive 2008 by sheilaellen (cc-by-2.0) This weekend, I learnt lots of things while at LugRadio Live in Wolverhampton. One thing was the surprising delay between posting something on this site and it actually appearing in the feed on my mobile phone. Another is that I can’t post to my new blog hosting from my mobile phone, which I’ll debug Real Soon Now. So, this is a bit later than when I first wrote it and it’s now one post instead of seven or so… Thanks to some unexplained delay travelling through Birmingham, I walked into LugRadio Live during the Introduction. The venue was generally pretty good, but the stage obstructed the entrance the acoustics in the atrium only seemed to work for the four gents. No idea what they said: I got past the stage into the audience and it finished almost immediately. For the first talk session, I went to see Rufus Pollock of Open Knowledge Foundation introduce a plan for the Comprehensive Knowledge Archive Network. Seems like a good idea. I’ve tons of questions, but I can’t quite get them into words, I don’t know when I’ll have time for this and I’m not sure they really matter anyway. I think I’ll mention CKAN to some librarians anyway and see what they make of it. I expected Emma Jane Hogbin’s “Form an orderly queue, ladies” to start an argument with the usual chix silliness but I was pleasantly surprised by how reasonable the advice was. In fact, the speaker also criticised the “chix” movements, although it appeared she participates in some women-only clubs, so not a 100% win for equality there. Sadly, much of the talk has been overshadowed in my mind by the memory of a giant furry racoon walking in unexpectedly, so I’ll probably grab the video of the LRL-USA version sometime soon. James Hooker’s talk titled “Taming the dragons — entrepreneurship and VCs” launched venturex as described on his own site already (along with more talk descriptions). It was an interesting demo, but it requires hackers to sell some votes in their companies to Venture Capitalists, which I believe is a bad thing for free software developers to do. We need to look more at a form of social entrepreneurism.</soapbox> I tried to ask a question, but the terrible atrium acoustics did funny things with my not-so-good hearing and I lost my way somewhat. At the end of that talk, I got chatting to an interesting web developer from Leicester who also forsook The Gong-a-Thong Lightbulb Talk Extravaganza and headed up to the Lightning Stage for Robert Collins and the Bzr talk. As well as some glimpses of how it’s changed since forking from tla, it was interesting to see a real (imperfect) demo and a non-Emacs version control GUI. The web interface for casual users to submit patches sounded very interesting and I also learned that some people pronounce “svn” like “Sven”. Most things that Robert thought were benefits sounded like drawbacks to me, so I’ll stay with git for now. Steve Lamb’s Green IT talk was the last presentation I saw. This talk really disappointed me because it seemed to be skewed towards the corporate governance nonsense instead of seeing Green IT as a vital pragmatic step, mentioning points I’d seen put more clearly elsewhere, as well as advertising Vista virtualisation and some panoramic webcam from Microsoft (who employ him) that doesn’t work with any free software, according to a deserved verbal shoe-ing in the Q+A. Only thing I remember that seems useful: charging from USB is more efficient than using wallwarts. Is that right? Finally, the main event: LugRadio Live and Unleashed. It opened with the shock announcement that LRL will continue into 2009, as announced elsewhere already. The rest of the madness will presumably appear online shortly and I don’t remember it well enough to do it justice… A tech conference crossed with a rocking gig by the strangest boyband ever, with a cheerleading racoon and some very cool people. I’ll try to be at LRL 2009. Will you be there? Were you at LRL this last weekend?

Maximilian Attems: OpenVZ Debian Linux images

Thanks to the Virtuzzo developers for forward porting the OpenVZ patch to 2.6.26. It uses a lot of the already merged namespace features (For interested peoples linux-next carries interesting sysfs patches). The openvz upstream merge statistic is impressive. The namespace solution allows low overhead, while still running multiple Linux distributions in individual containers on the same box. Control over the network vitalisation is gained as a resource management for CPU power, I/O bandwidth and disk space. Live migration including snapshotting is possible too. The Debian 2.6.26 Linux images will feature not only better Xen vitalisation support, kvm port to new archs, but also an opvenvz flavour. Please don't forget to install proper vzctl userspace support as the correct dependencies have not yet been added. Supported archs will start with both x86 and the ia64 archs. Tomorrows linux-2.6 Debian trunk snapshots will already build openvz. Thanks for your feedback. P.S.: 2.6.26 is the targeted kernel for Lenny, we hope to convince Debian installer people to pick it up soonest - 2.6.25 is a not so bad backup plan as release hasn't fully approved 2.6.26 before extensive unstable testing.

Russ Allbery: Tired now

Last week, Stanford University hosted Cartel, a gathering of several schools that share similarities of infrastructure and IT problems. I was one of the coordinators, handled most of the content for the web site, helped prepare the agenda, and presented for three of the segments. It's considerably more work hosting and coordinating one of these than just attending one, even with the travel. Jeff Altman and Derrick Brashear, the other two OpenAFS gatekeepers, were also in town for half of Cartel and stayed through Friday, so we went out to dinner several times, played a great deal of Fluxx, talked about the state of the world, and caught up. This was all great and very informative, but I'm also an introvert, which means that no matter how much I'm enjoying social interaction, it's also extremely tiring. I'm still fairly wiped; I'm getting more done (and got more done last weekend) than I really expected, but I expect I'll be paying the price all the way through this week. (And then I have more company from out of town that I've been looking forward to for months, but which will then take its own toll, which means it's likely I'm going to be exhausted until well into August.) So, I'm currently looking at all the things I want to do and trying to tell myself that not only is it okay that they're not all going to get done right away, but I need to make a concerted effort to take time to relax, try to work less than 40 hours this week (after working 56 last week), and spend more time reading. Of course, writing reviews is one of the other things that I'm currently a bit behind on.... Debian is freezing for lenny next weekend. If I have a few moments, I may do final uploads of OpenAFS (to clarify that hppa isn't a supported platform) and kstart (a long-awaited new upstream release that adds a flag saying not to get forwardable tickets, needed if one has a krb5.conf configuration saying to get them and a site policy that says you can't). gnubg could stand another upload, but I probably won't get to that. The Shibboleth packages are all in good shape except that they don't all have complete copyright files for all the Autotools helper stuff, which is very not important. Thankfully, the freeze is basically meaningless for Lintian, which will continue apace (and Adam D. Barratt continues to take much of the load off by doing a ton of commit work), and means that Debian Policy work should actually slow. My intention is to make the next normative release of Policy shortly after the lenny release, which gives us plenty of time to work on more changes for the next version. I plan on somewhat ignoring both for a bit while I catch up on other things, since I released Lintian 1.24.2 on the 13th (which I see I never announced here — whoops). In other news, I finally started the process of moving services from systems I own and have to fix to systems where someone else owns the hardware and has to fix it when it breaks by buying a VM from Panix. I still need to sort out my DNS situation and get more direct control over my zone file now that I have somewhere I can run my own DNS server so that I can start moving services there, but so far, so good. I'm extremely impressed by their service and capabilities and already have all of my Git repositories on the system and gitweb set up once I get DNS updated.

21 July 2008

Clint Adams:

This is the night of second-hand thoughts. Oh, the shame. I'm gonna do this in mostly-chronological order. Mostly. I vaguely remember the first great meal I had in Paris. I got off the plane, went through immigration and customs, hopped on the RER, got out and dragged my suitcase to Le Chat Gripp . I walked through the door in my T-shirt and jeans, and said well, I don't remember what I said, but I ended up getting a table and ordering the tasting menu. I don't remember very much about the food, but I remember that the waiter had to wake me up between courses. I've kinda had a thing for tasting menus ever since. Tonight I made a reservation at a fine dining establishment that was advertised as having a couple of tasting menus. I wasn't going to commit myself to a tasting menu, but there was a good chance I would find it irresistable. I timed my departure pretty well, and after walking the 2.5 miles to the restaurant, I was only a couple minutes early. Now the funny thing about this is I did not happen to notice that I had entered Molecular Gastronomy Hut. The signs outside did not say Molecular Gastronomy Hut, neither in cuneiform, hieroglyphs, nor any language I could read. The menu did not advertise the fact that this was Molecular Gastronomy Hut. Had I known that this was Molecular Gastronomy Hut, I would have not ordered the tasting menu, especially since I was not hungry and should probably have not even eaten a whole course. Had I known that the wine pairings would only include two reds, I wouldn't have ordered those either. Normally I expect wine pairings to include a white. It's the thing to do; it adds contrast. You drink it and get it over with and then you enjoy the rest of your meal. This had at least three whites and one ros . Mother of God. For the moment, though, I had no foreknowledge of the wines, and was was entranced by the knives, which were twisted such that if the handle was lying flat on the table, the blade stood vertically. Not only was this incredibly distracting, it seemed to have some practical value; if there were foodstuffs on your knife, they would remain elevated and not touch the tablecloth. Anyway, the food comes out, course by course, wine by wine. I wonder if Richard from Top Chef is hiding back in the kitchen. There are random foams and gastriques lying conspicuously on my plates. My second course had a lemon sorbet sitting on top of various types of vegetable matter. My third course involved arthropods. Ever wonder what to pair with fried arthropod? That's right, ros . My fourth course was actually tasty, much to my surprise. It was a pumpkin flower cappuccino. It is hubris to call it cappuccino, but they did and I am going to maintain the tradition. It tasted like warm infused buttery goodness, even though I was picking insect legs out of my mouth while drinking it. You may or may not be surprised to learn that the lemon sorbet made a reappearance in a later course. The waiter recommended mixing it with the other ingredients. Tom Colicchio was hiding in the back of my head asking why, if it was meant to be mixed, wouldn't they serve it mixed. I am forced to agree. The only other thing worth having was the cheese plate. It was populated with cheese I had never had before, and fruit concoctions to go with each. Most of the cheese were nothing special, but one was orgasmic. No, I'm not going to tell you what it was. Oh, all right, it was the middle one. One hundred fifty-six courses later, I was asked if I wanted any coffee. I didn't really want caffeine, but as I didn't want to sabotage the experience, I acquiesced and consented to an espresso. I'm not sure how I was understood, as by this time I had stopped speaking the local language and was presently shouting about bacon-burger dogs, the Huxtables, and Freebird. Then after coffee and being ignored, I asked for the check. Surprise, surprise: there was an additional dessert course to go. Didn't I look foolish? The bill came out to about half the country's GDP. The last time I had seen that many digits was when a bunch of hipsters tried to calculate while spaz-dancing to Fischerspooner and playing Space Channel Five. I wondered how it must feel for one of those guys who decides to order all kinds of extravagant room service in a luxury hotel right before committing suicide. After I paid, which seemed to confuse them a bit, they offered to call me a cab. I refused politely several times. I don't like cabs to begin with, aside from the whole plutocrat-fatcat I-might-as-well-get-a-maid-and-a-butler-and-a-valet feel to them, and the practical aspects of the drivers being douchebags. I had just spent a ridiculous amount of money on food that wasn't worth it, and I saw no reason to add insult to injury by paying for a taxi. It could probably have been $10 or $15 more. Mother of Christ. So I walked. It was only four or so miles to my bed, and I passed the time by singing songs of cormorants and racial disharmony and seventeen-year-old prostitutes and the time the Rescue Rangers got sentenced to maximum-security prison. All in all it was a terribly unpleasant contrast to the happy song about alfajores I was singing before dinner. Mmm alfajores.

Martin Michlmayr: Daily installer image available for QNAP TS-109, TS-209 and TS-409

Daily installer images are now available for the QNAP TS-109, TS-209 and TS-409. This means that complete installations of Debian testing are possible now. You can consider the daily image as a beta release of RC1 of the debian-installer for Debian lenny. It should only be used by experienced users and only if you can make a serial console in case something goes wrong. As the name suggests, the daily images change on a daily basis and they install Debian testing which also changes on a daily basis (although testing should be fairly stable since we're close to the freeze of testing in preparation for the release of Debian lenny). If you install Debian with these installer images, please send an installation report to debian-boot send an email to me so I can let you know in case there are any important news you should be aware of. There is a web site now with complete installation instructions and other information about Debian on QNAP Turbo Station. If you have any questions or suggestions, please let me know.

Runa Sandvik: Solskogen 2008: Shades in the sun

Friday morning was not much fun compared to the rest of the weekend. I rushed to the bus stop only to wait in the rain for ten minutes. All of a sudden a bird decided to dump its crap on me, leaving me with no jacket and only one pair of pants for the whole weekend. And then, just to top it all, the bus driver failed to see me - meaning I had to wait twenty minutes for the next bus. It quickly became much better once we got to Oslo; picked up a friend at the airport, met up with some other people at the train station, bought a tent and even managed to get on the train to s in time. During the weekend I learned that Kock sf l ny l is super cute, that Norwegian girls speaking Swedish sounds funny, that I should bring more warm clothes next time and to stay away from birds in the future. There’s a lot of moments that I’m never going to forget. Like spending four hours putting up a tent, the Danes dropping their pants, the free-beer-button, the moomin laptop and, of course, Duckers in a girly Outracks shirt. And there’s also one moment I won’t forget - but would like to; being hit on by a drunk, Finnish guy (Hi Sauli!) who wouldn’t take no for an answer. I must admit that I missed the wild compo because sleeping on the floor seemed like a good idea at the time. Even though every bone in my body hurt the next morning, I don’t regret it. Maybe I’ll just blame that on free alcohol and the organizers being late with the compos. I did have a great time with awesome people. The party was everything I hoped for and more.

Nico Golde: pwnie award nominations published


Finally the pwnie award nominations are out, a bit late though.

Of course we also got our nomination for the infamous openssl issue in the Most Epic FAIL category as well as one nomination for Luciano for the discovery of this in the Mass0wnage section :/

I nominated Wonderware (I wrote about that before) in the Lamest vendor response category, looks like it has been accepted.

wordpress also got its place in the Mass0wnage category:
An unbelievable number of WordPress vulnerabilities (CVE-2008-*)

Discovered by: everybody who cared to look

It seems like hardly a week goes by without a new vulnerability in WordPress or one of its many plugins. Many of them are actively being exploited to own popular WordPress blogs and use them to serve spam or client-side exploits to unsuspecting visitors. The popularity of WordPress combined with the abysmal security practices of WordPress plugin developers places the entire Internet at risk and is worty of a nomination.

138 reported vulnerabilities since 2004 referring to MITRE, shocking!

Joey Hess: graphical annotate

I'm envisioning a graphical app that displays a file. Like a pager, the up and down arrows move through the file. But the left and right arrows move through time. As each successive change to the file is displayed, the committer's name appears in a column to the left of the lines changed in that commit. Hover the mouse over it to see the commit message. Names of old committers will fade out as time advances, but still be visible for a while. (A menu option will disable the fade out entirely.) A nice bonus feature would be to allow opening multiple windows, with multiple files from the same repo. Moving back and forward in time would affect them all at once. A nice, but getting harder feature would be to have a horizontal timeline at the bottom, including branches, so you could click on a specific branch to visit it. (Without this, when passing a fork or merge point, it would have to choose a branch heuristically?) A tricky subtle feature would be to attempt to keep the current code block centered in the display as lines are added/removed from the file, adjusting scroll bar position to compensate. There seems to be a gannotate for bzr, that may do something like this. Offline so I can't try it. Google-and-caffine-fed update: bzr gannotate is closest to what I envisoned, though without a few of the bonuses (fade-out, smart scrolling, multiple files). qgit's "tree view" includes the same functionality, but the interface isn't as nice.

Joey Hess: graphical annotate

I'm envisioning a graphical app that displays a file. Like a pager, the up and down arrows move through the file. But the left and right arrows move through time. As each successive change to the file is displayed, the committer's name appears in a column to the left of the lines changed in that commit. Hover the mouse over it to see the commit message. Names of old committers will fade out as time advances, but still be visible for a while. (A menu option will disable the fade out entirely.) A nice bonus feature would be to allow opening multiple windows, with multiple files from the same repo. Moving back and forward in time would affect them all at once. A nice, but getting harder feature would be to have a horizontal timeline at the bottom, including branches, so you could click on a specific branch to visit it. (Without this, when passing a fork or merge point, it would have to choose a branch heuristically?) A tricky subtle feature would be to attempt to keep the current code block centered in the display as lines are added/removed from the file, adjusting scroll bar position to compensate. There seems to be a gannotate for bzr, that may do something like this. Offline so I can't try it. Google-and-caffine-fed update: bzr gannotate is closest to what I envisoned, though without a few of the bonuses (fade-out, smart scrolling, multiple files). qgit's "tree view" includes the same functionality, but the interface isn't as nice.

Matthew Garrett: The fallacy of the completely inclusive community

Emma Jane Hogbin gave a presentation on the gender gap in free software at Lugradio Live this weekend. One of the central messages was that a great deal of how to avoid putting women off computing can be distilled down to "Don't be a dick". This ties in well with Mako's restatement of the Ubuntu code of conduct as "Be excellent to each other" (a wonderful phrasing which demonstrates that Bill and Ted's Excellent Adventure is the most philosophically worthwhile film that Keanu Reeves has ever appeared in, and certainly not The fucking Matrix) and led to my 5 minute rant on why I hate the Linux community slightly later in the day, but does leave a certain problem. What standards are used to define whether given behaviour is dickish or not? The comments here show that there's disagreement even within a single sub-community of the larger free software world. Ben suggests that the reaction to perceived inappropriate behaviour is perhaps even more discouraging than the original behaviour, suggesting that bitching about things that offend you is dickish behaviour in and of itself. How do we decide whether someone is being a dick or helping the community? Is lack of tolerance a form of exclusionary behaviour?

This topic is actually one of the issues discussed in the Geek Social Fallacies, but here's a nice easy example. Would tolerating planet posts encouraging the eradication of the Jewish population be inclusive or exclusive? I suspect that most people would agree that it wouldn't be acceptable behaviour, which leads us to the next question. Why? There's two obvious arguments here. The first is that at a community level we have some form of rough moral consensus that advocating genocide is Just Wrong, and so criticising Nazis is obviously the right thing to do. The second argument is more pragmatic than philosophical - alienating millions of people in order to avoid alienating hate groups could be considered to reduce our potential contributor base in an unfortunate way.

I'm a fan of the second argument. The example I gave is emotive and relatively recent history has resulted in people tending to be pretty uniform in considering genocide to be a bad thing, but many other cases aren't clear cut. What I consider to be objectification of women is seen by others as appreciation of natural beauty. What I think of as sexist jokes are perceived by others as acceptable humour. When I advocate intolerance of certain behaviour, people are going to see me not having enough tolerance. So we end up in a situation where people make the "We should all just get along and be tolerant of each other" argument, which sounds fine but is fundamentally flawed in one significant way.

Advocating tolerance excludes the intolerant.

The reason people fail to see this is that it doesn't sound like a flaw. If you ask people whether we need to support intolerance, the immediate answer is probably no. But by advocating exclusion of intolerance, you're excluding all those who have good reasons to be intolerant. You're excluding the women who don't want to feel that the community sees them as a pair of breasts attached to some legs. You're excluding the ethnic groups who would prefer to avoid racist slurs or ethnic stereotyping. Telling anti-fascism protestors that they're being intolerant isn't likely to endear you to them. Advocating tolerance is telling the intolerant that they're wrong and should just deal with whatever it is that makes them unhappy.

So, ironically, tolerating certain types of intolerance is probably required in order to avoid alienating many potential contributors. That means some way of deciding what kinds of behaviour are acceptable and which are unacceptable. In the absence of either pre-existing community consensus or some philosophical breakthrough that allows unambiguous determination of the "rightness" of a given action, I'm going to suggest that we look at it from a pragmatic viewpoint. How many potential contributors do we discourage by criticising a certain type of behaviour? How many do we discourage by tolerating it?

The fallacy of the completely inclusive community is the idea that it includes everyone. The reality is that a certain level of social exclusion is required in order to include a wider range of people. So don't criticise people purely for criticising someone else's behaviour - make an argument for why that behaviour benefits the community. And when you see behaviour that you think discourages others, call people on it. Even if nobody's behaviour changes as a result, you're sending a signal that not everyone in the community agrees. Sometimes all people want is to know that there'll be some people on their side.

But, above all, try not to be a dick.

Joachim Breitner: One Week with an OpenMoko Freerunner

About one week ago, I received my OpenMoko Freerunner. This is an openly developed mobile phone that runs purely on Free Software. So this is what I have to tell about it.The hardwareIt was smaller than I thought, and is quite light. My girlfriend says it s ugly, but I m fine with the look of it. Besides being a GSM-phone, it comes with some nice gimmics: GPS, accelerometer, WLAN. The touchscreen works fine, although I don t have anything to compare it with.The softwareThe system it comes with, even after upgrading, is still very rough. It mostly works for doing phone calls and SMSs, but there are a number of unsolved quirks that prevent me from using the Freerunner as my sole phone for now. The suspend mode is left too often, resulting in a battery life of about eight hours, and there are issues with the audio for the conversation partners, who will hear static and echoes. But, as this is free software, there is hope that this will be fixed eventually.DevelopmentThe OpenMoko distribution is based on Openembedded, which uses bitbake for building software. So if I got it right, and this is not sure, because documentation is rare and spread, there is the git repository at git.openmoko.org, which is a copy of the openembedded git repository. This contains bitbake recipies for all the packages, which includes where they can be downloaded, the package metadata (such as dependencies and version numbers) and sometimes patches. These recipies reference upstream tarballs or subversion URLs. For the native OpenMoko applications, the source is in the OpenMoko subversion repository.One of the suggested ways of compiling software for the FreeRunner is by using a toolchain tarball, that can easily be extracted somewhere and used to build the software from the subversion repository, or other (hopefully autoconf ed) software. This builds the binaries, but does not produce proper .ipk files, so no version number or dependencies.The other way is the full openembedded setup, made easy using the MokoMakefile. This, automatically, fetches and builds everything needed for the cross compiliation and all available packages, producing the same output as can be found on the openmoko servers. Setting this up requires about 6 gigabytes of storage and takes over a day the first time, but then hacking the phone is relatively painless, as it resolves dependencies and is self-contained.The communityFor a free software project, the state of the community is very important. The OpenMoko seems to suffer from a rush of interested people on the mailing lists, so it s hard to follow real development in a mass of frequently asked questions and nice ideas from people who have neither an OpenMoko phone nor wil do any coding.On the other hand, it s not easy for new contributers. I have written some code that make sure the phone can handle numbers such as 0172/123 456 instead of the official +49172123456 in the phonebook and the SMS app, something that other users have complained about as well. But no one could tell me where and how I should submit my patches, and the mail to the mailing list with the patches and the bug report is unanswered. It is not clear, at least to me, who is responsible for what part of the project quite different to what I m used to from Debian, where there is a clear list of maintainers for each package, and a well known way of submitting patches (by going through bugs.debian.org).For interested users, I have published my branch of the git repository at git.nomeata.de, and I will hopefully add more features and bugfixes later at least when I find out how to properly contribute to OpenMoko.

Benjamin Mako Hill: OSCON and More

I'm in Portland, Oregon for the week where I'll be at OSCON. I'll be giving two talks on the final day of the conference (July 25): the first will be a 15 minute keynote on Revealing Errors at 8:45 in the Portland Ballroom; the second is a full-length normal talk on Selectricity at 11:35AM in Portland 255. It will be my first long-form talk about Selectricity and I'm looking forward to it. Because myself, a few Free Software Foundation staff members including Campaign Manager Joshua Gay, and quite a few FSF associate members will be in town, we're going to hold a small FSF Associate Members event in Portland (the first outside Boston!). It's going to be in the form of a pizza party with a few small talks from FSF folk including myself. Here are the details:
FSF Associate Members (& friends!) Event
July 22nd 6:30-9:00PM
Old Town Pizza
226 NW Davis St
Portland, OR 97209
It's free and open to all but is designed to provide a forum for members and friends. If you are an FSF member, please consider coming. If you're not a member yet, please don't let it keep you away; staff will be able to sign up new members there. RSVPs to Deborah Nicholson aren't necessary to attend but would be welcome. I'll be heading to Seattle right after the conference for a few days. If you would like to meet up in Seattle or Portland this week, please don't hesitate to get in contact.

Benjamin Mako Hill: I Will Revise

Once again, Wikimania was wonderful. I gave my scheduled talk on Autonomo.us and network freedom and network services. I also filled in for a few speakers to give a "Zotero for Wikipedians" demo and to say a few words about the BY-SA/FDL work as part of a Creative Commons panel. Perhaps the most memorable part of the conference was the writing and performance of I Will Revise. A couple days before the conference, a small group of Wikipedians -- The Difftones -- wrote the song at a karaoke bar in Alexandria. We had a wonderful time leading a room full of lightning talk attendees in song and a final rendition by a massive, fully-packed, stage at the party on the final night! It's online on meta.wikimedia.org. You should feel free to revise it, add verses, and improve it!

Next.

Previous.