Today i recieved an Tweet from Lydia Pintscher. Lydia wrote, that the KDE Project needs help.
What is to do? The goal is to find some simple data about KDE’s programs following by a template and putting them on the wiki. She tells us, that Screenshots also needed. The community wiki has more details. It doesn’t matter if you don’t know all the data for a certain program. Fill in as much as you know. If you have questions come to #kde-www on freenode or drop me an email at lydia at kde org.
Hola, amigos. It’s been a long time since I rapped at ya. The standard statement of “I know I haven’t blogged in a while, but…” really applies here. My last posting was February, 2009. That’s almost a human earth year. I mentioned my busy life on some of the KDE mailing lists (and tagged off to Troy), but to others I simply vanished. And I’m sure there was much rejoicing. What happened in Wade’s version of 2009 to keep him away from his beloved community?
Weeks after Camp KDE in Jamaica, Sebas presumably won the laptop longevity contest. He and I had purchased nearly identical Thinkpads years ago. In February 2009, a cat who shall remain nameless who belongs to a wife who shall remain nameless – said cat knocked over a glass of water on my laptop sending it to an early grave. One machine down.
Then my desktop PSU died and memory along with it. Other machine down.
As tokoe prefers screenshots in blogs, let’s start with one:
This is a screenshot of the current kdepimlibs build status on CDash. In the first column you can see the different build setups that have committed a build. There are builds from FreeBSD, SunOS, Linux, with different kind of CMake versions and differnt versions of GCC.
After that you can see the results of the different stages of the build: Update, Configure, Build and the Tests. The ‘Min’ column indicates how long that stage took. The most interesting column for me are the warnings in the build section. I’m trying to get that number down to the real warnings, removing all the non interesting warnings. On some line you can see 8 with -20 just below it. That means that in the last run the amount of warnings dropped from 28 to 20. Simalary you can see that there currently is a build error on one of the build machines…
The best new feature in the soon to be released version 0.4 of Okteta, the KDE hex editor, coming with the KDE SC 4.4, is surely the Structures tool (see also the “All new Okteta features for KDE SC 4.4 in a picture”). Because this tool is just a few months old, his author Alex concentrated on the code and not on the documentation, so the Okteta docs in the 4.4 branch have been missing any note of it. But Burkhard L
Justin and I have arrived in beautifully warm San Diego for Camp KDE 2010! The pleasant upper 60s (F) will be a warm welcome to the 30s and 40s (F) we’ve been dealing with in Washington, DC (although, it was beginning to warm up before we left today).
I was happy to see that there are other Camp KDErs staying at the Sheraton LaJolla which is walking distance to UCSD (20 minutes walking or 17 minutes by bus plus fare. I’ll be walking). The hotel is also in a good location near a mall with many restaurants which can handle typical conference crowds. However, unlike the lucky Camp KDErs staying at the Banana Bungalow hostel, we aren’t as close to the ocean.
Tomorrow is Day 1 of Camp KDE 2010, and the first day of presentations look very interesting. After Jeff and Aaron J open the conference, the first keynote will by from Philip Bourne (UCSD) about Open Access to Data in the sciences. This is particularly interesting to me because of ...read more...
After a really nice flight, my family and I touched down at San Diego’s airport, rented a car and headed down to Banana Bungalow, where I will be staying with the other participants, and the hotel across from it, where my parents will be staying.
Of course I could never find my camera. Prepare for craptastic cell phone pictures from me. The others have real cameras though, so I’ll probably manage to kidnap some real photos at some point.
Right now I’m sitting at a picnic table with a bunch of cool cats, catching up on mail. Will probably go idle on the beach later! More tomorrow!
A guy walks to the checkin desk of his airline with a lot of luggage:
Flyer: Hi there. I’d like you to send my suitcase to Beijing, my rucksack to Washington, my surfboard to Berlin, and I’m flying to San Diego. Airline: Uh, I’m sorry sir I don’t think we can do that. Flyer: Well you did it before without me even asking you to…
In fairness I had only one checked in bag on my flights, but it got lost somewhere through my cancelled and delayed connections. Hopefully it will turn up in the next day or two, or it could shaft my plans for after the event.
Right now though, they’re playing Moondance by Van Morrison in the lobby. The day is looking up. Time to debug my presentation methinks.
Upstairs are these computer screend with a camara which tracks sound. I was making the click sound with my fingers to make it focus me instead of jeff (who was talking). Weird thing. You can let it make a picture of you and put it on the web by moving your hand into a square it projects over your image... Which I promptly did, of course. Privacy be screwed!
Long time, no post… “Real life” is unfortunately keeping me busy.
Nonetheless, something I did back in November came to fruition this week. A few months ago Jos got in touch with the folks at Linux Journal to see if they might be interested in some KDE related articles for their February issue. It turned out they were and so the latest issue has plenty of KDE content with Jos’s interview with Aaron and Sebas about KDE’s future, Riccardo’s article on writing Plasma Widgets and my article on running KDE software on Windows.
Linux Journal uses a subscription model, but they make their archive available for free a month or two after publication and (if you didn’t use it already) you can get a free PDF trial copy of the current issue by filling in an online form.
Quite often -- or at least, "often enough" -- we get people that want to rescan a particular folder in Amarok. This is usually the result of them changing tags and wanting Amarok to pick it up. (Remember, for efficiency reasons Amarok watches the modified times of the collection directories, not the collection files, so adding or deleting (or renaming) files will trigger an incremental scan but modifying a file's contents won't.)
Previously, our advice was "touch the folder" or in the worst case "just do a full rescan." Now there's slightly better advice we can give. If you right-click on a folder in the collection setup dialog, and if the folder was already in your collection (i.e. you didn't just check it a moment ago), it will give you the option to rescan that folder.
I don't have a snapshot for you as the menu that pops up disappears when I click in KSnapshot (and if there's a shortcut for KSnapshot it's not obvious as Print Screen didn't work), but give it a try -- it's pretty easy. The ...read more...
Today - was up early (duh) to work on some articles for the dot and other stuff, tried to get online but that didn't work that well. Luckily they fixed the wireless later that day, it's great now. And so is the wireless at the university, btw so our basic needs are catered to (there is also power).
It turned into a busy day - been to the university to talk to some ppl and check things out, then moved on to buying snacks and other stuff at a few shops. Now we're going out to get Frank Karlitschek at the airport and find us some food ;-)
For those coming by plane - the directions on the website about the shuttles is wrong. The one they recommend doesn't exist anymore but if you walk out of the exit doors of the airfield, cross the street, there's a booth or something where they help you. You can get any of the other shuttles, ask the lady or guy there. Costs about 25 dollars...
Sometimes you stumble over an application that is really cool and makes your day. Of course when you tell your colleagues everyone knows it – except you, well…
Today I had this nice experience with a little tool called screenie. It helps to arrange screenshots or images in general nicely such as this example where I made boring Hermes screenshots look nice:
It does it with a perfect simple interface on which you drop three images out of a file manager. A handful of options allow you to adjust the image to your needs and there you are – your little screenshot composition simply looks amazing, after a few moments of work. Great software.
Btw, iit’s only around 500 lines of code and a couple of resource files. Amazing, must be based on a quite powerful toolkit utilized by a real smart guy…
If you also want to look nice, no idea how, but for screenshots and stuff quickly install screenie from the KDE::Community repository.
Apart from the customs delaying me enough to let me miss my next flight (I had almost 3 hours transfer time, damnit!), the USA's been treating me well. The usual very nice people - somebody pointing me to the right gate, lady at the gate putting me on top of the list of ppl to get spare seats in the next flight to San Diego, and then a taxi driver showing me around. I know, there are all these horrible things when it comes to the USA, from them choosing Bush up to 4 times, the (anti) terrorism stuff, the bombing of people pretty much all around the world. Environment. Politics. Yeah yeah. But they're nice people! Really, in person, I like 'em. At least in California I do...
Beach at night
So after traveling and working in the plane on some feature guide stuff I arrived at Banana Bungalows in San Diego. Well heck. The organizing team did it again - like in Jamaica, this place is ...read more...
One of the things I did not like about that particular visualization is that it said nothing about the artifacts in the repository. Instead, it focused squarely on the contributors. What if, for example, an individual was not just responsible for a disproportionately large number of commits, but also for a disproportionately large number of artifacts, too?
So the revised visualization goes a little like this:
Sqaure nodes are contributors;
Round nodes are aretifacts;
Square nodes are only connected to one or many round nodes;
Edge weights are the number of times the contributor has committed to that artifact.
Again, the graph is laid using Kamada-Kawai in order to get a feel for the “shape” of the community. I have also followed the same colouring scheme so that it is easy to spot the contributors with a high number of commits. I ...read more...
Technically it’s Day 0, but I’m about to go to bed, so I’m going to call it day -1
Tomorrow (Friday, two sleep cycles from now) I’m hopping on a plane to San Diego to attend Camp KDE, North America’s largest KDE event for the foreseeable future. I’ll be learning a lot about KDE while also getting the chance to tear open KPilot’s source code (hi Jeff!) and in general just hanging out and getting to know the KDE community a lot better. I’ll be the guy who’ll be sporting the big old box of Fedora swag that my regional ambassador, the awesomeness that is Clint Savage, will be mailing to Banana Bungalow. So, any Fedorans in the area of University of California San Diego, KDE users or not, I encourage you to visit the event, get to meet some awesome people and get to meet some awesome software. And you KDE folks, better be there :^)
Nepomuk, the "social-semantic desktop" framework named with a cute half-dragon namesake. It's an amazing set of technologies, but there are two huge challenges for it in 2010. If we conquer those challenges together, we will be laughing.
Communicating Nepomuk's Benefits
Right now there are a lot of questions surrounding Nepomuk: What is it good for? Why does it take so much CPU / disk? Why do I need it if I don't plan on doing any socializing or semanticizing (?!) on my computer? This translates to a lack of enthusiasm, appreciation and even frustration amongst our users and even at times developers.
The thing is: all of those questions have good answers. Whether it's the performance improvements of Virtuoso, educating our users about how Nepomuk is being used by various "every day tasks" (such as indexing and relating email, contacts and other PIM data via Akonadi, all behind the scenes and with good perormance) or making it easier to figure out that it's quite easy to turn off the disk indexing parts if you want, these ...read more...
As most of KDE is C++, and the Python API docs are translated directly from the C++ API docs, it is essential to have good examples to help newcomers learn faster. There are some PyKDE4 examples in the kdebindings module already, but I put mine in kdeexamples for a number of reasons:
Clear purpose: kdeexamples is meant exactly for this – example code;
Visibility: A central place to find KDE examples even for bindings is optimal, makes easier to find what one is looking for.
Visibility is also important as currently the examples are rather buried inside kdebindings, and as far as I know they aren’t included in the packages of some distributions (at least not openSUSE; YMMV).
I’m pleased to announced a new BIG release of Shapado (the free/libre open source stackoverflow stackexchange on steroids). We’ve added tons of new features and hopefully didn’t add too much bugs.
The new features are:
reputation constrains: you will need a certain amount of reputation points in order do some actions such as voting up or down and more.
badges: people who participate a lot or are just getting started will get rewarded with these :)
new ui: shapado should look better now
theming: if you still don’t like how it looks, you can now make your group look however you want, the default install comes with 5 default them but you’re free to create your own ones. Themes are based on web apps .
There’s some movement on the KDE/Maemo front. Lately we’ve seen more public announcements coming mainly thanks to the office viewer. But there’s also work under the hood cooking up. Most notably communication channels to provide feedback for the Qt 4.6/Maemo variant are open, hopefully we’ll soon see a few patches flying in. And also Jos posted some (large) patches to streamline kdelibs which are on the table for discussion and hopefully going toward a KDE wide solution.
Today though, I just wanted to let everybody know that I’ve been working on a virtual machine to help KDE developers easily get a Maemo SDK. I added some documentation so now we have a Qt/Maemo SDK VM page on techbase (download URL and installation procedure are there).
It should be relatively easy for anyone to have it working: download, boot, login, run a script, done you can know use Qt 4.6 in a fully setup Maemo SDK. Hopefully that will lower the bar to contributing for quite some people.
Once i have read comics, many comics. Especially those of some superheroes. What i can remember quite well is one comic about superman. It was about a problem with our parallel world. Suddenly there were 2 earths. And Superman's problem was now to put those 2 worlds together again. To keep it short, he was actually able to handle it. Why do i want to tell this? What we actually have are 2 different worlds.
The first one is that of a user willing to contribute but not knowing how and where. Maybe it also involves being a bit shy, maybe just not finding the right information or the right place.
The second world is the developers world. They work hard on their product and have a hard time to do it all, always waiting for a new volunteer.
Now, how could these two worlds be approached? Afterall, we want our small family called KDE grow, right? ;) That's where "Get Involved" comes into the game.
I took over a package that had been disowned and modified it to make it build on Arch with libofx. Aqbanking is still pending because I haven't found a suitable Qt4 package, but I will modify it when I do.
There were 12 participants registered (9 of them worked on the bug reports)
The overall results are: 141 bug reports checked (~14 of 20 batches) 42 bug reports which could be considered fixed/not-reproduceable (this is an estimation, some reports are not going to be closed)
(note that the results could change as it is somewhat difficult to “label” some bug reports’ status)
I think these are nice results considering the season (new year’s eve week), and that this was the first (and unpolished) experience. From my PoV, the whole experience was great: people was interested and willing to help us, and the BugSquad stuff was willing to help the participants too.
I would like to thank to all the participants: jtamate, R
Here's a little story I wanted to share with you. It's so bizarre, you might not believe it when you read it, but it really happened
Some back story:
A few months ago Amarok had migrated to Git, and then Konversation had migrated too. We had to write a special "commit hook" script for making the commits show up on IRC, via the CIA bot. This script was running on our Amarok server (called "Kollide"), and all was fine. At some point then we migrated our server to new hardware, as the old contract had expired. That also went really well.
What happened later:
At some point the CIA bot started to print everything twice. Yes, every single commit, all duplicated. I guess you can imagine how annoying that was. So we tried to debug this for weeks, looked at all scripts, at Gitorious, and whatnot. Noone was able to spot ...read more...
I thought it might be nice after the holidays to tell about the status of the Kraft project, the KDE software for people operating a small business. Some nice things happened around it.
The best thing is that an additional developer works on Kraft: After my last status post Thomas Richard (account trichard) contacted me that he is interested, next days I had the first patch in my mailbox and from that point of time on he constantly contributed high quality changes into the Kraft repository.
His high energy, dedication and fresh ideas gave me a new motivation push after having worked on Kraft basically alone for more than four years. That’s great!
The last months we worked on porting Kraft to the KDE4 platform which is in a quite good shape in SVN already: Kraft compiles without warnings and without Q3 and K3 support classes and works stable again.
We couldn’t resist to make use of the new capabilities of KDE4 here and ...read more...