Search Results: "claus"

10 December 2007

Steve Kemp: You're making me live

Is there an existing system which will allow me to query Apache logfiles via an SQL string? (Without importing into a database first). I've found the perl library SQL::YASL - but that has a couple of omissions which mean it isn't ideal for my task: Still it did allow me to write a simple shell which works nicely for simple cases:
SQL>LOAD /home/skx/hg/engaging/logs/access.log;
SQL>select path,size from requests where size > 10000;
path size 
/css/default.css 13813 
/js/prototype.js 71261 
/js/effects.js 37872 
/js/dragdrop.js 30645 
/js/controls.js 28980 
/js/slider.js 10403 
/view/messages 15447 
/view/messages 15447 
/recent/messages 25378 
It does mandate the use of a "WHERE" clause, but that was easily fixed with "WHERE 1=1". If I could just have support for count I could do near realtime interesting things... Then again maybe I should just log directly and not worry about it. I certainly don't want to create my own SQL engine .. it just seems that Perl doesn't have a suitable library already made which is a bit of a shocker!

Steve Kemp: You're making me live

Is there an existing system which will allow me to query Apache logfiles via an SQL string? (Without importing into a database first). I've found the perl library SQL::YASL - but that has a couple of omissions which mean it isn't ideal for my task: Still it did allow me to write a simple shell which works nicely for simple cases:
SQL>LOAD /home/skx/hg/engaging/logs/access.log;
SQL>select path,size from requests where size > 10000;
path size 
/css/default.css 13813 
/js/prototype.js 71261 
/js/effects.js 37872 
/js/dragdrop.js 30645 
/js/controls.js 28980 
/js/slider.js 10403 
/view/messages 15447 
/view/messages 15447 
/recent/messages 25378 
It does mandate the use of a "WHERE" clause, but that was easily fixed with "WHERE 1=1". If I could just have support for count I could do near realtime interesting things... Then again maybe I should just log directly and not worry about it. I certainly don't want to create my own SQL engine .. it just seems that Perl doesn't have a suitable library already made which is a bit of a shocker!

26 November 2007

Steve Kemp: You're making me live

Is there an existing system which will allow me to query Apache logfiles via an SQL string? (Without importing into a database first). I've found the perl library SQL::YASL - but that has a couple of omissions which mean it isn't ideal for my task: Still it did allow me to write a simple shell which works nicely for simple cases:
SQL>LOAD /home/skx/hg/engaging/logs/access.log;
SQL>select path,size from requests where size > 10000;
path size 
/css/default.css 13813 
/js/prototype.js 71261 
/js/effects.js 37872 
/js/dragdrop.js 30645 
/js/controls.js 28980 
/js/slider.js 10403 
/view/messages 15447 
/view/messages 15447 
/recent/messages 25378 
It does mandate the use of a "WHERE" clause, but that was easily fixed with "WHERE 1=1". If I could just have support for count I could do near realtime interesting things... Then again maybe I should just log directly and not worry about it. I certainly don't want to create my own SQL engine .. it just seems that Perl doesn't have a suitable library already made which is a bit of a shocker!

Evan Prodromou: 4 Frimaire CCXVI

Long weekend of travel and family, and now we're back on our way to Montreal. I spent most of Thanksgiving weekend with my father's family in New Jersey, where he and my mom both grew up and where 4 of his brothers and sisters still live (and their kids, and so on). We left Montreal on Tuesday afternoon, had dinner in Albany, and got down to Newburg (New York) in the early evening. The next morning we spent several hours at the nearby Woodbury Common Premium Outlets, which was about as crass and consumeristic as it sounds. But the loonie is still strong, and it's nice to buy some clothes. I especially like buying things a few sizes smaller than what I had to get a few months ago. Wednesday night we got into Hillsborough, NJ, where my Aunt Barbara lives, and visited with her and her family. Barb has four great kids -- Phillip (16?), Maddy and Vicky (14?), and Nick (13?), who are all my cousins despite being at least 20 years younger than me. When Amita June was too tired to move we hit the hay for the night, and in the morning we all hung around playing Wii sports (even AJ!), and had a hearty dinner in the early afternoon. Then we went to my Uncle Paul's for dessert, coffee, and a nice 2003 Ramos Pinto Vintage Port that we brought along. Friday and Saturday we spent at my Aunt Helen and Uncle Marty's house in Highland Park (New Jersey). They have a great 100-year-old house right by the Raritan River, and it was really nice seeing them. We had dinner with Paul and his wife Eileen on Friday night, and we saw the lighting of the Christmas tree in Princeton. Today we started the two-day trip home. It's not really that long a drive -- about 6-10 hours, depending on the route and kind of weather -- but we like to split it up into two days, since we have a 2-year-old aboard. We stopped in New York (city)/Queens to see our friend Jen for brunch at a nice place called Quaint, where I got a good house-cured salmon and Maj had an excellent bowl of granola. Amita got some nice challah french toast, which she wolfed down with the help of her kind parents. Tonight we stopped in the Pioneer Valley in Massachusetts to sleep over. I like this part of MA, and the New York Times had a recent article about its bookish culture, called In the Valley of the Literate. We had a nice quick dinner at Bueno Y Sano in Northampton, and we'll stick around tomorrow for more shopping (books! Whole Foods!) and a little site-seeing before we head home. It'll be good to be back in MTL, though. I miss my bed, and we only have a few weeks there before we're off again to California for Christmas time. tags:

Montreal SantaCon Speaking of Christmas, one of the things we'll be shopping for tomorrow is santa costumes. Friday, November 30th is SantaCon Montreal 2007. SantaCon is a world-wide anarchic cluster-together of goofballs and lunatics who go rampaging around their town from bar to mall to bar in full Santa costume (or Mrs. Santa, or elves, or reindeer, or something similar). Everyone's invited, nobody's in charge, and a fun time is had by all. SantaCon started in the 90s in San Francisco (like everything), but I never managed to go. I finally went to SantaCon in Austin in 2001, and had an amazingly good time. My pals at The Ministry of Truth have photo evidence here and here and here. There's nothing like overflowing a bar with 100 of your new best friends, all dressed like Santa, dancing and goofing off and having a good time. It brightens up everyone's day. Anyways, we'll be picking up Maj the beginnings of an outfit here on the US side of the border, so she'll be able to accessorize with her own bits and pieces. I'll probably pick up a couple of spares for friends in Montreal, too. I'm really looking forward to the event -- it should be a good time. There's a Facebook event for people who go for that kind of thing. tags:

le Sans Fil to go municipal I was excited to read (via Steve Faguy) that our beloved local community wireless group, le Sans Fil will be providing wireless to many parks and open spaces around Montreal. This is great news for Montrealers -- the city had previous vowed up the street and back that it would never have a municipal wireless program of any sort. So good deal. It sounds like it's going to be a tough job -- I don't think wiring up outdoor spaces for wireless is anywhere near as easy as doing caf s or homes. And I think it's going to be tough to show value -- after all, people are only outdoors in parks in great numbers during the few warm months of the year here. And when people are out in parks, they're not usually checking their email -- they tend to do more outdoorsy things. But my guess is that park culture will adapt to the new resource pretty well. Congrats to SF -- I think they're a great organization that's up to this new challenge. tags:

20 November 2007

Jacobo Tarrío Barreiro: AGPL

If I think that the FSF did the wrong thing, is there any way in which I can display my opposition? Can I become a negative member? Can I make an antidonation: get them to give me money? Update: In other words: I think that the AGPL is not free. Clause 13 is a restriction on usage. I’m very disappointed. (And the GPLv3 is not a high note for the FSF either).

19 November 2007

Benjamin Mako Hill: Affero General Public License Version 3

The Free Software Foundation sent out a press release today announcing a new addition to the FSF stable of licenses: the Affero General Public License or AGPL. The FSF has also published a set of answers to anticipated questions in the GPL FAQ. The first paragraph of the release explains what the AGPL is:
This is a new license; it is based on version 3 of the GNU General Public License (GNU GPLv3), but has an additional term to ensure that users who interact with the licensed software over a network can receive the source for that program. By publishing this license, the FSF aims to begin fostering user and development communities around free software web services and other network-oriented software.
The GPL is designed to ensure that users of software have access to the source code -- source is prerequisite to freedom and to the type of collaboration that has made free software successful. However, the GPL doesn't say "users" when it talks about who gets freedom; instead, it references people to whom the software is distributed. It doesn't say users for two reasons. The first is that, under copyright, "distribution" is a much more meaningful term and a powerful hook than "use" which is not, in most cases, one of the copyright holder's exclusive rights. The second is that, until very recently, having a copy of software was prerequisite to using it; possession was prerequisite to use. Things have changed. A large part of many people's computing experience involves running web applications. These include email clients (e.g., GMail or other webmails), office applications (e.g., Google Docs), social network systems, and others. These applications all run on servers -- i.e., on other people's computers. The providers of these services, the Googles and the FaceBooks, build upon, modify and improve GPL software without giving back to their users or the community that they took their software from. The AGPL was created several years ago by FSF board member Henri Poole as a way to address this issue. The license took the form of the GPLv2 with one extra clause. It was a first stab at a license and was imperfect. The language and methods were clunky and, most problematically, the license was incompatible with software under the GPL. The new AGPL is based on the GPLv3 and the extra clause has been rethought and rewritten. It has been vetted using the GPLv3 comment process and dozens of insightful comments from dozens of lawyers, hackers, and users of free software have been incorporated. The new license fixes the issues that many folks -- including myself -- had with the first version of the license. More importantly it can now be linked to GPLv3 code which makes the license a whole lot more practical. I am quoted in the release being excited about the license and I really am. I've got 2-3 major development projects (including Selectricity) which I've been waiting to distribute so that I could do so under the AGPLv3. The AGPL isn't a complete answer to the problem faced by disempowered users of web services. Without data or the capacity (in terms of servers, money, and expertise) to run web applications, the state and quality of these users' freedom remains far from clear. Thankfully, there are a whole bunch of folks thinking about what freedom for users of services might be -- it's a conversation that I'm going to push the FSF to participate in and pursue moving forward. The AGPLv3 marks a first solid contribution to the process of answering that question. If you'd like to help supporting or assisting the FSF in this effort, please consider becoming an associate member or donating.

24 October 2007

Russell Coker: Blog Ethics

Reporters Sans Frontiers (AKA RSF AKA Reporters Without Borders) has an interesting document about blogging [1]. They are specifically focussed on blogging as a way of reporting news. Their definition of a blog states that it is “a personal website” (there are many corporate blogs run by teams) and that it contains “mostly news” (most blogs that I read contain mostly technial information about computers and any “news” is mostly about the author). They also describe a blog as being set up with an “interactive tool” - most blogs are written using web-based tools, but some are written with plain text and a compilation system. Some of their technical information is simply wrong. For example they say that RSS “alerts users whenever their favourite blogs are updated” (this can be done through RPC notification which then requires RSS to pull the data - but a user will almost always have a tool polling their favourite RSS feeds). Their section listing the various options for blogging platforms mentions LiveJournal, Blogger, and MSNSpaces but doesn’t mention Wordpress.com which seems to be a serious omission (although it does mention civiblog.org which is a useful hosting resource for grassroots political campaigning). But these are minor problems, they are reporters primarily not programmers. Their document gets interesting when it gives links to pages about blogging ethics. One page that was not directly linked (presumably because it mainly concerns non-journalistic blogging) is Rebecca Blood’s document about blogging ethics [2]. She gives a brief coverage to conflicts of interest and gives most space to the topic of maintaining a record of changes. One thing I have been considering is having a separate instance of Wordpress for documents that change [3]. This way regular blog posts (such as this one) can be relied on to preserve a list of changes (any change other than correcting a typo will be documented) so if you link to a post you can rely on the original intent being preserved. But for posts which have ongoing value as live documents they will be kept current without a significant change-log. Items that go into the main blog would include commentary on news and predictions, and the document blog would contain technical information about Linux, the science-fiction stories that I will eventually write, etc. When I wrote my previous blog post about this issue I was mainly considering technical issues, but when considering the ethical issues it becomes clear that I need a separate blog (or other CMS) for such things. The site etbe.coker.com.au needs to be a reliable record of what I wrote while another site such as docs.coker.com.au could contain live documents with no such record. The essential factor here is the ability of the user to know what type of document they are seeing. Another really interesting point that Rebecca makes is in regard to known bad sources. Sometimes a known bad source can produce worthy data and is worth referencing, but you have to note the context (which among other things means that if the worthy data gets any reasonable number of hits it may get replaced by something entirely different). If a blogger cites a reference on a known bad site and explains the reason for the reference (and the fact that the nature of the site is known) then the reader reaction will be quite different to just a reference with no explanation. As a contrast to Rebecca Blood’s document the cyberjournalist.net code of ethics [4] covers the traditional issues of journalistic integrity, “public interest” etc. One interesting issue that they raise (but apparently don’t address) is the definition of “private people“. While it is generally agreed that movie stars and similar people deserve less protection as they have chosen to be in the public eye the situation regarding bloggers is less clear. Is a blogger with a high ranking on technorati.com in a similar position to a Hollywood star when it comes to privacy? A claim is sometimes made that blogs are unreliable because they can change (based on the actions of some bloggers who change posts with no notification and turn sections of the blogsphere into a swamp). Magazines and newspapers are held as an example of unchanging content and people who publish online magazines sometimes express horror at the idea of changing a past issue. The fact is that newspapers and magazines never changed past issues because it is impossible to recall hundreds of thousands of printed documents that are distributed around a country or the world. When it’s possible to fix old issues (as it is online) then the requirement is to document the changes not keep bad versions. It probably would be a useful feature for a blogging package to have the ability to display (and link to) old versions of a page. This would allow the users to easily see the changes and anyone who references a post can reference a particular version of it. In some situations it may make sense to use a Wiki server instead of a Blog server for some data to preserve the change history. Maybe I should consider a wiki in which only I have write access for my documents repository. No-one seems to cover the issue of how to deal with fiction. Obviously for a blog such as 365tomorrows.com (a science-fiction blog) it’s assumed that all content is fictional unless stated otherwise. The problem comes when someone includes fiction amongst the non-fiction content of a blog. I recently unsubscribed from a blog feed when the author revealed that what appeared to have been a diary entry was actually a fiction story (and a poor one at that). If your blog has mostly non-fiction then any fiction must be clearly marked, probably including the word “fiction” in the title and the permalink would be required to avoid all potential of confusion. For my documents CMS/blog I am considering having a category of “fiction” and to use the category name in the permalink address of each post. Of course science-fiction is sometimes obvious as fiction, but to avoid problems with fiction that is set in current times I think it’s best to clearly mark all such posts. The old-fashioned media seems to have dealt with this, tabloid womens magazines (which almost everyone reads occasionally as they are often the only reading materiel in a waiting room) traditionally have a fiction story in every issue which is clearly marked. Another type of blogging is corporate blogging. I wonder whether that needs to be covered separately in an ethics code. One thing that the three documents about ethics have in common (as a side-note in each) is the fact that the personal reputation of the writer depends on their ethics. If you are known for writing truthfully and fairly then people will treat your posts more seriously than that of writers who lie or act unfairly. There are direct personal benefits in acting ethically. The RSF document claims that the sole purpose of ethics standards is to instill trust in the readership which directly benefits the writer - not for any abstract reasons. Whenever ethics is mentioned in terms of writing there is always someone who claims that it can’t be enforced, well many people in your audience will figure out whether you are acting ethically and decide whether they want to continue reading your materiel. I wonder whether Planet installations should have ethics codes and remove blogs that violate them. In conclusion I think that a complete code of ethics for blogging needs to have some IF clauses to cover the different types of blog. I may have to write my own. Please let me know if you have any suggestions.

MJ Ray: Sky and Setanta Ad Complaints Highlight Differences

Both Sky and Setanta have had complaints upheld against their adverts by ASA this week. Sky for misleading criticism of Virgin Media's new-customer offers (Sky runs new-customers offers too) and Setanta for misleading advertising of their Premiership football package (or formally, Sky's "ad breached CAP Code clauses 3.1 (Substantiation), 7.1 (Truthfulness), 15.1 (Prices) and 18.1 (Comparisons)" and Setanta's "ad breached CAP Code clause 7.1 (Truthfulness)" ). But it's more interesting to look at who made the complaints:-
"Sky TV believed the [Setanta] ad was misleading"
but
"one complainant who was already a Sky customer"
and
"an existing customer"
were among the five complaints about Sky's ad. Sky's biggest critics seem to be their own customers. That's gotta hurt.

17 October 2007

Miriam Ruiz: OSI approves two Microsoft licenses as Open Source

The Open Source Iniciative (OSI) has approved two Microsoft license submissions: The Microsoft Public License (Ms-PL) and the Microsoft Reciprocal License (Ms-RL). The Open Source Definition was written after Debian Free Software Guidelines, also by Bruce Perens, and they have a lot in common. What is Hasefroch pretending with this movement? It’s not that I trust them too much, so I just don’t think they won’t have a hidden intention, but then again, they might not have it this time, who knows. It might be just a marketing show, having two OSI approved licenses, but not using them to release any significant code, or maybe they’re discovering that Open Source/Free and Proprietary Software are not exclusive and each of them might have its space. Or maybe… it was “Embrace, extend and extinguish“, wasn’t it? I’ve had a look at the licenses, and apart from some patent-related provisions, I don’t see anything in them that could make them non-DFSG-free, anyway. The difference between them is that the Microsoft Reciprocal License (Ms-RL) has a clause stating that you should release your modifications under the same license. Lets see what the future provides.

26 September 2007

Miriam Ruiz: Piklab in Debian

I’ve been so busy lately that I forgot to write about it: Piklab is now in Debian. I don’t know if any of you has done and development with PIC microcontrollers, but it’s not that there was a lot of free programs for doing so. Even now, it might be problematic depending on which hardware you have for programming them. In any case, Piklab is an integrated development environment for applications based on Microchip PIC and dsPIC microcontrollers similar to the MPLAB environment, which makes it easier to develop. It’s a real pity that we cannot consider the newer versions of SDCC as DFSG-free, due some non-commercial clauses, because it is a real nice companion compiler for Piklab.

15 September 2007

Lior Kaplan: Hebrew, Perl and a License Hell

Three months ago Gal-Gur Arie asked me to package a Perl module named Locale::Hebrew. The goal is to enable Hebrew support in xmltv which uses a Perl script to pull the Israeli TV schedule. See #432748. Gal’s request falls under my Debian Hebrew category, otherwise I would refer his request to the Debian Perl Group. I started to work on the package, and reached the part of creating the debian/copyright file. In the Perl code, everything was OK, as it’s licensed under the Artistic License. But then I notice a bidi.c file with the following “license”:
Source code in this file and the header file may be distributed free of charge by anyone, as long as full credit is given and any and all liabilities are assumed by the recipient.
But it also had this:
Copyright (C) 1999, ASMUS, Inc. All Rights Reserved
As the “license” isn’t free, and the previous line pretty much makes that clear, I couldn’t upload the package to the archive. Maybe to non-free but I prefer that would be my last option. I was able to contact the copyright holders, and ask for clearing the license. Preferably with re-licensing the code with the GPL or other OSI approved license. Asmus Freytag answered me that there’s an updated version of the file in unicode.org with a proper references to a license, and suggested that I should check if it that’s OK for me. That license isn’t a free software license, but has en exclusion clause for certain files:
Permission is hereby granted, free of charge, to any person obtaining a copy of the Unicode data files and any associated documentation (the “Data Files”) or Unicode software and any associated documentation (the “Software”) to deal in the Data Files or Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, and/or sell copies of the Data Files or Software, and to permit persons to whom the Data Files or Software are furnished to do so, provided that (a) the above copyright notice(s) and this permission notice appear with all copies of the Data Files or Software, (b) both the above copyright notice(s) and this permission notice appear in associated documentation, and (c) there is clear notice in each modified Data File or in the Software as well as in the documentation associated with the Data File(s) or Software that the data or software has been modified.
To me, this seems free according to the DFSG. So I got a second opinion at debian-legal just to be sure. Well, now that the licensing issues are over, I needed to check that the software can work with the new bidi.c file. Audrey Tang (the original upstream) was kind enough to help with the testing, but here tests showed that too much have changed in the new bidi.c file, and the program doesn’t build correctly. So I’m back in square one… I got back to Asmus Freytag for a license change, this time asking for the unicode.org license. Asmus didn’t approve my request, and referred me to unicode.org for an answer. Full correspondence is available in the liblocale-hebrew-perl’s ITP. The problem is that I can’t be sure the file originated at unicode.org, as there isn’t any reference to them. And anyway, any license change should be done by Asmus Inc. and not unicode.org. Any one with contacts in Unicode, Inc. ? The best solution would probably be writing a Perl bindings around libfribidi as was done for Python. The problem is that I don’t have a volunteer for that. Bummer.

10 September 2007

Rob Taylor: gobject-introspection

So, progress has been moving on nicely on a tool for generating gobject-introspection xml. Development’s getting pushed forward now by two veritable geniuses, J rg Billeter and Mathias Hasselmann. We’ve got sparse able to handle extended attributes, so headers can be marked up with details like ownership of returned data. There’s also a git branch of gobject-introspection where we’ve been delveloping some python code that takes the headers, runs sparse over and generates some basic introspection XML, using ctypes to call into gobject for getting interfaces, signals and properties. Very Nice! BUT, we’ve hit a big problem. Sparse is licensed under the Open Software License 1.1. Debian considers this non free, and it certiainly looks to have some overly onerous clauses. Linus did try to relicense it a few years ago, but hit a brick wall with Transmeta, who own some of the copyright from when Linus worked there. We might end up having to drop the use of sparse and maybe have our own bison-based parser. We really don’t want to have to go there though. So, here’s my lazyweb request - Does anyone out there know anyone at Transmeta that we could talk to about relicensing this work? It might be worth pointing out to that it might be in their interests, given the patent termination clauses.

8 August 2007

Miriam Ruiz: El rei de la casa

The Proof of the PuddingThis is an updated translation into English of the one-question interview with pjorge (based on Darren Rowse’s one-question interviews idea) in which Javier Candeira (Barrapunto co-founder and editor among many other things, and a good, loved friend of mine) comments about an interesting game of his creation that’s being exhibited in Barcelona and that deals with the fears many parents have towards the Internet and the new enterntainment technologies and videogames. The game code will be released as GPL, even though the game data will have a non-free Creative Commons (with a non-commercial clause). The game has a really interesting approach, and mixes the concept of pinball games with that of graphics generated with “paper dolls” techniques, to try to make people think about the ideas mainstream media are pushing, and the way they try to tell everybody how to raise their kids. You might like it or not, but it will probably won’t leave you indifferent. That’s what art is about, in fact, isn’t it? What is ‘El rei de la casa’? ‘El rei de la casa‘ (an expression that in Catalan and Spanish means “the precious child”) is an exhibition and a videogame. The exhibition deals with the cultural construction of the idea of childhood, and can be visited until September 24 in the Palau de la Virreina in Barcelona. From there. Among other works, in the exhibition there are photos by Loretta Lux and Bego a Egurbide, paintings by Marc Ryden, Kiki Smith and James Reilly… it’s really worth a visit. El rei/la reina de la casa. ( The videogame is a commission from Andr s Hispano and Marc Roig, curators of the exhibition. They wanted to portray Internet and videogame arcades (or cybercafes, which are their modern equivalent) as one of the “new forests”, these places where parents don’t dare allow their children go alone for fear of the dangers (real or imagined) that may lie in ambush. The Internet has entered into the collective imagination, and one of the memetic niches that it has crept into is that of the bogeyman, the scapegoat that bears the brunt of all the evil that happens in society. It is enough to look at the news programmes from right-wing TV stations with their adversative Internet coverage: “it’s good, but…”. All over the media you see headlines like “gang of pedophiles arrested who sold child pornography *on the internet*”. They conveniently skip that pedophiles filmed those poor kids *in a flat*, and that they did it *on a bed* and used *videocameras* just like those used by the reporters now sounding the alarm. But no, what’s bad is *the Internet*.
The other theme that we wanted to touch on with the pinball game is how videogames are presumed to corrupt childhood. When pinball games were introduced, the North American authorities laid down the law: it was an infernal machine that incited gambling and even lust. From the religious right to the secular left, every moral guardian has denounced the supposed harmful effects of videogames on childhood: because of them children and teenagers engage in murder, robbery, truancy, bad school grades and even untidy bedrooms and doubtful personal hygiene. For this reason, the “new forest” of the Internet and videogames had to be a videogame, proving once more that games are cultural vectors, a form of artistic, political or commercial expression like any other. It also had to be a videogame about the a triangle: on one side the children, on the second one the children minders (parents and society at large), and finally the Great Scapegoat: the Internet. After many abandoned and reworked proposals we arrived at the present design for the game: an emulated pinball game presented on a panoramic TV screen, and having two levels: one set in the real world and named after the exhibition, and a second one set in a more or less conventional cyberspace. This second level is called “Prey of the Net”, and portrays the vision of the Internet that a Fox viewer may have: you have Spam, game-playing killers, kids making more money than their parents, S&M gear, dildos… in short, everything that is scary and nothing that is comforting, at least to some.  Presa de la red! (All the illustrations for this pinball, both on the gameplay field and on the scoreboard, are by Mauro Entrialgo. For the scoreboard I asked him to prepare a set of drawings similar to KISS dolls (like the cut-up dolls that kids still played with in the last century). Thanks to these dress-up dolls the scoreboard shows more than the score (which grows randomly anyway); it also portrays the state of the boy or girl protagonist of the game. I say “boy” or “girl” because in the game, just like in real life, you have a 50/50 chance of starting the game of life with either sex. The fist level, ‘El rei de la casa’, portrays the stress that families feel when facing children’s media consumption. The targets trigger lines from the parents: “All day in front of the Idiot Box!” when you hit the tv, or “without a degree, you are nothing” when you hit the school. There are four targets on the right, which can be reached shooting the ball with the left flipper (the one representing the parents): school, museum, church and reading. On the left, and reachable from the right flipper, representing the kids’ id, are the TV, the kid’s peers and the videogame console; at the top of the playing field, towering above it, the internet-enabled computer. As the ball hits the different targets, the scoreboard dresses the kids in a housecoat, a leather jacket, and gives them a mortarboard or a saint’s halo. They are the pride of their parents, kids still not perverted by the Internet. It is cheap symbolism, I confess, two-dimensional sociology, but that was also something we aimed for. After all, pinballs have always been complicated allegories rather than complex ones. In a first design I planned to make computer accessible only under certain conditions, but that is not something that would have work in this exhibition: some people just play and play (which gives me an immense joy), but other people can’t or won’t give it much effort. It’s best to make it easier for everyone, so they can send the ball into the next level even without meaning to. The second level, “Prey of the Net”, is accessed when the player puts the ball through the PC’s screen. Here the character on the scoreboard keeps smiling while the game dresses them in a straightjacket, S&M headgear, or leaves them in their underwear, with their hands full of money, playing cards, bloody knives and sex toys… to their parents’ horror. The player has no fixed goal here, only to make the ball go through the pachinko and the spinning spider. These elements work as an atrocity generator and a rebuke distributor. Parents’ voices scold the player, faced with the horrors of the Internet. But the star is the scoreboard. Mauro rocks. Right now the code and content for downloadable game are done, and the people responsible for the ISO are giving it the final touches. It will be a bootable liveCD with some Debian variant that (hopefully) will run on any PC bought in the last two or three years. We will treat the computer as a games console, which may or may not be symbolic (if you want it symbolic, we can make it symbolic!). The game itself is under the GPL license (the pinball part is based on Henrik Enkvist’s Emilia, which is packaged in Debian), and only the graphic resources will be under a non-commercial Creative Commons license. The music is also under a non-free Creative Commons license because of the status of the original samples, but I recommend you download it and play it because its author is none other than man, the Barrapunto founder and sometimes editor.

6 July 2007

Anthony Towns: GPLv3 and Debian

So with the GPLv3 and LGPLv3 finally out (hurray!) it’s time to actually pay attention to the practical consequences of an upgrade to the world’s premier copyleft licenses. One of the things I hadn’t noticed, though I should have, is that the LGPLv3 is not compatible with the GPLv2 – that is, GPLv2 programs that used LGPLv2 libraries cannot make use of new versions of those libraries released under the LGPLv3 without also updating their license to GPLv3 (or “GPLv2 or above”, or LGPLv2 or LGPLv3 or something similar). Fortunately one of the major LGPLv2 libraries out there – glibc – is reportedly going to remain available under the LGPL v2.1 but for other libraries, it could become a problem, and it’s something GPLv2 authors will need to pay attention to. Also fortunately the opposite problem – GPLv3 apps using LGPLv2 libraries isn’t a problem, because the LGPLv2 explicitly allows redistribution and modification under the terms of GPLv2 or later, so you can take an LGPLv2 library and incorporate it in a GPLv3 application and just release the whole thing under the GPLv3. Unfortunately, the LGPLv3 doesn’t have a similar clause, so when the GPLv4 comes out, if it ever does, we could easily find the GPLv4 apps can’t use LGPLv3 libraries, and GPLv3 apps can’t use LGPLv4 libraries. Really these are side-effects of a fundamental change: up until now, almost everything we’ve distributed – and certainly all the low level stuff: the kernel, the C library, the compiler, the shell and basic tools – have all been under a GPLv2 compatible license. Some of them have been more flexible than that, due to being under a BSD or MIT license, or being under the LGPL or having a “GPLv2 or later” clause, but we’ve been essentially able to ignore all that and just treat everything as GPLv2. There are a few exceptions that we have to deal with – the occassional app that’s not GPL compatible doesn’t cause much of a problem, because things that depend on it don’t usually create copyleft issues, which just leaves checking that it doesn’t use any GPL-only libs, such as gnutls or libreadline. Openssl is a nuisance, in that it’s a popular, GPL-incompatible library, but it’s also reasonably easy to deal with on a case by case basis. But with the GPLv3, that changes: as GPLv3 apps and LGPLv3 libraries get uploaded, the assumption that more or less everything is GPLv2 compatible goes out the window, and while some things are GPLv2 only (such as the kernel!) we also can’t assume everything is GPLv3 compatible. Fortunately, both the GPLv2 and GPLv3 have what is known as the “system library” exception, which allows you to not bother distributing the source to your C compiler or C library or kernel with your app, because everyone’s assumed to have one of those already. Unfortunately, the GPLv2 version of that exception includes the phrase “unless that component itself accompanies the executable”, so Debian has always cautiously assumed the exception doesn’t apply to us, because everything we distribute in main “accompanies” everything else in main – kernel, C library, C compiler, etc. Equally unfortunately, while the GPLv3 avoids that problem, but ends up with a clause that’s not terribly comprehensible, despite a couple of rewrites during the drafting process. What’s all that mean? The big thing is that it means Debian’s going to have to put a bit more attention into the system library exception, both for GPLv2 and GPLv3 apps, because our current policy of trying to avoid needing it is probably not going to be sustainable. I’m not sure how in depth we’ll need to go for that; we’ve already contacted the FSF licensing folks for an explanation of the GPLv2 clause in relation to the CDDL, but it’s possible the FSF might prefer to be ambiguous in responding so as to keep their options open for defending or enforcing the GPL later, in which case we might need to get legal advice of our own as to what we should do. The second thing is that in reviewing our understanding of the system library exception, we might be in a position to have a Debian GNU/OpenSolaris port, making use of the exception for the CDDL-licensed OpenSolaris kernel and libc, as Nexenta do. That seems to me to be almost certainly possible for GPLv3 (or “GPLv2 or above”) applications, and probably possible for GPLv2 apps as well. If so, that’ll let us expand Debian to supporting four kernels in the near future: Linux, Hurd, FreeBSD and OpenSolaris, which will be pretty fun, in my book. The downside, is that if we find an interpretation of the system library exception that lets us mix and match licenses comfortably, that same interpretation might be able to be used to let propietary software vendors mix and match GPLed software with non-free software, rather than just free software with different copyleft licenses – and thus defeat the entire point of copyleft. What’s worse, is that by following Debian’s lead, they’d have some moral authority in doing that, beyond just having a legal argument as to why it’s okay. And that’s the rub. (My thoughts on the license texts as posted to -legal are here, here, here and here.)

1 July 2007

Gustavo R. Montesino: Exception handling on PyGTK applications

A feature I've been wanting to implement on bug-triage for some time now is to have unhandled exceptions shown in a gtk message dialog instead of getting lost on the terminal. And I've finally got it working now.

At first, I had some vague impression of having read about changing the default exception handler on Python. Maybe I've just mixed things up, but I couldn't find anything about that today (maybe it was Java?). Instead, I found out some information about Python decorators.

This is the first time I've seen anything like the decorators, and I must say this is a concept a bit hard to get used to, at least for me. Basically, if is a function that gets a callable (ie, a function or anything else that can be called) and returns another callable to be used in its place -- usually the original one with some nice extra.

I've created a python decorator to wrap the function call it decorates inside a try statement, whose except clause show some info about any exception it gets. The code can be seen on the bug-triage git repository.

On the linked file, errorhandler is the decorator and msg_exception takes an exception as argument and shows a message dialog. Applying the decorator to a function is simple, import it and add an @errorhandler just before its declaration.

Some references on decorators:
PS: I just got really happy to discover that this blogger/blogspot draft autosaving stuff works...

5 June 2007

Martin-Éric Racine: Tip of the day: fetching all Debian source packages

A few weeks ago, the Linutop team received a request for its source code. We had already anticipated the GPL source offer clause in our development plan, so it was just a matter of myself getting around producing a source code ISO image. Piece of cake, right? Almost. You see, Linutop includes a custom kernel package and several separate wireless module packages, so the the following command would not work as expected:
apt-get --download-only --ignore-missing source $(dpkg --get-selections   cut -f 1)
Why is that? Because APT ignores the --ignore-missing option whenever executing the source command. Instead, Roland Mas suggested that I used this simple Bourne loop:
for p in $(dpkg --get-selections   cut -f 1) ; do apt-get --download-only source $p ; done
Done this way, the source code of each package is fetched individually and, if any package's source is not available, APT exits but the Bourne loop moves on to the next package in the list. Nifty, isn't it?

26 May 2007

Sam Hocevar: Bits from the DPL: FSF, expenses, DSA

chat with the FSF I had a nice talk with Peter Brown, FSF Executive Director and Brett Smith, Licensing Compliance Engineer. We mostly talked about the GPLv3, the GFDL and the Nexenta project. The official GPLv3 launch is approaching very fast, and the FSF was wondering how Debian could play an active part in it. As I also said on debian-devel I am not eager to promote the use of this new licence until we know how much of our libraries are GPLv2-only. Any ideas about what Debian could do are of course welcome. We didn t talk much about the GFDL. The FSF s absolute priority right now is the GPLv3, the GFDL will be addressed later. After last year s GR Debian decided that works under that licence were free if they didn t use unmodifiable sections. We are still waiting for a fix for the badly worded DRM clause, which the FSF told me they re going to address. The Wikipedia project also has concerns with the GFDL so we should expect the licence to change a lot. I opened a licensing questions ticket on May 16th to ask the FSF to clarify their position about the Nexenta and other OpenSolaris projects (full text available here). There are good chances that the answer will be in favour of allowing the redistribution, but it will take the FSF lawyers a few weeks to carefully write it down. I am personally enthusiastic about having this new port in Debian if possible. disbursement of Debian funds Around $4,300 USD (3,200 EUR) of Debian funds were spent or pledged to be spent this month, mainly on travel reimbursement for developers attending Debian meetings or representing Debian at various places. I will send any details to debian-private until I m confident this is the kind of information I can really make public. DSA team Three weeks ago I posted about how not many people were proposing to help with the various core teams, and immediately got a lot more candidacies. Two weeks ago I sent a list and short description of 6 of these people to the current members of the DSA team for comment. Depending on what they are going to answer I ll decide on what to do next. I haven t done anything similar about the other teams yet, apart from collecting proposals and ideas.

25 May 2007

Biella Coleman: Pricefull and Priceless

$ 5000 medical bill (that insurance won’t pay for)
$ 450 water bill in Puerto Rico
$ 150 library fine for one lost book that normally costs under 20 dollars Anxiety and rage from dealing with these ludicrous bills: priceless. Ok seriously I am now dealing with these three things and it has been really really really unpleasant. I sometimes wonder if I was once a bad as* Roman tax collector by the name of Biella Plebius and now, reincarnated as Biella Coleman, I am suffering the karmic consequences of extorting people in the 3rd century A.D. Other times I take a lighter approach to all of this and console myself that if nothing else, I am learning a lot. For example, as I had mentioned awhile back, Blue Cross Blue Shield Horizon of New Jersey is stalling and denying health insurance bills for my mole surgery. Because I had a pre-existing clause in my contract, they are trying to squirrel out of it. However, since I never had a pre-existing issue with moles, I am pretty sure they are required to pony up the cash but getting them to do this has been a Herculean, no Sisyphean task. Since it was clear they were not going to pay if I alone was applying pressure, I was about to file a claim in Special Civil court (the bill is too high for small claims court) but I wanted to see if I had any other options. So hours and hours after diligent web research, I finally found on lawyers.com that I can file a complaint against my health insurance via the Department of Banking and Insurance. I am amazed that NO ONE in the doctor’s office, including those whose only job is to deal with health insurance, had a clue about this option. And even when you go to the Dept of Insurance website it is not totally obvious that you can file a complaint (it is under the “file for assistance” category). But once I got in touch with them, they have been incredibly helpful. Now, my detailed complaint letter is with them, and some other documentation and apparently they have an investigator on the case. I am not sure if this route will be enough pressure to get the job done but at least by the time this is over, I will be in the greater NY area so that I can move to the court option. The take away lesson here is that if you are having any trouble with claims and health insurance, do do do do file a complaint with your state Department of Banking and Insurance. This is a great first option to use.

17 May 2007

MJ Ray: Contracts for people to work on Free Software: unearthing a lawyerbomb

Marc Fargas commented about the work-grabbing contract clauses --

"From clause 2 I understand the $ COMPANY has access to later version **used in the $ COMPANY ** ""of such software in use at $ COMPANY ."", not any later version, just those used while being in $ COMPANY as they may be depending on such code."
So, is this (all versions of (such software in use at $ COMPANY )) or ((all versions of such software in use) at $ COMPANY )? Whoo, a lawyerbomb - it's unknowable unless it's reached court.

16 May 2007

MJ Ray: Contracts for people to work on Free Software

This is a reply to Andrew McMillan Contracts for people to work on Open Source Software, posted on my blog because of yet another stupid eyetest. It looks like there might be a loophole: Clause 2 maybe gives $ COMPANY rights to access the source code of later versions, just because $ EMPLOYEE used one version at $ COMPANY . I don't think it's fair for $ COMPANY ownership to be the default instead of joint ownership. I didn't spot anything obviously missing. I'd like to see $ COMPANY changed so that the workers are owners rather than merely employees, but that's probably not on offer ;-) However, that's part of how TTLLP side-steps the question - it's a partnership, not a employer-employee situation where the employer's owners try to own the fruits of the worker-employees' labour in addition to the company's assets.

Next.

Previous.