Safe as Milk

Mikael:
First, let me be clear – the fee is there to help with the costs of the conference. It is not there to scam people coming to the conference, or to make money. If you don’t want to pay the fee, then don’t. Turn up, and you will not be turned away at the door. We want as many people as possible at GUADEC. If you don’t want to pay the €225 or €150 rate, tell everyone in your company to pay €30. Then sponsor the conference to the tune of what you think is fair.

Let’s be clear – the conference will not make money because of the fee. GUADEC loses money. Sponsorship is not enough to pay for the conference, and when you pay a registration fee, that the money will be going to pay for someone’s bed, or travel expenses, or internet access, or facilities. The foundation will take a hit of a few thousand dollars/euros on the conference, as we did last year.

GUADEC has become a big conference. That’s because there are so many supporters of the desktop, which is great. Starting with Dublin, there was an attempt to make GUADEC appeal more to businesses, because they would pay money to support the conference, and back then it was felt that hackers wouldn’t. So GUADEC stayed free, and businesses and sponsorship covered most of the bills.

Last year, we spent more money getting people to GUADEC than ever before. GUADEC was also more expensive than ever before, because of its size and location. This year, it’s looking like it will be just as expensive. We’re bringing several speakers from Australia, Canada and the US. We’re sponsoring travel for people who need it. And all that takes money.

Perhaps we do need to re-think GUADEC, take a smaller facility (or even a field), announce the thing late, stop having presentations altogether, make it free, and get closer to the way things were in Paris in the good old days I never saw.

At the very least, we need to decide whether we’re a technical conference or outreach to local users and business. 3 days is too short to be all things to all men.

But it is unrealistic to expect that an event the size of GUADEC can be organised with little or no cost, or that the costs can be completely covered by sponsorship. A registration fee is reasonable, in my opinion. And €30 is not a huge amount.

Yet another GUADEC post

As Murray mentioned, GUADEC is one of those times of the year when we really need people’s support.

Support comes in many shapes and sizes – from people who pay as much of their own transport costs as they can to be there, to people who volunteer to sell t-shirts during the event.

One great way to support GUADEC is to sponsor a hacker. Sometimes, people who really need to be at GUADEC can’t get there, because of the travel costs involved. We always do what we can to get as many people as possible to GUADEC, and you can help.

Companies can offer to pay air fare for somebody, and make that be tax free by going through the foundation. Or as an individual, you can give anything from a few dollars to help contribute to the train fare for a poor German student. GUADEC is our Christmas-time, a time for giving and sharing. So even if you can’t be here, come join in the fun.

Camp Stuttgart

A quick reminder that the ultra-cheap accommodation option for GUADEC Camp Stuttgart will be available if there is sufficient demand.

Someone in Germany will be paying a deposit out of their own pockets, so if you want this option, please sign up now on the wiki under the heading “Extra cheap camp”.

The price will be around €30 for the 3 nights of the conference, apparently, bring your own sleeping-bag.

Elijah asked me a question on why I thought the 6 month cycle was too short.

I’ve discussed this with a few people and have been reminded of a Joel Spolsky interview – the grandmother story (“the process is overtuned”) on page 2 caught my eye. Basically, he explains that over the years Microsoft has picked up so many good habits (by correcting their mistakes) that the process (testing, validation and so on) has become more important than the actual *thing* – the product being created.

When you’re on a 6 month cycle, you’re in feature freeze for 3 months. That’s 6 months a year that we’re not focused on new features.

Now, if you move to a 9 month cycle, you still have a 3 month feature freeze per cycle, but you’re only spending 4 months a year in freeze, so you’ve gained 2 months innovation/breaking time. Experiments can happen right in GNOME.

If we stay in the 6 month cycle, the breakages happens outside the main GNOME tree (as Luis said). That’s risky for some young gun to take on in his garage.

As an alternative to the “clean break”, the leap of faith that Luis is talking about, perhaps we can just have a little more madness in GNOME devel. Doubling the feature addition period, moving the focus from testing and bug fixing to innovation for 1 quarter a year more, might be a way to do that.

Luis made a couple of points I agree with about an eventual leap to 3.0.

One of the major reasons for what he calls the fear to fail is the fact that the 6 monthly release cycles, which were necessary to stabilise the 2.0 work, and have been a huge boon overall for GNOME, are not suited to 3.0 work. They are just too short. For a platform as big as GNOME, to get any big user-visible features in a release cycle, it needs to be at least 9 months, and perhaps a year.

I know I’m not the first one to have said this, but I’m more & more convinced that the 6 month cycle has outlived its usefulness.

Having been shamed by Edd, I spent some time today on the GUADEC wiki, organising things into sub-pages that made sense.

As always with wikis, your help is needed to make the wiki a useful resource. We need more people offering lifts, accepting lifts, more Stuttgarters, and more information on sleeping, eating and drinking in Stuttgart.

Thanks for your support.

Wiki update

Several people recommended the C based Didiwiki (although I must admit that coding a wiki in C is not something I would have considered): http://didiwiki.org

potwiki (a VIM based wiki) also got a vote, and will be tried: http://www.vim.org/scripts/script.php?script_id=1018

Christian: The point of the whining isn’t that a change has been made. The point of the whining is that a change has been made (1) which sucks, and heavily imacts the user experience (2) two weeks before a release, and (3) in everyone’s new favourite distribution. Oh, and (4) from the looks of the bugzilla comments, as a unilateral decision by the boss.

I would have preferred if they had added a toggle in the preferences, and defaulted to the other “standard” Nautilus behaviour of the browser. In addition, that would probably be much more pleasing to the vast tracts of Windows and KDE users out there who seem to expect that and find Spatial annoying. Then I could just switch on spatial, and be done with it.

Personal wiki solution

I’m looking for a wiki-like program which has the following characteristics:

• Easy – I don’t want to spend time on the program
• Just for me – not publically available on the web
• Persistent – I’ve been using sticky notes, but they are just not persistent enough – not versioned, and they really feel like they should be thrown out regularly
• Works everywhere – Windows at work, Mac and Linux at home
• Hierarchical – I want to link from “stuff to do” to “how to do task X”

Really, a wiki is ideal, except all of the wikis I know need a web server, and what I really want is more like a cross-platform Tomboy. Does such a thing exist, and I just don’t know about it?

Update: Thanks to Emmanuel Touzery and Stewart Smith for quick answers – Emmanuel reccommended Instiki (which I believe Nat mentioned a few weeks ago too). 2 clicks, and I was away. Exactly what I was looking for. Bummer that it doesn’t use the same wiki text as moinmoin, but you can’t have everything 😉

Paul Graham on high school

What you’ll wish you’d known

Particularly amusing are the footnotes:

If a bunch of actual adults suddenly found themselves trapped in high school, the first thing they’d do is form a union and renegotiate all the rules with the administration.