LinkedIn has become one of the more popular professional networking sites out there in recent years. It’s a great way for co-workers to stay connected with each other after they part ways and also a nice platform for marketing your resume to what could be your future co-workers.
In addition to that, there is a nice section on the site for groups where you can post questions and discussion topics. With that in mind I wanted to point out that on LinkedIn there are several KDE-related groups. In particular, I’d like to invite all of you who are on LinkedIn to join the“KDE User” LinkedIn group and participate in the discussions there.
So far there are over 500 members but despite this there is not a whole lot of active discussion. I’m not sure if everyone is shy or busy or what but generating some lively discussions about KDE in front of a large group of interested onlookers could only be a good thing for promoting KDE. LinkedIn seems to have a very strong presence ...read more...
Interested in trying out KDE SC 4.4 but don’t want to do a full installation, risking system instability? Before my presentation at Wednesday’s Phoenix Linux User Group meeting, it occured to me that I should bring a live image for folks to play with. Unfortunately, I spun x86_64 live images, which are great for x86_64 folks, but pretty lametastic for everyone else. So, our awesome KDE SIG and kde-redhat maintainer Rex Dieter, fixed that, and, after fixing my kickstart a few times of course. Now we have unofficial i686 KDE 4.4 previews. They lack the Fedora branding for legal reasons, but for all intents and purposes, it’s the same system as you’d get by installing Fedora 12 and then configuring KDE-redhat repos.
So, have at it. Rex has three servers seeding, and I’ll seed when I can The image is 70Mb total (sorry) so it doesn’t fit on a CD, but is just about the perfect size for ...read more...
It’s been a long time since the last update, and admittedly I haven’t been working on PlasMate as much as I’d like to in the past month (with school kicking in and all). Anyway, just a quick post to highlight some of the stuff we’ve been up to.
The screenshot at the top shows the beginnings of PlasMate’s project management dialog. Right now it does nothing but lets you load a project. The idea behind this though is that we want to keep project management inside of PlasMate, so that you’ll never need to find or create a location to store or “save” your projects to. PlasMate would spare you that management overhead by taking care of storage somewhere out of sight, and allowing you to view, search, load, and delete your projects from within the project management dialog. As shown in the screenshot, you would still be able to view and load your 5 most recent projects from the start page itself. And you could still export your ...read more...
As a heads up to everyone out there: we're getting a lot of bug reports, particularly crashes, from people using Qt 4.6.0. That version of Qt has a handful of crashes in it that some KDE apps trigger all too reliably. A patch release of Qt, v4.6.1, has been released that addresses a number of these issues. Qt 4.6.2 that's upcoming will be even better, and I understand that some distributions have been backporting some of these critical fixes. If you are having a hard time with the 4.4 release candidates, please check your Qt version first.
Then there's this bug in glibc, which has been fixed, and some distributions have backported those fixes to affected versions already. Unfortunately, some of our users are still getting exposed to it. Not fun.
Just one of those months, it seems.
The 4.4 release for KDE SC is coming along well. We've been hammering nasties, of both the crasher and general misbehavior sort, over the head at a reasonable pace, even though 4.5 is open and some ...read more...
As I prommised on an obscure mailinglist where the evil plans for KDE World Domination are being developed (and consequently rejected), I'd like to solicit some opinions in this blog about Freedom.
I'm not talking about the free-as-in-beer nor the free-as-in-speech, but the relative independence the KDE community enjoys from the influence of one or a few large corporations. Most of you probably realize that it's a rare property for a community of our size - pretty much all other communities with over a 100 developers (KDE has about 2400 active developers!) are basically run by anything from one up to 3-4 large companies with little or no volunteer input. At a recent meeting Frank, Jeff and myself had with a major manufacturer of mobile chipsets it became abundantly clear that the independence the KDE community enjoys is seen as a big plus by companies who might want to work with us.
Of course, talking with volunteers you are not seldomly reminded how they prefer their freedom. While support from a big company is nice, for many the ...read more...
"Looking to help the KDE community and living in Southern California? Then this is a great opportunity for you! The Southern California Linux Expo will be in town February 20-21, 2010, at the Westin Hotel near LAX.
The more I see things like iPad, iPhone, iTunes, etc. coming, the more I am motivated to continue using, developing and promoting Free Software. This world needs people who care about freedom in general and digital freedom in particular. And we are those people.
"The KDE team is getting very close to a final release of KDE 4.4. The second release candidate came out yesterday as a testing platform for users and developers to find and squash bugs before the final release date of February 9th.
Last year a lot of people were attending FOSDEM. This year, 10th anniversary and everything, it seems that very few people are visiting Brussels on Febrary 6th and 7th and attending the largest Open Source conference in Europe.
Anyways, I am attending
NB: Comments on this blog do not work due to a hosting issue
To date, all of my work has looked at SVN artifacts and the contributors who interact with them: add, delete, modify, move etc. On a couple of occasions I have been asked why I do not look into the artifacts. I never really had a good answer and so now I have got around to it.
The question, I guess, is why would anyone want to look into the artifacts when looking into the health of a community? My previous work has shown how certain contributors can be shown to be responsible for lots of artifacts and lots of commits. But what are they doing to those artifacts with those commits? For all we know (based on the work so far) they are making trivial changes to the same line of code over and over.
As a start I have made use of svn blame to gather data one who “owns” each line of code in KMail. The script I used to achieve this looks like this:
Hi guys, I was preparing this summary of blogs and other coverage of Camp KDE to forward to our sponsors to show the activity occurring at the event. I figured I'd share it with the planet, if you folks are interested. If blogging is a measure of productivity, we certainly set the bar high. :) Dot.kde.org Posts (during and around the event only):
So if you’ve used kdesvn-build to build some of the modules that are hosted on Gitorious then you are probably familiar with an error that always comes up when doing the initial checkout. This error is so famous that every “how to build using kdesvn-build” guide I’ve seen over the past couple of months have mentioned that the clone step for qt-copy would need to be done manually.
A Konversation developer, argonel, noticed the issue the other day and got in touch with me, so I had him strace the output of the (successful) manual run and the (unsuccessful) kdesvn-build run. It wasn’t initially super helpful although it clarified what was going on (the gitorious.org end of the connect was closed on their end for some reason).
That was the conclusion of that, but then I get an email the next day from argonel saying that he’d done more digging, and that it was a known issue which could be worked around by adding the -v flag to git, which forces progress output to ...read more...
This country continues to surprise me. Take the concept of lite beer, bringing the taste of this beverage to a new low. Or the fastfoodizing of practically every kind of food you can imagine. And at the same time - fruit and vegetable snack trays in the supermarkets which must be scary healthy to some. Amazing.
Van Camp KDE 2010 - Banana Bungalows, THE place to be in San Diego :D
Then the breakfast - I've had sandwiches with peanut butter and jelly every day, certainly something crazy I'm gonna keep around. However, I won't ever even contemplate having a breakfast at a restaurant around here. I tried an American breakfast 2 years ago in San Fran, and since then I know it's not for me. Way overkill, I'd consider the average breakfast here a heavy dinner... I've even skipped several dinners as the 'lunch' I had was just too much.
2009 is over. Yeah, sure, trueg, we know that, it has been over for a while now! Ok, ok, I am a bit late, but still I would like to get this one out – if only for my archive. So here goes.
Let’s start with the major topic of 2009 (and also the beginning of 2010): The new Nepomuk database backend: Virtuoso. Everybody who used Nepomuk had the same problems: you either used the sesame2 backend which depends on Java and steals all of your memory or you were stuck with Redland which had the worst performance and missed some SPARQL features making important parts of Nepomuk like queries unusable. So more than a year ago I had the idea to use the one GPL’ed database server out there that supported RDF in a professional manner: OpenLink’s Virtuoso. It has all the features we need, has a very good performance, and scales up to dimensions we will probably never reach on ...read more...
The Theodor Heuss Foundation (German site, but the Wikipedia article is probably more informative), named after Germany’s first post-war president, is a foundation established to remember the political achievements of Theodor Heuss as an example for social commitment, moral courage and the dedication to fostering democracy. The foundation seeks “to bring attention to something, which has to be done and shaped in our democracy, without being finished” (Carl Friedrich v. Weizs
WARNING: This is a unstable release, it is actually 0.14 Alpha release, it should work like any release from the 0.12 branch, but do not blame us if it turns your printer into a broom.
Changes against the 0.12 branch: core: * Improvements to Annotation rendering. Bug #23108 * Do not give an error when opening files without pages. Bug #24720 * Try to read streams without Length * Do not crop the transformation matrix at an arbitrary value. Bug #25763 * Make poppler (optionally) relocatable on Windows * Use a small object cache in GfxResources to cache GState objects * Reduce the number of redundant pattern creations in the Cairo outputdev * Use colToDbl() to avoid rounding error in the Cairo output device * Fix problems with mask handling in the Cairo output device. Bug #8474 * Use a better scale down implementation in the Cairo output device * Various optimizations to the Splash output device * Add ...read more...
This scattered series of posts has been about the RDF support I'm working on for KOffice. The ODF document format lets you store RDF/XML data inside the document file, which in turn lets both a human reader and a computer know about things that comprise an office document. You can refer to a person, place, or time and have the computer know what you are saying without having to resort to heuristics.
Having RDF support in document formats means you can send somebody a single file containing exact information about real world events. The RDF can contain details which can be pulled up in the formatting of the text that you see. For example, for a given contact you might know his phone number, home page, normal business location, email address etc. You might only want to see a small fraction of this information at one place in a document, but perhaps for a header you want to know the postal address too. Stylesheets are what I'm working on right now to let that happen.
"Carla Schroder wrote an editorial piece this week on Linux Today entitled Editor's Note: What is User-friendly, Really?. "In it, Carla claims to be "90% satisfied" with KDE3 and "60% satisfied" with KDE SC 4.3. Why? "KDE 4 sacrifices customizability and efficiency for glitz.
Now everyone is gone, I'm the lone wolf here in San Diego. Still working on a couple of loose ends, including the final article (which is next on my todo, after I've done this blog and done some stuff for Qualcomm as we promised during our meeting).
I knew the esp the first to articles were long and booooring - al talks, little fun. This time I'll do better, I promise.
You can expect an epic tale of hackers risking their lifes to get to the university while the streets were flooded, only to arrive in a place threatened by two dragons and a few too-cute babies. And more flooding. If it wasn't for the good care of Jeff we'd have been without beer, snacks and wifi...
So expect an article tomorrow around this time on the dot.
Of course, Solaris has been a primary target for OpenOffice for ages, so KOffice is a little late to the game on this particular platform. But I guess that’s my fault, since I’m one of the packagers for KDE4 on Solaris, and I hadn’t gotten around to it yet. So this weekend I spent a little under two hours hammering together a specfile (RPM-style) for koffice and getting the whole darn thing to build. Screenshot of KWord in action as proof. I tried KPresenter as well, but that crashed on changing the list style, so I didn’t think that was a ...read more...
I haven’t written a proper tech article since before I (re-)started this blog, so I thought it was high time. Besides, I’ve been wanting to write this post ever since I read some articles on Google’s Chrome OS, around the time right after my old blog vaporized. So there’s a couple of buzzwords to hopefully sucker you into clicking the ‘more’ button and actually reading the article – It’s about Google’s upcoming Chrome OS and it’s implications for the web, the desktop and the browser, as well as why desktop evolution can take an alternative path, exemplified by KDE’s budding Project Silk movement.
I’d really like to link to some of the posts I read on Chrome OS as they were really interesting, but I read them around half a year ago and I sadly couldn’t find them anymore. Anyway I’m going to start by doing a brief exploration of what Google likely wants to achieve with Chrome OS. Most of you probably already have an idea of what Chrome OS will be like:
So if you worked with some version control systems for a bit, you’ve probably heard of a concept called branches. It is quite a simple concept: you can perform several development processes in parallel without them interfering with each other. Most projects use branches for experimental features that could set hell loose and for backporting bugfixes to older releases. Subversion and CVS people usually dislike branches, because they involve lots of uninteresting and painful work that they don’t want to do. That is easily explained by the way branches are implemented there.
As you might know, branches in SVN are implemented in a very interesting fashion. They are not, in fact, implemented at all. SVN branch is just a folder, which is created when a branch is started. If you want to merge it back, you need to remember the revision number, when you created the branch, and use that magical number in a complex “svn merge” command. But still, SVN project history remains a straight line.