Okay, it's not me that needs your money, it's people living with multiple sclerosis (MS).

After we survived last year's swim, we're again swimming in the Fitzroy 24 Hour Mega Swim, a 24 hour relay. My contribution will be somewhere between two and three hours of swimming over the 24 hours (plus hours of counting other people swimming up and down). Rachel will do a couple of hours too.

The aim of the swim is to raise funds for people affected by multiple sclerosis, the most common disease of the central nervous system. MS strikes young adults (the average age of diagnosis is 30) and over 20,000 Australians are affected. The ratio of women to men is 2:1. It's a crappy disease to get.

I don't ask for money often, and never for myself. If you feel so inclined, please take a moment to visit my fundraising page and consider giving a secure donation (there's a donation button on the right hand side of the page).

A tax deductible receipt will be emailed to you when the transaction has been completed. That's good in Australia, does anyone know if it counts overseas as well?

I just signed up for Amie Street after a recommendation from Owen (a recommendation he gave months ago), and the site looked really promising. Lots of my favourite artists were represented, with links to promising sounding stuff I didn't know.

I happened to be chatting about music with Andy C while signing up, recommending The Kills to him (he reciprocated with Brakes). I had a quick look to see if Amie Street had any stuff by The Kills that I don't have yet.

However, I'm in Australia. That means I'm not in the US. And that means, all those little "N/A" flags on most of the music that I was interested in.

I know it's the fault of the record companies rather than the music sites, but for fuck's sake, can't we get past this shit? I'm so sick of not having access to stuff because I'm in Australia. I would have bought a couple of albums right then and there, but instead I have annoyance and a growing sense of hatred aimed at arseholes in suits.

After a short while trying to find music it quickly became obvious that the amount of music marked as unavailable in my region makes Amie Street frustrating and unusable for me.

[Update: I should be absolutely clear that I don't blame Amie Street. I also sent them a note, and they gave a lengthy and reasonable response. Yes, it's the content providers, Amie Street are trying to get more liberal licensing, in the meantime they're working at hiding the content that's not available.]

Damien Katz of CouchDB:

We don't want people who tend to ask "How can I contribute? What should I do?". We want people who identify for themselves what needs to be done and how they can contribute, and then do it. Our employees want to contribute to make things better, not for a paycheck, not for validation from a manager or even the community. They do it because they think it will make things better.

Damien Katz: Thoughts on an Open Source Company

He's talking about running a company based on an open source project, but the sentiment is valid for any project. There's a flip side too though; open source projects need to provide a structure where it's clear how people can contribute, make it clear that if you start on X or Y you're not going to tread on someone's toes.

It takes good communication on both sides, project and newcomer.

What is it with me and music sites? First I became a disgruntled ex-emusic customer, and now I'm a refugee from thesixtyone.

How did thesixtyone fall from beginning to fulfill my music wishlist? Not long ago, James and Sam, the guys who run t61, announced that they finally understood the way forward for the site. Last week it launched, and apparently the relaunched site has had positive feedback from sites like TechCrunch. For those on the site, the people in my community, I think the biggest reaction was ... WHAT ... THE ... FUCK?

The biggest attraction of t61, for me at least, turned out to be the community. It was great to chat to people in my group, the Beat Geeks, engage with artists, and talk to other users. On the whole, that was how I found music that I liked. And that's exactly what I feel that the redesign took away.

This is what the Beat Geeks group page (or channel, as it's now called) looks like now.

The background image changes, depending on what music is playing. What used to be on that page was the top five songs the group was playing and the discussion that was going on between members. Can you see the group discussion? If you click on the tiny link 'discussion' in the box on the bottom right, the discussion turns up in the box. That little tiny box down there is all that's left of what was one of the most engaging things about t61.

There are other things that drive me mad about the new site. I find it terribly difficult to navigate, with all the links hidden away. The changing pictures are a distraction too; I'm here to listen to music and engage with people, not watch pseudo video clips. You can no longer browse around the site because going to a new page changes the music. And possibly worst of all from my straight user experience point of view, the new site insists on starting the music again after I've paused it. Finally, it doesn't even seem possible to leave a message on an artist's page any more. That's not a step towards bringing fans and artists together.

I don't feel angry at Sam and James, as I did with the dishonest money-grubbers at emusic, but I feel disappointed. I think they've made a mistake, that they've damaged the thing that made the site engaging and special in the first place. Of course, I may be wrong, and only time will tell, but a whole lot of people I know are abandoning the site, and feeling hurt.

Thankfully, a big bunch of those people have moved to a new place, somewhere that's equally community driven, and growing fast. You can now find me on uvumi. Once I find my way around, I'll probably do a write up. Let's hope my presence doesn't kill it.

Via Simon, I heard about the Great Australian Internet Blackout. While trying to keep up with the great disaster that Stephen Conroy has been peddling, I've also been hoping it will just go away. Well, it doesn't look like it's going to go away, and Australia might be joining China and Iran in censoring the intarwebs for their citizens.

In protest, this site will be participating in the Great Australian Internet Blackout. What does that mean? Come back sometime between 25 to 29 January to find out.

The Federal Government is pushing forward with a plan to force Internet Service Providers to censor the Internet for all Australians. This plan will waste millions of dollars and won’t make anyone safer.

1. It won't protect the children
2. We will all pay for this ineffective solution
3. It sets a dangerous precedent

Great Australian Internet Blackout

Along with a host of smaller goals for 2010, there are two major things I have to get done this year. In this post, I'll talk about those two goals and look back a bit as well.

Finish my PhD

Yes, this will be the year that I finish my PhD. I first enrolled in 2004, studying part time while working as an academic at RMIT's School of CS and IT. My main role at the time was the operations manager of the delivery of the African Virtual University project. Like all good roles, it was at the edge of my comfort zone when I started, and I spent a lot of time trying to do it well. In hindsight, I might have been able to delegate some of the work, but I think that was part of the learning experience.

Delivery to Africa wrapped up at the end of 2006, and I saw it as an opportunity to focus on my research, which had been terribly neglected for the three years of my enrolment. I quit my job and went full time. It took a few months to make the transition to full time study, something I hadn't done for more than a decade, and by the time I was starting to gain a bit of momentum I realised I had no faith in the direction my research was heading. Painful though it was, I ditched what I'd been doing and took a couple of big steps backwards, resulting in six months of work that won't make it into the main body my thesis.

From there I've battled with all the usual things that PhD candidates battle with; distractions, procrastination, yak shaving, family stuff, a stint back in industry, loss of motivation, what the hell is this all for anyway, et cetera. But now I'm finally within striking distance of the end, so it really must be finished this year.

That means trying to focus more, compartmentalise the worthy distractions, not spend too much time surfing engaging music sites, and writing regularly.

Establish a reliable, enjoyable source of income

And then what? I could spend a lifetime just exploring the stuff that I find interesting, working on Habari and other open source projects, but in and of itself that doesn't put food on the table. The next goal is much more nebulous. How do I turn the stuff I enjoy into an income stream?

While I'm happy to work hard and work long hours, I don't really want to go back to traditional full-time work, a 9-to-5 job. The idea makes me yawn, though I guess I'd do it if the job was awesome in other ways. I definitely don't want to go back into traditional academia. Teaching can be fun, but it can also suck up any amount of available time, and given the amount of bureaucracy that seems to be required, the chances of getting any research done as a junior academic are slim.

My ideal job would allow me to work on web stuff, interesting open source projects, particularly Habari, be engaged with people. I don't need a huge income, but flexibility is important. I don't want to be tied to a physical location, mostly because I want to be able to work from the farm when we're there and I don't want my work to tie down Rachel's job opportunities, wherever they may be.

I would like to continue to collaborate on research work, stuff related to the web and to open source, evaluating the stuff I'm working on so that other people can benefit from it and build upon it. Maybe twofish creative will be re-energised, and we can do web sites for people we like (we're doing a bit of that, but not much). Maybe I'll start another business with like-minded folk. Maybe I'll do some freelance coding. Maybe interesting projects will pop up.

Whatever shape the thing is, I have to wrangle it by the end of the year. Wish me luck (or, when I've submitted the thesis, suggest something or make me an offer).

I've been thinking about diversity in open source communities for a while now. I believe diversity of participants is a real benefit to an open source project, and I think the one community that I'm heavily involved with, Habari, is pretty open and welcoming. For example, you don't have to be a coder to have your contributions recognised in the Habari meritocracy¹.

Right now, we're in the middle of a vote as to whether Habari should adopt a community and diversity statement. Here's the statement in full.

The Habari project is built on the idea that community is more important than code. As such, we, the Habari community, are committed to making you feel welcome.

We welcome people of any ability level, age, gender, race, ethnicity, religious belief, nationality, and sexual orientation. And we welcome ponies.

Members of the community should always treat others with respect, whatever their background or involvement with the project. Everyone is expected to help maintain a welcoming environment. This means not only policing your own actions, but taking responsibility to point out and take action to stop behavior that could be harmful to the community.

Of course, you are free to disagree with opinions and beliefs held by others, but not to be disrespectful towards them because of those opinions and beliefs.

In general, people are in favour, however there have been a couple of dissenters, the gist of the dissent being that such a statement is beyond the scope of an open source project. Several people have responded that when someone does something bad, this sort of statement is a good thing to point to. Rich Bowen has recently written about how open source projects should deal with bad behaviour, and that's worth reading.

But responding to people doing bad things wasn't what prompted me to start (or at least formalise) Habari's discussion on diversity. Rather, I was acting on a feeling that a project that talks about diversity is more likely to attract diverse participants. I don't know of any formal research that supports that feeling, or even much that's informal. If you do know of any, please let me know.²

I'd like to conduct some informal research of my own.

If you're a member of a minority group or a woman (as a minority in IT and FLOSS), are you more likely to become involved in an open source project if there is an upfront statement of diversity?

1. This isn't meant to imply that people in minorities aren't coders, it's just a comparison to some other open source communities that value coding above all else. ↩
2. There has been some investigation of women in IT and FLOSS, but I haven't found anything that measures the outcomes of various approaches to encouraging diversity. ↩

If Blackboard can’t help you fix your problems, you’re out of luck, because nobody understands their code or has the right to look at it. If your Moodle vendor can’t help you, you can go to another vendor, or find another adopting school that knows how to fix the problem. You can also fix it yourself. You don’t have to, but unlike with Blackboard, you can. Likewise, if Blackboard were to go out of business (ask WebCT or ANGEL customers if this sort of thing ever happens), you wouldn’t be able to find somebody else to support and continue to develop your platform. Not true with open source support vendors.

Blackboard’s Response to Open Source: Fear, Uncertainty, Doubt

The lack of support argument gets trotted out so often to attack open source, and it really shits me. You generally have one support option if you're using proprietary software, the vendor. With open source you have at least three types of support; fixing it yourself (by which I mean literally yourself or hiring someone to do it), paying a support company to do it, or relying on the community fix it through normal processes.

I recently submitted a patch to Weka to clean up some code formatting. Unfortunately, I didn't think testing the patch was necessary but the maintainer wrote back to tell me it had failed to apply cleanly, with many chunks failing.

I couldn't work out what the issue was. These were incredibly simple changes, changing mixtures of tabs and spaces for indent to spaces, and removing trailing whitespace (two bugbears of mine). Running patch with the verbose switch didn't tell me anything more about why it was failing.

I popped into #habari IRC, where the friendliest and most helpful people I know hang out. Luke from Squareweave suggested that patch might be confused because there were many small changes in one chunk, close together but not contiguous. Investigation showed that the whitespace changes were a red herring, and that any changes would fail. The individual changes would also apply if patched separately. So Luke was right.

To get around the problem, I reduced the context (the number of lines that surround the change) when creating the patch. This forced many of the changes into their own chunks, and the patch applied cleanly.

svn diff --diff-cmd diff -x "-C 1" > whitespace.diff

Subversion's internal diff tool doesn't allow you to change the amount of context, so I use the diff-cmd switch to use the system diff, and the x switch to pass in the necessary diff parameter.

And now the patch has been applied to Weka.

So what does it feel like to be a woman in open source? Jono Bacon, at the Community Leadership Summit on the weekend, said — addressing the guys in the room — that if you want to know what it’s like to be a woman in open source, go and get your nails done at a salon. He did this a week or so back, and when he walked into the salon he realised he was the only man there, and felt kind of out of place.

Infotropism – Standing out in the crowd: my OSCON keynote

While I'm on the theme of women in open source, this is from Kirrily Robert’s post about her OSCON keynote, which inspired Rich's observation. It's well worth reading (and doing something about).