Oct 3rd: http://DRM.info was launched today. The aim is to make an information portal where people can see real world uses of DRM, how it affects a variety of sectors, and who is together in rejecting it.

Here's the press release. If you want to raise awareness of DRM, probably the easiest thing you can do is to link to this site and point people to it. DRM.info is a collaborative effort. FSFE also has its own DRM page.

There seems to be almost unanimous dislike of DRM in the free software community, but people are less unified on how to tackle it. One suggestion is that we can defeat DRM by not buying DRM'd hardware. This is often called "vote with your feet", but it is not enough. Relying on it alone would be certain failure.

People who put forward this idea usually mention "free market", but they ignore that people can participate, not just purchase things, in the free market. Here are four hurdles to tackling DRM by "vote with your feet" tactics:

1. Not many people are aware of DRM, and not many people see the value of their freedom. DRM.info is an effort to address this.
2. Purchasing decisions are not very granular. They lump together varied aspects such as price, style, compatibility, recyclability, and respect for freedom to control the software. This makes it hard to send a signal to manufacturers since a drop in sales could be attributed to one of many factors.
3. The options offered to purchasers - what you can "vote" for - are set my a someone with a special interest. If the hardware manufacturers have an interest in locking down users with DRM, they can stack the options to make it inconvenient for users to choose DRM-free hardware.
4. Those with an interest in locking down technology users can leverage other markets, such as the entertainment market. Monopolies or cartels can be set up so that the public's technology purchases also decide what entertainment they have access to.

To effectively defeat DRM, we must not only reject DRM'r hardware that locks us out, but we should also participate in the drafting of related legislation (FSFE does this), participate in policy forming, participate in international treaties (FSFE does this too), and use our licences to say that our software cannot be a stepping stone for using DRM against people (GPLv3 does this).

Some people have expressed a worry that if we are unfriendly to Tivo, as GPLv3 is, they will stop contributing to our projects. This may be true, but we never relied on their contributions, and their practice of preventing tinkering is losing us contributors too. Fewer tinkerers equals fewer contributors.

The British Library seem to understand the problems of DRM. (It's unfortunate that they used the term "Intellectual Property". That term works against them by encouraging oversimplified thinking.)

Georg Greve also has a blog entry on DRM.info.

I recorded my talk "GPL: what can v3 improve?" at aKademy 2006 on my digital camera. Below is a video and the timeline of the talk.

I still need practice at public speaking, but I'm getting better. I'm good enough to be a discussion starter for certain FSFE issues, but I should say at the start of my talks that I'm not a spokesperson for FSFE.

Another mistake I made a few times is using the word "we" without saying who I was talking about. Sometimes it means "me and the people nearby", but it could be misinterpreted as "me and the authors of GPLv3" - that group doesn't exist, I'm not in any such privileged group. My information comes from public sources, I've just been following the issue closely.

This URL is probably not permanent. I will move the video to another server when I find one. If you want to reliably link to it, mirror it or link to this blog entry.
http://ciaran.compsoc.com/ciaran-gplv3-akademy-2006.ogg

Sections

1. [00:20] 5 Motivations for a new GNU GPL
2. [00:42] Why change it now?
3. [01:36] Motivation #1: Clean-ups
   • [01:36] (a) BitTorrent distribution
   • [02:50] (b) Licence termination
   • [04:36] (c) Internet versus postal distribution
   • [05:50] (d) Duration of source code availability
   • [06:36] (e) Easier to understand
4. [07:32] Motivation #2: Internationalisation
5. [10:57] Motivation #3: Licence compatibility
6. [14:50] Motivation #4: Patents
7. [20:17] Motivation #5: Digital Restrictions Management
8. [24:38] Linux developer comments
9. [26:18] Can Linux relicense?
10. [28:53] Commenting
11. [31:17] The gplv3.fsf.org/comments system
12. [32:38] Discussion committees and the decision process
13. [34:25] Audience Q1: What happens if Stallman dies tomorrow?
14. [37:15] Presentation conclusion, http://fsfeurope.org/projects/gplv3
15. [41:30] Audience Q2: Are "me too" comments useful?
16. [43:05] Audience Q3: Have FSF met the Linux developers in person?
17. [44:26] Audience Q4: Can v3 and v2-only code be combined? (No)
18. [46:28] Audience Q5: How can large projects guard against future incompatibilites?
19. [48:14] Audience Q6: What licences will be compatible with GPLv3?
20. [53:20] Audience Q7: Are the differences between drafts available online?
21. [53:40] Audience Q8: Will the anti-DRM clauses prevent companies from preventing employees from modifying their work computers?
22. [55:54] Audience Q9: Might the compatibility section allow for a less-free GPL?
23. [58:56] End of session