Bolzano

On the 11/11 I will be in Bolzano, Italy attending the First International Annual Meeting of the Fellows of the FSFE this will be an excellent opportunity to meet the fellows and the team. In addition to this there have been promises of new projects that will be announced at the meeting. The event also coincides with the South Tyrol Free Software Conference which is in Bolzano on the 10th – unfortunately I will miss a large part of this event since I shall be travelling to Bolzano.

If I have some spare time (which I doubt) I hope to be able to pop in to the South Tyrol Archeological Museum, which hosts the Ã?tzi the iceman.
Ã?tzi is the nickname of a well-preserved natural mummy of a man from about 3300 BC, found in 1991 in a glacier of the Ã?tztal Alps, near the border between Austria and Italy. The nickname comes from Ã?tztal, the region in which he was discovered. He is Europe’s oldest natural human mummy, and has offered an unprecedented view on the Chalcolithic (Copper-stone Age) Europeans (Wikipedia).

The Fellowship

As a member of the Free Software Foundation Fellowship I have finally got around to beginning to work with attempting to get my membership cryptocard to work on my Mac. It is not as easy as I had hoped. The thing is that I have soon abused my tecchie friends to the point where they refuse to actually help me directly but tend to give me small hints. I feel like an illiterate person faced with a crossword…

This promotes the learning curve but frustrates the hell out of the desire for instant gratification! For those of you who are not yet members of the fellowship I can recommend getting involved. The FSF is a valuable and important resource organisation and it also creates a higher level of awareness of our technical abilities and vunerabilities. Join now.

Software Eco-Systems

Say ecosystem* and most of us will think of something delicate and finely balanced. We have been taught to understand that the environment is made up of systems which hang together and that disturbances in one part will created unintended and in our experience sad consequences.

Say Microsoft, Adobe or General Motors and we tend to think of corporate bohemoths hardly the delicate flowers in need of protection, but more often a cause of some destruction within their particular ecosystem.

A letter (pdf here) to the European Commission has recently come to light (it was leaked). The letter shows the extent which the anti-Free and Open Source Software (FOSS) lobby is prepared to go in order to maintain control of their dominant business model for the production of software.

The letter was sent in response to a recent EU report on the role of open-source software in the European economy. The letter warns of against encouraging the FOSS movement. The letter states that the actions taken by the European Commission could “disrupt the entire software eco-system” and the report itself was biased and looked “more like a marketing document than a serious survey”.

The letter comes from The Initiative for Software Choice (ISC). A name which inspires one to think of openness and freedom. Yet the group is a lobby group funded by proprietary software manufacturers – this, in itself, may be seen as a contradiction in terms.
According to Techworld the ISC was created to oppose government efforts to give preference to open-source or open standards-based systems. According to critics such as Bruce Perens, the ISC largely pursues a pro-Microsoft agenda, though the group itself emphasises that it has more than 300 members.

The letter is full of artful uses of language and leaves the unsuspecting reader with an impression that the writer is concerned about the welfare of the European Union and its development. At the same time the message is hammered home – with the subtly of a rhino with a headache – do not change anything. The system works as it is.

Naturally the concerns of the manufacturers of proprietary software should and must be taken into consideration but this letter is a masterful peice of dubbletalk and rhetoric (in the worst way).

Read the letter and LEARN from it.

* An ecosystem refers to the collection of components and processes that comprise, and govern the behavior of, some defined subset of the biosphere. The term is generally understood to refer to all biotic and abiotic components, and their interactions with each other, in some defined area, with no conceptual restrictions on how large or small that area can be. To many, ecosystems, like any other system, are governed by the rules of systems science and cybernetics, as applied specifically to collections of organisms and relevant abiotic components. To others, ecosystems are primarily governed by stochastic events, the reactions they provoke on non-living materials and the corresponding responses by organisms. (Wikipedia)

You Cannot Patent Software

…and yet there are software patents.

In a long draft article entitled “You Canâ??t Patent Software: Patenting Software Is Wrong” – Peter Junger states that which most lawyers fail to see. Maybe because they are blinded by economics?

Computer programs are texts, not machines as some lawyers have confused themselves into believing, and thus they may be copyrighted and protected by the First Amendment, but they are not patentable as machines. Computer programs are indeed processes, but they are not patentable processes because what they process is information and what they produce is information, not some modification of material goods or articles of commerce. The simple fact is—though the reasons for it may be hard for most lawyers to grasp—that, as the title of this article puts it: “You can’t patent software: patenting software is wrong.”

A nice, old school, scholarly legal paper which hammers home it’s point. It’s a good way to start the week with a work like this.

The Boredom of Programmers

I doubt that there is an authoritative history of boredom in the workplace but anyone making an educated guess would probably point to the factory and the division of labour as the point where large-scale workplace boredom became a serious problem. For those looking for a movie depiction of the problem of machine/man interaction need look no further than Chaplinâ??s film modern times where the character Chaplin plays attempts to keep pace with the inhuman rhythm of the machine.

When stuck in boredom many workers attempt to relieve the monotony in different ways. By searching code we can now see that bored and frustrated coders suffer from the same industrialised worker phenomena of boredom.

The results? Strange messages in the computer code. By using the search function in koders.com we can find lots of messages from programmers venting their frustrations by writing small messages. Here is an example:

ptr = buffer;
/* This f*cking sh*t is still giving problems downloading
* the f*cking images through the motherf*cker http, the only
* code we share with the other s*cking implementation is
* the code that follows, so I guess this is the damn sh*t that’s

or how aboutâ?¦

// I REALLY hate this kind of SHIT!
// yes I know MYSQL can be switched to ANSI bla bla but
// it is obviously not the default…

Nice to see that despite our developments we basically remain the same – humans dislike boredom and handle frustration badly…
(via TheRegister)

Swords and Apples

A long time ago I read the biography of the Japanese swordsman Miyamoto Musashi. This story led me to curiously find and read Musashiâ??s own strategy book, called â??Book of Five Ringsâ?? (Go Rin No Sho). Musashi developed the skill of fighting with a sword in each hand. He also had a list of seemingly simple recommendations for the reader. Among the recommendations that Musashi had which stuck into my mind was the advice:

Know your favorite tools and techniques for key tasks without getting overly attached to any one

This advice is on the surface extremely simple. We can all intuitively understand the importance of not getting stuck in a rut, learning new things, challenging our established beliefs and principles. BUT this is not an easy thing to do. We are (or at least I tend to be) simple solution people. We identify a problem from memory and apply the same solutions from the past – even if these did not work so well then.

This philosophically sound advice is important. But on a simpler level â?? I miss my mac. After having handed it in for repairs I have been using a loaner. Itâ??s a great machine. Itâ??s an IBM â?? I shouldnâ??t be complaining. But I miss my mac. I realize that it is not the actual software solutions that I miss. What I miss is the familiarity of the tool I am accustomed to.

Chilly Protest

We carried out a final anti-DRM protest in Göteborg today. We stood outside the AIPPI Congress and handed out flyers. There were less people who took the flyers but on the other hand we had interesting conversations with those who stopped to talk. It was a nice way to spend the morning – even if it was a bit chilly…

Yesterday's Anti-DRM

As you may have known yesterday was the international day to protest against DRM. For more information see http://drm.info. Despite the fact that I defended my PhD and partied until two. I pulled myself out of bed at 6am to get dressed in yellow overalls and demonstrate outside Chalmers University at 7.30. At about 9.30 stopped handing out leaflets and took a well deserved break.

This did not mean that we were done for the day. Oh no. At 11.30 we gathered at the center of town to continue our demonstrations until 1pm. The results? We handed out well over a thousand leaflets, we were interviewed by two newspapers and my headache never left me for a moment.

It was a brilliant way to celebrate my new life as Dr. Klang. This is the first time I wrote Dr. Klang! Feels kind of strange, but nice…

GPLv3 info from FSF

The Free Software Foundation wishes to clarify a few factual points about the Second Discussion Draft of GNU GPL version 3, on which recent discussion has presented inaccurate information.

1. The FSF has no power to force anyone to switch from GPLv2 to GPLv3 on their own code.  We intentionally wrote GPLv2 (and GPLv1) so we would not have this power.  Software developers will continue to have the right to use GPLv2 for their code after GPLv3 is published, and we will respect their decisions.

2. In order to honor freedom 0, your freedom to run the program as you wish, a free software license may not contain “use restrictions” that would restrict what you can do with it. Contrary to what some have said, the GPLv3 draft has no use restrictions, and the final version won’t either.

GPLv3 will prohibit certain distribution practices which restrict users’ freedom to modify the code.  We hope this policy will thwart the ways some companies wish to “use” free software — namely, distributing it to you while controlling what you can do with it.  This policy is not a “use restriction”: it doesn’t restrict how they, or you, can run the program; it doesn’t restrict what they, or you, can make the program do.  Rather it ensures you, as a user, are as free as they are.

3. Where GPLv2 relies on an implicit patent license, which depends on US law, GPLv3 contains an explicit patent license that does the same job internationally.

Contrary to what some have said, GPLv3 will not cause a company to “lose its entire [software] patent portfolio”.  It simply says that if someone has a patent covering XYZ, and distributes a GPL-covered program to do XYZ, he can’t sue the program’s subsequent users, redistributors and improvers for doing XYZ with their own versions of that program.  This has no effect on other patents which that program does not implement.

Software patents attack the freedom of all software developers and users; their only legitimate use is to deter aggression using software patents.  Therefore, if we could abolish every entity’s entire portfolio of software patents tomorrow, we would jump at the chance.  But it isn’t possible for a software license such as the GNU GPL to achieve such a result.

We do, however, hope that GPL v3 can solve a part of the patent problem.  The FSF is now negotiating with organizations holding substantial patent inventories, trying to mediate between their conflicting “extreme” positions.  We hope to work out the precise details of the explicit patent license so as to free software developers from patent aggression under a substantial fraction of software patents.  To fully protect software developers and users from software patents will, however, require changes in patent law.

Demonstrate against DRM before 40

Lists are popular. One such list is the things one is supposed to do before turning 40 (for example this book). I don’t know what the book includes but I don’t think it contains what I have recently done… I have applied for, and received, a permit to carry out a public demonstration.

On 3 October between 08.30-10.15 we will be standing outside Chalmers University. Between 11.30-13.15 we will be standing near the statue called Kopparmärra (the copper mare).
We will be wearing yellow overalls and masks while handing out leaflets against DRM. Join us for the Day Against DRM.