Licensing is a big deal in the software and cultural freedom movements; there are a lot of licenses available in both domains (probably too many), and people have strong opinions about what licenses and license components are better or worse. But in the truly libre category of licenses, maybe the most controversial aspect of licensing is that of copyleft, a powerful copyright hack that uses copyright itself in a sort of judo move to force those to make derivatives to give their contributions back to the commons.

There are two primary copyleft licenses, the GNU GPL for software (and some other categories of functional) works (and the related AGPL and LGPL) and CC BY-SA for non-software (generally cultural) works. But I don't intend to go into details on copyleft or the licenses themselves, there's plenty of resources about that already on the internet.

What I'm more interested in exploring here is the perspectives on copyleft. Is copyleft good? Is it bad? A lot of people have extremely strong opinions about it. Actually that's an understatement; if digital ink were made manifest, the amount spilled over copyleft could fill at least one olympic sized swimming pool. But despite all the heated debates about copyleft, I've never really found a good breakdown about what those arguments are. I actually think it's not too hard to separate the arguments categorically, so here's my attempt to do so.

Even though I'm on the overall-in-support side of things (I am actually conditionally in strategic support of copyleft and think the decision about whether to use copyleft or not should be weighed on a case by case basis; more about that at the end) I'm going to start by discussing the objections before I move to the support side. Generally I think the objection side of things is a bit trickier (and intellectually, maybe a bit more interesting to analyze) than the support side, so I'll go to that first before I explain why one might actually find copyleft to be a valuable tool. (A slight amount more caveat: I'm not claiming to not have bias here; I do. But again, I'm not completely on one side or the other, and I think the decision about whether to apply copyleft to your project is best made by understanding both the pros and the cons.)

I'm marking this as objection 0 because it's not actually an objection itself (some even argue it's a feature, and at the very least it's mostly necessary, unless you're using file or package-based copyleft like the MPL or LGPL). That is to say, on its own people aren't upset about it, but combined with the other objections some people find it particularly irritating: if you combine a copyleft work with a non-copyleft permissively licensed work (again, unless the copyleft license is the LGPL or MPL or similar), effectively the combined work is under copyleft. (This doesn't mean that you can't continue to develop the non-copyleft permissively licensed work separately without copyleft applying though.)

It should be noted though that the same thing is true with combining a non-copyleft permissively licensed work with a proprietary work: effectively the entire work is proprietized. (Indeed, that's exactly what copyleft licenses like the GPL are trying to prevent.)

Anyway, that wouldn't bother you if the terms of copyleft itself didn't bother you, so let's move on to the reasons people find copyleft itself objectionable.

The first objection is maybe the most classic objection to copyleft: copyleft itself is non-free. There are a few variations to this argument but it generally goes like this: restrictions in licenses are bad; possibly copyright as a system of restrictions is itself bad. Since copyleft relies on copyright and restrictions to preserve the commons, that means that it's also bad. The most free license then is one that provides as few restrictions as possible.

Sound confusing? Let's put this another way and go back to the copyleft as a "judo move" perspective. If copyright were violence (and a number of people in this camp believe that it really is), then copyleft defends against proprietization with a violence-in-retaliation move. It might be defensive, it might even just be returning the violent force of the oppressor against the oppressor itself, but to this particular category of anti-copyleft objection, that doesn't matter. Any violence itself (or any copyright restriction) is objectionable, even defensively, and the fact that a copyleft license makes use of such force is offensive.

The trouble with this position is, if you're really arguing it, you'd better be consistent about it and also object to the violence of proprietization (which is surely worse than copyleft in its reduction of freedoms through restrictions). If you really are concerned with user freedom, your whole ecosystem had better be free with completely permissively licensed non-copyleft works to bring that dream alive. If someone wants to proprietize your world, and legally they can, you can't stop them directly. Your only routes to bringing this completely ultra-restriction-free world to life are to keep building freely licensed works and tools (and encourage others to do so) and to try and reduce the scope of or eliminate copyright on a legislative level (a worthwhile pursuit, but certainly not an easy one, and one we seem to be losing rather than gaining ground on at the moment).

In the software world you used to hear this argument a lot more, particularly along operating system lines: back in the day it especially used to be [Free/Open]BSD users arguing with GNU/Linux users. If you're completely running permissively licensed free software and objecting to both copyleft and proprietary software (like Theo de Raadt), you have the moxie to back this position up by sticking to your principles. (And notably, even though I don't agree with this position entirely, it's one I have a strong amount of respect for.)

However, I think this position is on the decline, and instead we see a different argument on the rise...

The other argument (which I think we've been hearing more and more of) is that copyleft is strategically a poor choice in comparison to permissive licenses for free and open source software.

There are a few reasons you might make this argument; permissive licenses are generally more interoperable with other licenses, but the main reason given is that you'll get more developers and more users on-board this way. Some businesses are uncomfortable with the obligations of copyleft; avoiding copyleft means that you'll get a larger marketshare, and greater popularity means that it's more likely that you'll have more people giving back to your project. Maybe you aren't even worried about contributions; maybe you're making a library and you want as many users as possible even if you're the only active contributor.

You might also not feel strongly about the freedom side of things at all; you might write a library that you're totally okay with being used by only-proprietary-programs; you just want developers to be able to share code and give back to each other or think that you'll end up with better software by following such a methodology, principles be damned. (However, many people who do take this side do feel strongly about free and open source software, they just think this is an easier strategy to iterate toward that goal.)

What I do think is true is that in the software world (but I don't think quite as much in the culture world) we're seeing this attitude on the rise: these days you often hear and see people take the route of "release the code to the projects that aren't your core business, but keep the core bits of your business proprietary if that's what makes sense to you." The move to this trend has been growing simultaneously with the rise of interpreted languages like Python and Ruby, the move to distributed revision control systems, and maybe most importantly, the move to software as a service web applications. This post by GitHub co-founder Tom Preston-Werner, "Open Source (almost) Everything", captures that mindset pretty well.

To say nothing of the culture side of things, the good news here is that for a certain scope on the software side (libraries and infrastructure specifically) this seems to be doing more than well enough. For libraries and certain parts of infrastructure, people do seem interested and willing to contribute back even without copyleft. And we're seeing an abundance of code crop up these days because of it. I think that's great, though I don't think it's actually enough... but more on that below.

In short, arguments to not use copyleft for strategic reasons are fairly common, probably even increasingly common, among many developers. And at least in certain situations, there seems to be reason to back up such a choice.

There's another sort of objection that's actually a combination of the previous two, but in a way that's deceptive and potentially even dishonest. What I'm talking about is when anti-copyleft individuals are arguing for not using copyleft for strategic reasons but mask the argument to sound like a principled, freedom-oriented reason. This comic might help best explain what I mean (based on a true story):

COPYLEFT COMIC
by Chris Lemmer-Webber
+-----------------------------+
|  Don't use that copyleft    |
|  license!  It's non-free!   |
|  It destroys your freedoms! |
|     /                       |
|   , ,               , .     |
|   O o               o O     |
|  \ C /               ~      |
|   '|'               /|\     |
|                 /           |
|   Oh no!  I like free!      |
|     Why isn't it free?      |
|                             |
+-----------------------------+
+-----------------------------+
|  I can't use it in this     |
|  proprietary program        |
|  with my proprietary        |
|  license!                   |
|     /                       |
|   \ /               , .     |
|   O o               o O     |
|  \ C /             __c      |
|   '|'                |\     |
|                 /           |
|  But your license is even   |
|  more restrictive point for |
|  point, and forbids even    |
|  basic distribution and     |
|  modification!              |
|                             |
+-----------------------------+
+-----------------------------+
|  What are you, some kind of |
|  software freedom zealot?   |
|     /                       |
|                             |
|   \ /               - _     |
|   O o               o O     |
|   c                  ~      |
|  <'|'>              /|\     |
|                             |
+-----------------------------+

To the extent possible under law, Chris Lemmer-Webber
has waived all copyright and related or neighboring rights to
Copyleft Comic via CC0.  Paste, alter wherever/however you like.
http://creativecommons.org/publicdomain/zero/1.0/

Let me describe this perspective in another (non-comic) way: the argument is that I'm reducing someone's freedom by using a copyleft license that will infringe on their ability to integrate said program with their proprietary application, that by choosing a copyleft license one is reducing their "freedom to choose what license they want to use". Sorry, but as I said earlier, the reason why it's hard to maintain the freedom-oriented anti-copyleft position is that you also have to object to proprietary software without a mechanism to protect your work from being proprietized (and this particular breed of truly-freedom-oriented-anti-copyleft Theo de Raadt style perspective seems to be on the decline, maybe because it is hard... though as said, I do admire people who truly take this perspective). But if you're straight up looking to proprietize software (or any other works) then it really isn't freedom you're concerned with at all, it's strategy. I actually think that many people aren't maliciously trying to deceive people, they probably don't realize they're doing this. But a lot of people are, you hear this perspective all the time, and the hypocrisy of it is really annoying.

(And, by the way, if you're waving your finger at me over the edge of your macbook about copyleft being nonfree while committing to your GitHub account in-between working on your software as a service web application and the game you're working for the iOS app store, sorry, but I'm not going to take you seriously.)

Please don't deceptively use arguments about user freedoms when user freedom isn't your primary concern, it diminishes those who are actually concerned with principles and diminishes your own argument when you had a perfectly good one already, one of strategy.

On the support side, I think things are generally simpler to analyze. Actually, there's one perspective on supporting copyleft that I think is in decline but has traditionally played enough of a role that it's worth observing: the financial incentive of proprietary relicensing. The basic idea here is that the copyleft allows anyone to release free work that integrates with or extend your own copylefted work, but if they want to release something proprietary that integrates/expands with your work, they need to relicense with you.

Over the last decade this strategy was very popular, but seems to be rapidly on the decline for I suspect a couple of reasons: 1) it's not generally as lucrative as organizations might like and 2) if you get outside contributions and don't just throw code over the wall, you generally need some sort of copyright assignment or contributor agreement. People seem less and less willing to sign such things these days and furthermore they delay integrating contributions (today's distributed collaboration systems have gotten people used to being able to get their contributions integrated very quickly into a codebase).

From my perspective, the decrease in this trend is probably not much to be sad about, but it does probably help point to the perceived decrease in copylefted works.

Now for the main reason for supporting copyleft: as a strategy (or even as regulation) for preserving user freedom. I think I'm fairly right in pinpointing this as strategy, I'm not sure I know of anyone who seriously thinks that copyleft is a matter of principles (the FSF directly says "Which license is best for a given library is a matter of strategy, and it depends on the details of the situation" in the article Why you shouldn't use the Lesser GPL for your next library) and it's certainly not a requirement for a work to be considered either free software or free culture. The question really is then, if we have preserving user freedoms in mind, is it a good idea?

Copyleft supporters tend to think yes, it is: going back to the judo move metaphor, there's simply too much risk right now of being beaten up otherwise, so some sort of form of self defense is necessary or at least very useful. By adding a requirement that others share alike, we've helped to make sure that the commons is not commandeered by interests that might not otherwise personally care about user freedom.

So what do I think? Actually, I already stated it: I'm in the conditionally-consider-whether-or-not-copyleft-is-good camp. I am in the concerned-with-user-freedom camp, and I don't feel bad about having a license condition that you're only violating if you're proprietizing things. So a more important question to me is: is copyleft the most strategically beneficial licensing option? And, as I keep semi-saying, it depends.

I think it's worth recognizing that libraries are doing just fine without copyleft. In fact, it's now the case that almost everyone who releases libraries does so under a permissive free and open source software license. And people do seem to be contributing back to those libraries, as much or more than they would be if they were under copyleft (mainly because the scope of people using them is higher and because people seem to realize that you're lowering maintenance costs by trying to give back your contributions into an actual codebase, plus it feels great to have your code merged into a library you love). So as for libraries, I think maybe copyleft isn't so necessary these days as it used to be.

But a world where only libraries are free is also a world where developers are free and users are not. As someone who believes in user freedom, that's not acceptable to me. So if not libraries, where does copyleft hold value? And the answer is obvious: applications. Applications have traditionally been the areas that have had the strongest copyleft. They're also the area that's receiving the least amount of attention from a free and open source software perspective in emerging areas right now (web applications and mobile applications). Particularly I'm interested in the web world, where we're winning on the library side and losing on the application side. What we do see is that free and open source web applications still have a high proportion of copyleft licensing (think Wordpress under the GPL and StatusNet under the AGPL). I suspect copyleft has a huge role to play here yet.

An addendum: I wrote this blogpost a while ago, but continued to procrastinate on publishing it for some reason. On that note, I've just come back from PyCon, which is an amazing conference, but one generally that has a strong amount of the "release your libraries under a permissive license, and snark on people who use copyleft" type attitude (pretty much exactly in the manner of the Open Source (almost) Everything article). Surprisingly, despite having a big logo of AGPL in our poster session on MediaGoblin, we only got one person who snarked at us for the license choice (a pretty lame snarking at that, which was "I think people who use copyleft are insecure", which sounded like hyper-masculine chest thumping in licensing wars form). What I wanted to say in response to that person, but which I failed to do, was to say: I think permissively licensed tools are still great, but I use copyleft in the space that you probably would have proprietized it. I don't want to just "open source almost everything"... I want the whole stack to be released as free software. It's not just developer freedom I'm concerned about, it's user freedom. And I think that's probably the difference.

Another addendum: It's been pointed out to me that maybe my position on "libraries are doing just fine without copyleft" misses that, for example, the state of Android device lockdown might be less abysmal if that ecosystem were copylefted. That's a fair point, though I'm really honestly mostly a web developer and speaking from a web developer space. In the web world, I feel like the type of people who are traditionally copyleft advocates completely fell asleep at the wheel for a while, and the generation of (erk) "rails community" type people took over. And where they've driven us to is a place where the whole ecosystem is so close to being free, but people stop right before finishing the job. And if I wrote copylefted libraries in this space, for the most part, people will just not use it. So why not just be allies with those people, and in the space that they normally lock things down, I can release things as copylefted free software web applications?

This month is going to be pretty intense... maybe I should even say "pretty insane". I'm going to be at three different conferences. Maybe I'll see you at one?

• PyCon -- I've been attending PyCon every year since 2008. As with most years, I'll be on the video crew. Last year I gave a talk on Blender's Python API (video here). This year I missed the deadline to give a talk, but I will be giving a poster session with Deb Nicholson on MediaGoblin. (Deb handles most of our press related stuff, including writing up most of our blogposts. She does a really great job!) PyCon is always a fantastic conference, and apparently news of that has gotten around. This year both the hotel and admission to PyCon sold out a month in advance. Yow!
• LibrePlanet -- This year I'll be presenting with Mike Linksvayer about Creative Commons. I suspect it'll be a fairly wide ranging talk, going from the 4.0 license process to bridging Creative Commons and free software. Unfortunately, I'm attending a wedding on Saturday, so I'll only be around for Sunday. However I'll be in the Boston area for a few days afterwards, crashing at Deb Nicholson's place. If you want to meet up, let me know.
  Not sure if somehow MediaGoblin will tie into this whole thing, but in a sense it's very pertinent to LP2012 since it started right after LibrePlanet 2011 (which I didn't attend), is a GNU project, and I started planning it immediately after LibrePlanet 2010 when I finished up my work with the FSF on Patent Absurdity (debuted at LP2010; I did the animations for the film as mentioned previously.
• Flourish -- I'll be speaking at Flourish this year on (surprise, surprise) MediaGoblin. Flourish is a good conference, in Chicago, and really cheap. In fact, it costs nothing, and if you register in advance you can even get a free (as in t-shirts) shirt. It's a good "tech and culture of free software" type conference.

Wow, that's a lot of conferences! And a wedding! Yesterday my friend Will commented to Deb (whose life is pretty much nonstop conferences) "I don't know how you do it. I do a conference and then I have to hug myself in a dark room for a month to rejuvenate." Too true. I think after this month is over I'm going to have to reconstruct myself in a bucket for a day or so.

I got interviewed about MediaGoblin on the excellent Frostcast of FrostbiteMedia. This happened over a month ago, but life has been intense, and better late than never in blogging it. Anyway, I talked to Jonathan Nadeau who runs the podcast, and even though FrostbiteMedia doesn't specifically say so, this episode is released under Creative Commons Attribution-Sharealike 3.0 Unported. (mirrored here)

(Your browser doesn't appear to support HTML5 audio, but I mirrored the file here.

Anyway, I've given it a few listens, and I'm super pleased with how it came out. We talk about the motivations behind MediaGoblin, the underlying architectural decisions, and even a bit of my own free software personal history. It went by really fast... hard to believe the show comes out to about an hour. (It was also my first time being interviewed on a podcast or anything of the like before, and I had some dumb self-inflicted technical difficulties. Luckily, Jonathan was very patient.)

By the way, I have a lot of respect for Jonathan Nadeau. Jonathan is not only a free software activist, but also a blind user of free software. He's also starting a nonprofit called the Accessible Computing Foundation which aims to make the life of computer users with various disabilities better by improving the state of accessibility in free software. Very cool and noble goal. There's a good interview with him on this Linux Outlaws episode. Best of luck to you, Jonathan!

There's been plenty of discussion on the blogosphere already about Gnome 3 already, and I'm not sure this post will add much to it, but whatever. A lot of people hate it. A lot of people love it. A few people love it, but hate certain things about it, but are optimistic that things are bound to get better in the future, in which case they will completely love it. I'm in that latter camp.

Let me put it this way: I recently got a new laptop, a Thinkpad X220 tablet with a gorilla glass screen (yes I am trying to make you jealous, because this is probably the best computing purchase I have ever made in my life) and before I wiped windows and installed Debian testing on it, I decided to try out a Fedora 15 live USB key to see how nicely gnome 3 felt. I instantly began to crave that this could become my regular desktop environment. Especially in tablet mode, damn, it's really great... but even in not-tablet mode, it's still really great. But I installed Debian anyway because I'm pretty used to it, and pined for the day when Gnome 3 would become available in testing.

Sometime last month, that became available. I upgraded and never looked back.

...well, kinda.

Gnome 3 has been really great on my laptop, great enough that I eventually lost patience with my desktop (on which I was running StumpWM, which I mostly enjoyed except when I wanted to use the GIMP, which is often, but that's another post of its own that I'll never write) and upgraded that from Debian stable->testing too. For the first few minutes, I was in heaven. Then the pain points began to set in.

The main issue is that it keeps crashing on my dual monitor + nvidia setup. I did file a bug for this, but a pretty miserable one. There's no -dbg package in Debian, and I haven't had the time to compile gnome-shell from scratch to test it, so I just haven't been able to submit a decent report with a backtrace. Lame, I know. But when it crashes on my dual monitor setup (which happens once every hour or two), it usually fails to recover and makes me log out, and then I lose all my work. And then I'm sad. It turns out this isn't just the proprietary nvidia drivers either... stunningly enough I got the nouveau drivers to work on my desktop and they work pretty damned well. (Okay, the overview doesn't seem to work for me, but that still seems to be pretty good progress. Did I mention that Blender runs well with nouveau too? Pretty exciting.) That's the main reason I switched away on my desktop though... and bugs happen, I'm not meaning this post to blame developers for that, just including this for context's sake.

But another thing, the Gnome developers currently seem to be unconvinced that persistent notifications are a needed feature because they clash with the primary design philosophy of Gnome 3, which is that the shell shouldn't interrupt you from whatever you're working on. I can understand this theory, but the fact is that it's simply wrong. I need to treat my IMs like a queue... if I miss a message from a coworker, I need to respond to it. And to respond to it, I need to know it's there. The fact is, sometimes when I am hyperfocused on my task (when the goal of gnome shell is succeeding), I will miss the subtle hints of messages, and I need to come back to them at some point. Anyway, there's an extension for that, but it requires gnome-shell 3.2, and Debian testing only has 3.0 in testing at the time of writing. Which means I'm back to pining for a gnome-shell Debian release. I think this is a bigger deal than the developers are acknowledging, and it's something that should be provided by default; 3 of my coworkers switched to gnome shell then switched away to XFCE largely because of this issue. That's a pretty big deal, and I think it's something that should be addressed part of Gnome core, as not everyone will learn how to install extensions (not everyone will in Firefox either).

But here are a few counterpoints to that: extensions do exist, and they seem to be capable of doing a hell of a lot (even including providing a tiling window manager if you're willing to run a modified mutter). And people who are doing the most complaining like "Gnome ruined everything! We had a perfect desktop! It's all dead because the Gnome developers killed the free software desktop!" I wonder how many of these people were around for Gnome 2.0, which was also not a perfect desktop either. In fact, around Gnome 2.0 I also switched away from Gnome in frustration, experimented with a bunch of different window managers, and eventually came back somewhere around 2006 and was surprised to find that everything was just so damned... pleasant. I think the same thing is going to happen to Gnome 3 also. In fact it already is. And I think this guy put it right: thanks to extensions, and given some time, plenty of users can be frog-boiled into loving the change in desktop paradigm. That is, assuming that the developers and designers can come to be convinced that walls users are running into are real walls. And they probably will.

One last thing, and this might be rude. I've had a number of friends who have been involved more closely in GNOME than I am complain that there's a large amount of cliquishness in the GNOME world, and even between separate parts of the contributor teams (developers and designers not really talking and working directly together?). I don't really know if that's true for sure, I don't work directly on GNOME, but I trust the friends who have said it, and I've certainly seen plenty of other projects do this at least. I've felt pretty strongly that avoiding this kind of cliquishness in MediaGoblin has been a big win for us. I hope it isn't true for GNOME, and if it is, that they can work on trying to avoid that. But maybe I'm just talking out of my ass on this one. I would prefer that I was. But if not, hopefully people can realize that in-crowds in projects are not the way to go.

Anyway, a sure sign that Gnome 3 is the future for me at least is that when I am using XFCE on my desktop, I do keep moving my mouse to the upper left corner and being sad when nothing happens. I keep using my laptop more because Gnome 3 is working there. And I keep refreshing the status of Gnome 3.2 in Debian page. Given enough time, and assuming the developers can take the needs of their users seriously, I do think Gnome 3 is the free software desktop that most people will come to love.

Or, at least, ten years in the future when contributors kick off Gnome 4, I think Gnome 3 will be the desktop that everyone will be upset at being taken away and replaced with something else.

Today I went in for an exploratory surgery... a very minor outpatient procedure. Actually, I've never undergone surgery before. As the anesthesiologist put me into sedation, I handed the book I had been reading over to Morgan (one of if not the first programming books I had ever picked up, which was on C, and which I decided was time to seriously revisit). Morgan said to me, "Basically, you'll go to sleep before you know it, and then you'll wake up, they'll tell you it's over, and you'll be like 'What, already?'"

As I sat in the surgical room and started to space out, I was still thinking about coding, and my thoughts about coding must have started to shift over to MediaGoblin and its community. Suddenly I was at my computer. I started writing a blogpost, full of all the things I've been thinking about and have learned by working on the project over the last many months; my thoughts on community, releases, communication, everything. I ran it through ispell-buffer. I was super pleased with it. I was ready to commit it and push it over to my site.

Then I woke up to a nurse telling me, "That's it, we're done, you can wake up now!"

"Damnit," I mumbled. "Now I have to write that whole damned thing all over again."

Today I received a call from my friend Miles telling me that one of our mutual close friends, Matt DeSpears, passed away by taking his own life. It's hard to pick the appropriate words to describe how I feel upon hearing this news. "Shattered" and "devastated" are words that come to mind, and yet even though I feel like I am both of those things I don't feel that I have fully processed it yet. How do you describe losing one of those people who you just take for granted as a constant in your life?

I don't really feel like I am thinking completely clearly, but I feel compelled to write. And I feel like Matt deserves a proper tribute. And maybe the most appropriate time to give that tribute is right now, when I am most overwhelmed with emotion.

Matt, like many of the people I know and love, was a misfit. I don't mean this in a negative way: the people I love most in life are misfits (and I consider myself one of the biggest misfits of all). Being misfit means your character is likely to develop into something unusual, and the most unusual people are often the most beautifully interesting. Matt was even more misfit than most, and I loved him dearly for his unique character. There will never be another Matt. But being a misfit also means that it's harder to fit into the rest of the world, and that was especially true for Matt.

I met Matt at an alternative school called Kradwell, which I transferred to in my junior year of high school (as I was nearly failing out of school due to my social issues and trouble coping with my attention deficit disorder). I quickly came to love Kradwell. At Kradwell, my social problems vanished. I used to joke with people: nobody makes fun of you for being a freak at Kradwell because at Kradwell, everyone is a freak. Instead of resenting how weird I was, I came to embrace it. I met many friends there, all strange in their own wonderful ways. One of the friends I met was Matt.

Photo of Matt DeSpears from the Kradwell yearbook

It took a while for Matt and I to become friends. Matt had a certain amount of awkwardness that was high even by Kradwell standards. But eventually I did come to know him, and one time I invited him over to a get-together at my house. I don't really remember the details, but I remember that day becoming a day when he became more integrated into the group of friends I was meeting at Kradwell. It was also around the time that my group of friends at Kradwell became integrated with my older group of friends from childhood. Without any realization, we formed a close knit group of friends that had continued to be strong even until this day, which my wife and I now call the Milwaukee Crew. I came to love this group of people, not just individually, but as a group: bonded through a mutuality of friendship and antagonism. It had that kind of dynamic to it that you can't force into being, that just develops, and you come to enjoy. Whenever I've come into Milwaukee, the Milwaukee Crew would assemble... or whoever of us were around. Morgan would sometimes remark about how resilient our group of friends were, still meeting together and making the same old jokes, expecting the same quirks... I thought it would last forever...

As I said, Matt was more awkward than most, but underneath that shell of awkwardness was a true warmness. Matt had a very fuzzy and puppy-dog like personality to him when you knew how to reach it. The truth of the matter was, Matt just wanted to be loved. I guess that's true for everyone, but even more so than for most people, that's how I think of Matt.

Matt also loved to antagonize people. We all did, but there was this certain flavor of antagonism in Matt that's really hard to describe. I remember Jay driving Matt and saying "Which way should we turn, Matt?" and Matt said, "Pope." "No seriously, which way do we turn, Matt?" "Pope." "No seriously, we're about to pass the light, which way do we turn?" "Pope." Maniacal laughter ensues, as Jay drives through the intersection yelling with frustration. (Edit: Apparently it was a highway off-ramp, the next intersection wasn't for miles, and I wasn't even in the car. But the memory has been strong enough in our group that I've remembered it as if I was.)

It might be hard to understand how that could be lovable, or even entertaining, but maybe you just weren't there. For years, we've groaned about this story, but behind the groan was a fondness for the memory, for the dynamic that unrolled between our friends.

There are other things, too, that I remember fondly, that seem like they will never be able to happen in the same way again. All night LAN parties playing CounterStrike, with Jay and Matt getting angry at each other over some tidbit. Playing a prank on Matt so we made it so that every action on his computer elicited the noise "whoop-da-doop-da-doop!" and watching him getting angry as he couldn't turn the noise off. Later (after it was disabled), he became obsessed and in love with that noise, as we all did. It's just one of those inside jokes that all of us became obsessed with that nobody else could understand the meaning behind.

I also remember that Matt became obsessed, as a few of us were, with an MMORPG that existed before that term existed called Graal, which was basically Legend of Zelda in 2d online. Believe it or not, this proprietary game partly led me to become obsessed with the idea of free software as it was completely scriptable, and for a time, anyone could run their own server which meant that anyone could build their own universe. Then they took the ability to run your own server away and I became angry and... hm, that's a topic for another blogpost. The real point is, after a good number of us stopped playing, Matt continued playing the game, caught up in that online social world. We used to antagonize him about it, and then he asserted that he stopped playing the game altogether. Later, Miles and Jay would sneak across the side of his house and take a photo of him playing the game. He was furious. But eventually he came to laugh about it, as we all did. Filed into another memory of fondness in the Milwaukee crew. And there was something about that game that seemed to reflect something interesting about Matt, maybe about all of us. The promise that you could build your own universe, and the ability to escape into another one that wasn't as painful as your own. Matt became an administrator on the server. One day Matt had shown me that he had built an entire trading card minigame inside the game itself that had a bit of a following, even a fansite. He had never programmed anything else in his life. He just did it. I don't remember Matt ever doing anything else like that before.

This is either Miles or me chasing Jay in a cardboard robot suit. I think it's Miles. Regardless, it captures the spirit of the times and the crew.

I could go on into infinity listing off fond memories, and I'm a bit tempted to, but I think maybe I shouldn't. But here are a few of the ones I remember the most fondly:

• Creating cardboard robot suits and beating each other with plastic bats to the confusion of our neighbors.
• Hanging out at The Node, a coffee shop for nerds we all loved (until sadly they shut it down) and playing Risk. One day after a particularly serious defeat, I "whoop-de-doop-de-doop"'ed Matt while doing a dance. Nobody else in the coffee shop knew what I was doing or why I was making a fool of myself. But we all understood.
• Driving around and talking about our relationships, or sometimes lack thereof. Cheering each other up as friends, dropping by to say hello.
• Jay and Miles stopping by to order the most complex sandwich they could order at the sandwich shop Matt was working at.
• Matt's wonderfully strange vocal intonation somehow becoming a manner of speaking that everyone in the crew adopted.
• Various shenanigans at Kradwell.
• Matt's bizarre obsession with the Pope, Battle Pope, and BatPope.
• After I had moved away out to Barat College, Matt, Miles and Jay driving all the way down to my dorm completely unannounced, picking me up and making me come along with them on some adventure. At the time, I acted like it was an inconvenience even though I truly appreciated it. And of course I really appreciate the memory now.
• Hanging out on our private web forum which was entirely full of inside jokes and shenanigans. "Nice" and "Shut up Wesley" being inside jokes that were tossed everywhere on there.
• As members of the group began to disperse, doing various get-togethers in Milwaukee or Appleton nonetheless. Beating each other senseless with styrofoam pool noodles even though that doesn't make any sense because we're supposed to be adults here.
• My bachelor party, which was also a LAN party. We were hoping it wouldn't be one of the last time we ever got to do one of these types of things again, but knew that it probably was.
• Matt being one of the ushers at my wedding, with Jay as my man of honor, Miles as one of the groomsmen (the others were siblings). Several other members of the Milwaukee crew (Claire, Dani, Fatch (Jon), Corinna, Jeni... and I am probably missing a couple others) weren't in the wedding party but were in the audience.

Matt, Miles, myself, and Jay (in order) at my wedding

I think, more than anything, I am sad that in all of our get togethers there just won't be a Matt anymore to recollect with. There will just be an empty seat and a memory of Matt. It seemed like it would last forever, be a constant in my life, and yet now it will never be the same.

A couple weeks ago I was going stir crazy from living in DeKalb. Those of you who know me personally know that DeKalb is not exactly my favorite place to be, but we're here because of Morgan's grad school program which I am supportive of (and we can do because I have the good fortune of working remotely as a programmer). I decided to go to Milwaukee to visit friends and family for Thanksgiving and even take a few days off to work on some of my own projects. Right before I left the car broke down... but we decided that it was important enough to blow the money on a rental car so I could get out of town.

While I was there, I tried to assemble the crew, but it didn't happen as it usually did. I had the chance to meet most people individually, at least. Matt and I had scheduled to go out and meet one night, but for reasons I won't go into I did something I never did: I got so frustrated over some detail that I canceled. Thankfully, we agreed to go out and get breakfast at George Webbs the next morning.

We talked about relationships, life, work, the usual. It was a good catch up. Matt wasn't upset that I had refused to meet with him the previous night, or he didn't show any animosity. After we got breakfast we went to American Science and Surplus and walked around and looked at various things. I considered buying several things but didn't. Matt bought a keychain container for his medication. It was a nice and quiet walk through someplace that we both cherished. I was a glad we had that opportunity to get together for it. Afterwards Matt suggested I meet his father, as I had never met his parents strangely in the more than ten years I'd known him. We walked in, his father was preoccupied but said hello, Matt and I shrugged, he grabbed an iced tea from the fridge, and I drove him home. Prairie Home Companion played on the radio, which I love, and Matt had never heard. It unusually wasn't a good episode, not even the part with Guy Noir, Private Eye, and I felt bad that I didn't give Matt the opportunity to appreciate this show I really enjoyed. But he didn't mind. I dropped him off, we cheerily waved goodbye, and I drove home thinking I was glad we had that opportunity to hang out before I left.

Today I received a call from my friend Miles. He asked me to make sure I was sitting, which I was, and then told me that he had just heard from Matt's nephew. Matt had gotten into a fight with his girlfriend, swallowed a bottle of pills, and passed away.

Matt was a strange and wonderful person. Like many of us strange people, he suffered from depression and various other issues. I also in many times in my life, have suffered from depression, and have come close to attempting suicide on several occasions. I am glad I have not done so, as I probably would have become the same thing to others that Matt will be now: a dearly loved friend who is no longer there, an empty chair at a coffee table in a gathering of friends and family. I will miss Matt dearly. He was a great friend.

I want to say one more thing in this post before I close it out. Matt had a son whom he rarely got to meet in this life. If that person ever reads this, I want you to know several things about your father. First: he regretted not being able to be a better father and blamed a lot of this on himself. Family issues can become complex, as they were here, and at one point Matt thought he should finish school before he was more supportive, and then that never seemed to finish, he wished he could move down and be with you, and that never seemed to pan out. But he wanted to be there for you, he just didn't know how to get to that point. Second: your father loved you. He would show me pictures of you, he would talk about you, and he wanted nothing more than to figure out how to be there for you, and the fact that he wasn't was a great source of sadness and guilt for him. But when he spoke of you there were moments of inner pride and happiness that I never saw otherwise. And I wish that things could have worked out so you could have gotten to know your father and loved him as I did. He was a wonderful man, in his own curious way. Third: he would have wanted you to be happy, to do good things, to enjoy life. There's nothing he would have wanted more than that.

And to all others: if you know someone who is awkward or strange, be nice to them, embrace them; they need it. And if you yourself are strange or weird, don't be afraid of this, learn to love it.

Matt, I will miss your strangeness, your wonderfulness, your kindness, your friendship. Around the coffee table of my heart, there will always be a seat for you.

Edit: I tried to incorporate some text earlier into this post to make it clear that I don't think Matt's girlfriend was to blame. I honestly don't think she was. I haven't always gotten along with Matt's girlfriend in the past, but when I met with Matt for breakfast he expressed to me, "I know you guys don't like hanging out with her, but I love her, and she makes happy. I'm happier now than I have been for a long time." And I agreed... he did seem happier than he had been in a long time. This is partly added to the surprise of this news. I spoke with Matt's girlfriend and heard her side of the story. I didn't think she was to blame before, and I especially don't now. Couples' fights happen... and Matt was close to the edge for a long time. This event is going to be hard on a lot of people, but probably especially it'll be hard on Jackie. Please don't put any more grief on her shoulders than she is already going to have to bear.

It seems like it was just a few months ago that I switched my blog over to Zine. Well, actually it was a little bit over a year ago, but I've barely blogged since then. :\

Actually the fact of the matter is that I thought that by switching from my homerolled blog to Zine that I'd feel less frustrated about running my blog because it wouldn't just be some homerolled software that I was running, and I could contribute back to some larger project if I wanted to. But Zine turned out to be unmaintained basically, I wasn't really interested in spending time contributing to it, and most significantly, I didn't enjoy using it. Not because it's bad software, I just didn't enjoy blogging in it, the same way that when I blog in Wordpress for work I just don't enjoy it. But lately I've been blogging for MediaGoblin (well, a lot of the actual writing is done by Deb Nicholson). http://mediagoblin.org is actually done using PyBlosxom (a project maintained by friend and fellow MediaGoblin contributor Will Kahn-Greene) and I've come to realize I really enjoy writing in a plaintext site/blog setup I can just keep in git.

So I switched over. However, I already had the site using Jinja2 templates for Zine and Ventriloquist (something simple but semi-neat I should really write about) so I figured that why not shave a whole herd of yaks and add a Jinja2 renderer plugin to Pyblosxom. So I did, and actually... I'm fairly happy with it. I also think this plugin could maybe be a cool direction for PyBlosxom, but... more on that later maybe?

In the meanwhile, most of the site is ported over, some embarassing things are cleaned up, and a few things are now also missing. Namely, comments and tagging. Tagging should be back soon, but I'm not too sure about when comments will be back. Oh well, nobody was commenting on here anyway. (I have the old comments stashed away on my hard drive but they aren't on here yet for now either.)

Anyway, that's it for now. Now I'd better write a whole bunch more blogposts so that this blog doesn't become one of those crappy blogs where people just blog about (not) blogging. I guess it already kind of is...

I'm going to keep this brief. Or rather, the original content brief. We've launched a project called GNU MediaGoblin (yes, it's an official GNU project) which is going to save the internet from media hosting homogenization.

Well, hopefully! It all depends on how well we can organize ourselves, work hard, and organize our contributors. Anyway, read the announcement post. Sound interesting? We could use your help.

Here's some more info:

• About GNU MediaGoblin
• How to become a contributor
• Docs! (Especially the Hacking HOWTO.)

So far I've spent the last month putting down infrastructure, but we just announced the project this week and are getting a lot of interest. The founding team is a pretty solid group of people I think, and we've got a number of people interested in contributing. Again, we could use more. This weekend I'll spend a bit of time making it easier to get involved.

Lastly, here's our mascot goblin:

I think he's pretty cute. By the way, if you contribute to the project and do a copyright assignment to the FSF, I will probably make a cool unique goblin dedicated to you. Copyright assignment on this project is not mandatory, unless you want the goblin. :)

Since announcing on Monday we're already starting to get quite a bit of press. See:

• On NetworkWorld
• On LWN (points to the NetworkWorld article)
• Some German article
• Another German article?
• Another article I don't know how to read, this one in Spanish

... and since I had an interview last night, more is coming. I'm kind of stunned, honestly. I want to say "not bad for a project that just announced itself this week" but that understates the amount of surprise I have here. We've got some cool people jumping on the project (we could use more!), a fair amount of infrastructure for a project that's just barely launching, and a lot to organize. You can check out and run the code and there isn't a lot there from a user perspective (a lot more from a dev perspective) but hopefully soon we will be so beautiful you just won't be able to resist. We're still kind of running on hopes and dreams here, and hopefully those hopes and dreams can become true. It'll be a lot of hard work, but I think we can do it. At the very least, we need to try!

Comment on this post on identi.ca!

I have a huge backlog of blog entries I've been meaning to write about interesting things I've done recently, but haven't written because I often feel like I should be doing interesting things instead of just writing about them. Luckily most of the things I've done online recently have some sort of interesting web presence, so I'm just going to link to a bunch of them and call it a day:

First, conference stuff:

• I attended PyCon, and even gave my talk on Blender & the new Python API and it was extremely well received. There were some really great competing talks going on at the same time, but people who saw it really seemed to like it. PyCon was great, and the people were even better. Particularly I really enjoyed hanging out with good friends Asheesh, Karen, Bassam (who was on the video team recording my talk... hilarious that the director of Elephants Dream & Tube was recording bits of me talking about some of his projects), Will, Carl, my friends from my old work at Imaginary Landscape, and many I'm surely missing and I'll feel terrible about later.
• I'm going to attend Libre Graphics Meeting 2011 and once again I am talking about Blender, this time in relation to Patent Absurdity and using Blender for activism animations in general. I'll also be on an autonomo.us panel, representing CC and... something else I'll talk about in my next blogpost. :)

Next, even though I've been mostly silent here, I haven't been at work (well, I should be doing more work blogging, but anyway). On the main Creative Commons blog I've written the following:

• Massively Multiplayer Game Ryzom Released as Free Culture and Free Software
• An interview with Ton Roosendaal of the Blender Institute on Sintel's release -- I really loved doing this interview, as I have a massive amount of respect for the Blender Institute and what they're doing. I snuck a question in there about the modeling sprint which, if you read that post, you might notice that I actually had written to them and suggested the format of said sprint (I'm attributed as "cwebb" in that post). Apparently the modeling sprint went rather well (the animation sprint less so though... you should read the interview!).
• If that wasn't enough, I did a second interview with Ton Roosendaal about the Sintel 4k release.
• I also made available and wrote about plaintext versions of the CC licenses and CC0, which is something many free and open source software developers wishing to package CC-licensed content with their works have wanted for a long time.

That last one (the plaintext legalcode) was actually a side effect of something even more exciting: Using CC0 for public domain software, and CC0 compatibility with the GPL. I didn't write this blogpost (Mike Linksvayer did) but I was heavily involved in this process. For about half a year we had on and off conversations with the FSF (particularly Brett Smith) about GPL compatibility. At this point there had been nothing clearly marked about CC0's acceptability for software or whether its fallback license was GPL compatible, and for a tool that's all about internationalizing the public domain this seemed completely crazy (well to me, anyway). I made the assertion that getting CC0 on the FSF's free software licenses list and being noted for GPL compatibility would be the gold standard, and I am very happy that this is exactly what we achieved. Honestly, keeping the website running, maintaining our tools, etc is pretty great, but I think this may be one of the most important achievements I've made while working at Creative Commons. (As a side note, I think this means maybe that CC0 is now the only legal option for something that is simultaneously both free culture and free software (like some game assets) without dual licensing?)

I've also written up some more technical posts on CC Labs:

• Understanding the State of Sanity (via whiteboards and ascii art)
• cc.engine and web non-frameworks
• Using virtualenv and zc.buildout together
• Orgmode and Roundup: Bridging public bugtrackers and local tasklists
• LibreOffice and CC OpenOffice Plugin: Good to go
• More helpful 404 pages
• Your own python egg baskets / package repositories
• A post with good advice for GSOC students (Sadly, due to a lack of bandwidth, we only were able to accept one GSoC student this year, and that student switched projects, so we simply aren't doing GSoC this year. Oh well.)

I've also been doing quite a bit of work on Tube doing python scripting and the like. I'd like to write more on this soon. Maybe I'll guestblog over there eventually.

Oh, and of course, even though I'm usually silent here, I am in no way silent on my identi.ca microblog.

That's all for now, or rather, all I'm going to bother to post. There's actually something much more exciting I'd like to mention, but I'll do that in the next post.

Update: There's another reason I haven't posted much. A while ago I switched my blog over to Zine and thought it was a great move because at least I wouldn't be maintaining my own blog software anymore. But Zine is now also unmaintained, and I haven't set up any sort of spam filtering system, which means at any time I have about 1000 unfiltered mostly spam comments to go through, and every time I think about blogging I get exhausted thinking about filtering through those comments. I had a crappy accessibility-breaking captcha on my old blog, but at least it worked. Until I figure out a better solution, and frankly I'm too busy to probably do that immediately, I've taken a tip from Bradley Kuhn's blog and am just going to use StatusNet's great comment threading as my comment thread. :) If you want to comment, you'll have to use something OStatus enabled. For now.

Comment on this post on identi.ca!

Are you going to (the US) PyCon this year? I am! And I'm pretty excited about it, since I will also be presenting on Blender's new Python API!

The talk lineup looks really great this year. If you're planning to go, and you read this, maybe consider contacting me; maybe we could say hello, potentially having one or more interesting conversations!