my blog


Entries feed

Wednesday 6 April 2011

Enjoy GNOME 3 today!


GNOME 3 banner by Jakub Steiner & Lapo Calamandrei

After nine years in the world of GNOME 2, our community is now moving one step further with the availability of the first GNOME 3 release. We're writing an important new line in the history of our project.

It's hard to ignore the feelings this event creates.

I remember the long discussion Lucas and I had about the future of GNOME, in front of his hotel at FOSDEM 2008.
I remember how, at GUADEC 2008 in Istanbul, the release team discussed the idea of finally doing GNOME 3.
I remember the Boston hackfest in October 2008, and all the ideas that were generated there.
I remember writing the first draft of our plan for GNOME 3.0, late at night at the end of March 2009, while being hosted by Christophe.
I remember meeting with as many teams as possible for two days at GUADEC 2010 in the Hague, to decide if we should delay the release.
And I obviously remember the Bangalore Hackfest we did last week to work on the final details on the release.

I love our project and what we achieved. You will love it too!

Getting ready to celebrate GNOME 3? Maybe in Lyon?

Today, we'll release GNOME 3 to the world.

We still need to finalize a few things here and there, but the release is mostly ready. While every .0 release generates some stress (especially when it's one starting a new major cycle), there has been much confidence about how smooth this would all go. This is mostly thanks to the Bangalore Hackfest, where we were able to prepare for this big step.

I actually came back from India on Monday around noon and I immediately started working on the release. We nearly got all tarballs in time (thanks!), and even though we had to re-roll a few tarballs to fix some extremely visible issues, everything went fine so far. I was able to quickly publish the 3.0.0 modulesets so that anybody could help with smoketesting and I built everything, at least twice. The few visible issues I've seen in my tests are either already fixed in re-rolled tarballs or in git, or with a patch in bugzilla. Since those issues are not necessarily considered as blockers (it depends on how severe they are), some of them might stay for 3.0.0; but they'll certainly be fixed for 3.0.1, due in one month. So all in all, things are good there. There is still some coordination to be done for the website update, though.

The bad news is that my body apparently doesn't want to keep working like this for long: what was supposed to be a short break at 6PM yesterday ended up being the end of the day, as I fell asleep for the whole night. I guess considerably eating on my sleep time in the last two weeks and falling sick during the last days in India didn't help :-)

It's slowly getting hard to keep focusing on just the release in this last day, since I already find myself thinking about all the release celebration! There's much excitement all around, and all the launch parties around the world make me think we'll all have fun for the celebration. I'll go to the Lyon party tomorrow (Thursday), and I certainly hope to meet many people there. So don't hesitate to pass by if you're near Lyon tomorrow!

Now, going back to release mode :-)

Friday 1 April 2011

Delaying GNOME 3.0, again

Update: in case people had any doubt, this was an April 1st joke :-)

The Bangalore Hackfest was really useful for the release team to evaluate the status of GNOME 3. We really want GNOME 3 to be amazing, and various recent events lead us to wonder if doing the release next week is a good thing; we had a lot of discussion and meetings, and we even had a call with the Board to evaluate different options.

It was not an easy decision, but after announcing that GNOME 3 would occur in September 2010 instead of March 2010 as originally planned, and then pushing it back to March 2011, we have to announce another delay: GNOME 3.0 is now scheduled for September 2011.

The announcement linked above explains the various reasons for this decision, which was really hard to take. You can also go read the next mail I sent afterwards to the same mailing list for more information. I really want to thank all the community for their hard work, and everybody should just keep rocking. Because what we achieved so far is still pretty impressive.

Of course, this changes a bit the topic for the talks we're going to deliver to the GNOME.Asia conference, especially my keynote scheduled tomorrow on April 2nd...

Wednesday 9 March 2011

WebKit-powered gnome-web-photo

A few weeks ago, I was looking at what was still using an old version of XULRunner in openSUSE, and one of the few applications that was left with no port to XULRunner 2 (the one that will be out with Firefox 4) was gnome-web-photo. In case you don't know gnome-web-photo, it's a small utility originally written by Christian Persch, to capture screenshots of a web page, which can also be used to generate a thumbnail for web pages. It's actually the main reason why we care about it in openSUSE: having a thumbnailer for HTML files is a nice little touch.

So I look at porting gnome-web-photo to XULRunner 2, and... I felt some pain. I asked Christian about his plans and if he thought porting this utility to WebKit could be a good idea. As Christian was not working on it actively, he was open to the idea. After a few hours of coding (WebKitGTK+ is really cool, with its easy-to-use API), a rewrite was ready.

I did some more cleanup and added the option to print directly a web page to a printer, and then released gnome-web-photo 0.10. The only real regression, as far as I know, is that it won't handle correctly very tall web pages (like this one): it will simply cut the web page, because we're hitting some limits in some libraries below us. This is probably fixable by scrolling the page and writing the resulting image ourselves, but I really wanted to get the rewrite out and I'm not even sure people would notice this regression ;-)


Monday 28 February 2011

Canonical, you're breaking my heart

Quoting code from Banshee:

    // We ask that no one change these affiliate codes. ALL (100%) revenue
    // generated by these affiliate IDs is sent directly to the GNOME
    // Foundation. The GNOME Foundation controls/owns these affiliate IDs.
    // Please help support Free Software through the GNOME Foundation!

I've been resisting blogging or talking about this topic publicly, but I'm so frustrated with how Canonical dealt with the whole topic that I can't resist more... If you don't want to read my stuff, I encourage you to go read Zonker's articles about the story.

Very short summary for those who didn't follow:

  • the Ubuntu community decided to switch to Banshee as default music player.
  • Canonical offers the Ubuntu One Music Store in the default Ubuntu music player to let people buy music online. Referral fees go to Canonical (as far as I know).
  • Banshee comes with an Amazon MP3 Store plugin to let people buy music online. Referral fees go to the GNOME Foundation.
  • with the switch to Banshee by default in Ubuntu, Canonical proposed two options to the Banshee developers: disable the Amazon MP3 Store plugin by default, or changing the affiliate code for the Amazon MP3 Store and giving 25% of the referral fees to the GNOME Foundation (the other 75% would be going to Canonical). Banshee developers chose to keep the money going to the GNOME Foundation, and to have the plugin disabled by default.
  • a few days later, Canonical changed their mind and decided that the Amazon MP3 Store would stay enabled, and that 25% of all referral fees (Amazon MP3 Store and Ubuntu One Music Store) would go to the GNOME Foundation.

There are a few things that are wrong with this story, and I've read a few things that made me wonder if some of the people standing for Canonical's decision in the comments I've read have a good understanding of everything (and maybe they do; everybody is entitled to his own opinions after all). It's worth pointing out first that I'm annoyed at Canonical, and not at Ubuntu, and my first two items below explain this:

Money does not go to Ubuntu. It goes to Canonical. I'll start with that, because I feel this was neglected by most. I would be much less annoyed if the money went to Ubuntu instead of Canonical. This way I would know that the money would be used for Free Software; I would still not be completely happy (see other points below), but that would make me feel better. But it turns out there is no active Ubuntu Foundation (the Ubuntu Foundation does exist, but is nowhere near active or alive), which means there is no real way for Ubuntu, as a project, to collect money. The result is that we have no idea how the money will be used, in concrete terms; and this raises accounting questions.

This is not an Ubuntu decision, this is a decision from Canonical. As far as I can tell, this decision was not discussed in any way inside the Ubuntu community, and I have serious concerns that such a decision that does affect Ubuntu is not taken by the Ubuntu community. I've added an agenda item to the next Community Council meeting (tomorrow, March 1st, at 21:00 UTC, in #ubuntu-meeting). To be blunt, though, I have absolutely no hope of open discussion there: I've yet to heard of anything that is agreed by the Community Council that goes against the interests of Canonical. I believe that is a serious flaw in the Ubuntu governance, and it's certainly not the first time this is highlighted.

It is legal, but it is not necessarily right. Of course it is legal because of Banshee's license. Nobody is arguing about that. However, the will of the Banshee developers is to donate money to the GNOME Foundation. They've expressed this will twice: when they first chose to donate the money to the GNOME Foundation, and when they chose one of the two options proposed by Canonical. So Canonical's decision is explicitly going against the will of the developers. It is legal, but going against the will of the developers is definitely wrong.

Releasing Banshee as free software doesn't mean Banshee developers don't care about how their software is changed or used. I've read several times that Banshee developers could simply have chosen another license to avoid this issue. That's an extremely dangerous slope: many free software developers choose a free software license because they believe in freedom and they believe that releasing their software under these terms will help improve the world in some way. That's our contribution to making the world a better place. We also believe that, usually, people will understand what we want to achieve and will respect that. Canonical's decision, and how it was taken, doesn't show any such respect. Should we stop contributing to making the world a better place because a company is doing things wrong? I don't think so. We should try to make that company a better citizen, and keep making the world a better place. Suggesting that we can simply choose a non-free license is suggesting that we stop trying to achieve our dreams. Sure, we could do that, but that's certainly not the right solution.

A 75%/25% deal does not reflect what Canonical brings to Banshee. I've read this several times: people think it's actually a fair deal because Ubuntu does most of the job, by integrating Banshee in Ubuntu and by exposing it to many more users. I'm disturbed when I read this. The fact is that Ubuntu chose to adopt Banshee by default because it was the best solution. If it was the best solution already, then somehow, the Banshee developers did a hell of a great job and Banshee actually improves Ubuntu. And that part is certainly more than 25% of the whole job, isn't it? I mean, if that's not the case, then certainly Ubuntu would be shipping with something better already. Also, this way of thinking gets me wondering: do people seriously suggest that Ubuntu would exist and be successful without great upstream developers? The work done to build Ubuntu is integration. It is not easy, there's no need to argue about that and I know this because I work on a distribution. So I know it's far from trivial. But compared to actually writing the applications upstream... Most of the hard work lives upstream, and integration, while key, is only a small percentage of the work. Even the argument that Ubuntu will bring more users falls apart for me because Ubuntu brings more users to applications, but only because those applications themselves are great. Ubuntu can only bring something to the applications because the applications bring something to Ubuntu.

No, a 75%/25% deal is not necessarily a better deal for the GNOME Foundation, money-wise. Several people mentioned that 25% of referrals fees of the plugin enabled by default is higher than 100% of referrals fees of the plugin disabled by default. How can we know? We can't. We simply don't know. I've heard that the Ubuntu One Music Store is... suboptimal, so I think it's also a fair position to assume that many people would have found on the web that there's a great Amazon MP3 Store plugin, and would have switched to it. It could therefore turn out that in the end, maybe, even if the plugin would have been disabled by default, it would have brought more money to the GNOME Foundation. Who's right? Let's be honest and agree that we don't know.

No, even if it's a better deal money-wise, a 75%/25% deal is not necessarily a better deal for the GNOME Foundation. You know what? Please don't put words in the mouth of the GNOME Foundation, and leave the GNOME Foundation decide for itself. The GNOME Foundation is a non-profit organization and while the GNOME Foundation could use more money, it's certainly not the goal of the Foundation. As a past Foundation Board member, my informed guess is that most members of the GNOME Foundation would agree that respecting the will of authors is more important than money. If the GNOME Foundation decided to take a public position about what is best for itself, it could well be something as simple as this deal is not in our best interests. I'm of course not saying this is the position of the GNOME Foundation since that's not my job, but I hope this helps people understand that more money doesn't make the deal a better one for the Foundation.

There is now no way to make the money go to the GNOME Foundation. With the current decision, there is no way for the user to choose to leave the money to the GNOME Foundation. I've seen at least a comment from Jono suggesting that Banshee could distribute a new plugin for that. I can certainly understand that Canonical doesn't want to do that itself, but Ubuntu people could. Is there any reason that Ubuntu can't ship this small plugin (17 KB) itself, on the CD, or even in a package in the Ubuntu repositories? If people would do the job, would the package get accepted on the CD? I don't want to guess, so I'll leave the question open.

The whole decision process is just alarmly broken. Canonical came with two options, and one was chosen by Banshee developers. There was some reaction in blog posts, news articles and comments about the two options, that were already negative about the proposed choice. And then Canonical came back with what I understand is a unilateral decision, that does not respect the previous explicit choice of Banshee developers. Sure, there's now 25% of the referrals fees from the Ubuntu One Music Store, but did some people really think that would make Banshee developers change their mind? How can this sound right?

I'm sure I could go on and on, if I'd take more time, but I'm not sure it's worth it. If the deal was something like 25%/75% or even 50/%50, I think I'd feel a bit better but I'd still want the money to go to Ubuntu instead of Canonical, especially as Canonical did absolutely nothing to develop this Amazon MP3 Store plugin. I'd be surprised if the Ubuntu community would have no use for money that it could decide how to spend.

The bottom line is that I'm highly annoyed. It's just yet another illustration that, even though some parts of Canonical care (or try to care) about upstream, in the end, what matters to Canonical is money. I'm even more annoyed because I have many good friends at Canonical, and that makes me not want to dislike their company.

Canonical, you're breaking my heart: I thought you understood the spirit of Free Software, but you're just another normal company that is first going after money.

- page 4 of 36 -

by Vincent