FOSSwire

In case you haven't heard, the new version of Ubuntu, 7.04 Feisty Fawn is out. One of the new features Jacob told us about in his introduction was a new codec download feature. He explains it well, so I'll reiterate that here:

Another addition, and the best in my opinion, is the option to automatically install the required codecs for a video file when you try to play it. You simply click to open the file, and if you do not have the codecs installed, Totem (the movie player) will ask you if you would like them to be installed for you. Click Yes, check a box, and click Install. You now have all of the codecs you need to play movies, including WMV9 (GStreamer only) without the need of the w32codecs package.

Curious as to how this works, I fired up my Ubuntu Feisty virtual machine and headed over to a site with a QuickTime video on it. Here are my experiences of this new feature.

It wouldn't play in the browser, but I could easily extract the URL of the .mov file and paste it into the Totem movie player.

On realising the format, Totem displayed this dialogue box:

I chose Yes and up popped a standard software installation window offering to install one package which would, in theory, allow me to play this QuickTime movie.

On ticking the package to choose to install, I was then presented with this warning:

Obviously, this warning has to be there due to the occasionally dubious legality of using proprietary and patented codecs within Linux. After agreeing to that, the codecs downloaded just like a normal software installation.

Once that had finished, I tried again to play the video, but got the original dialogue box again. I though for a moment that I was out of luck, but decided to try it once more anyway. This time, it found several additional packages, all of which also carried the stern patent warning.

After installing all of the packages, to my surprise, the QuickTime movie actually played.

The experience was far from perfect due to some buffering issues, in fact I couldn't actually get it to play with a reasonable frame rate. I'm not sure whether that was because of the fact I was running it inside a relatively slow virtual machine or whether it was a codec issue. I also should point out that this VM didn't have sound, so I have no idea whether or not the sound actually worked.

Still, the point is, it was reasonably easy (with a few minor caveats) to play QuickTime under Feisty. I assume this also works for other popular proprietary formats. So what does this mean and what repurcussions are there?

Well, the problem boils down to pragmatism versus idealism. Some members of the FOSS community are the former, and think that sometimes in order to promote free software, we have to sometimes also make use of proprietary technology, while others are very strongly against including non-free components in free operating systems.

This means that the issue of proprietary bits in Linux distros is always a sensitive issue. To add to that, as Ubuntu helpfully pointed out while installing the codecs, there are also legal issues surrounding using proprietary and patented formats.

Unfortunately, most users don't care. They want their stuff to work.

Feisty clearly edges on the pragmatism side of the argument by making it reasonably easy to download the proprietary stuff should you so wish, but without compromising too much on the freedom aspect, because they're not there by default. In my opinion, it's a good call by Shuttleworth and the team and I think it could well help further mainstream adoption.

Interestingly, I reported a while back that for the next release of Ubuntu, there will be a new, completely free software variant (Ubuntu at the moment still includes some 'restricted' drivers for the purpose of out-of-the-box hardware support):

Also announced in that post is the fact that there will be a new variant of Ubuntu which will be composed of completely free software (with no proprietary drivers at all). Apparently, this effort is being assisted by some of the guys behind gNewSense.

Hopefully, by the next version, we'll see things getting even easier for the end user and also a completely free distro for those who so wish.

Slashdot is reporting that popular free software accounting package SQL-Ledger recently secretly changed their licence from the GPL to the SQL-Ledger Open Source Licence. The project leader did this without notifying anyone on the project.

Users of the popular accounting package SQL-Ledger were being kept in the dark about a recent license change. Two weeks ago a new version of the software was released but along with it came the silent change of license from GPLv2 to the 'SQL-Ledger Open Source License' — presumably in an effort to prevent future forks like LedgerSMB. As it turns out, the author was making deliberate attempts to prevent the community from finding out about the license change. No posts to the SQL-Ledger mailing lists asking about the license change were getting past moderation and direct questions to the author were going unanswered. Just recently the license was switched back to GPLv2. This behavior is not a first for this particular project, and is part of the reason for the original LedgerSMB fork. Does a project maintainer have an ethical obligation to notify his or her community of a license change? What about a legal obligation?

It is being presumed that the reason for the licence change was to try to avoid forks of the code (for the uninitiated - a fork is where a project's code is taken by one set of developers and they split up from the main branch and do their own thing with the code). The licence has now been changed back to the GPL, but it raises questions about whether this is an ethical, or even a legal move.

Regarding the previous post on the possibility of a Compiz and Beryl merge: it is happening.

http://forum.go-compiz.org/viewtopic.php?t=761

After several weeks of discussion the leaders of Compiz and Beryl have agreed that the two communities shall reunite. This decision is supported by both David and Quinn and represents the majority decision of the administrators and developers in each community.

There will be two main sections: compiz-core and compiz-extra. The Core section will be the basic Compiz package and plugins. It will be considered most stable out of the two. The Extra section will be where you can have all of the fun with your effects. Many Beryl plugins will be in this section, and it will essentially be Beryl. It will be named Compiz Community for the time being.

For now, the websites will remain separate until the two projects are completely merged.

Keep your feed readers tuned to FOSSwire for more updates on the merge!