We’ll probably do another RC release to test some of the code that is not yet in this version, like supporting the restoration of manually added resolutions (something only needed for broken monitors).

Tarballs:
http://download.kde.org/unstable/libkscreen/0.0.81/src/libkscreen-0.0.81.tar.bz2.mirrorlist
http://download.kde.org/unstable/kscreen/0.0.81/src/kscreen-0.0.81.tar.bz2.mirrorlist

Cheers !

Explanation:
Since BlueDevil was released we have been updating all stable versions, which means:

• 1.0 (currently at 1.0.5)
• 1.1 (currently at 1.1.5)
• 1.2 (currently at 1.2.4)
• 1.3 (about to release 1.3.1)

This has been possible because the code base did not change much between releases so we fixed the bugs in the oldest version and then forwarded the fix to all the other releases, this was the easy part.

Before each release we like to do some intense testing to make sure that none of the basic functionality has been broken. In the hardware world quality is extremely important, we do not want to leave the user without a mouse, connectivity or an usable screen just because we are lazy or we don’t feel like doing QA.

In the case of BlueDevil we test most of this before each release (independently of what code has been modified): http://community.kde.org/Solid/Projects/BlueDevil/Tests

This means that even if the “Send File” functionality was NOT modified in a new release, we test it just in case something broke.

In the list there are more or less 60 items, lets say it takes 1 minute per item to test it (it takes more) that means that it will take roughly an hour to test an entire release. Now multiply this per 4 which is the number of releases we have been doing and you will get 4 hours we invest on QA.

Besides the work we do before each release there is a constant effort of bug triaging that becomes way more difficult when you support a variety of versions since it makes you have to switch to a given version to try to reproduce and fix a bug you can’t reproduce with the version you are using.

If it is that much trouble, why have you been doing it?
In one word: distributions. Each distribution has a different time table, each distribution has a different minor release policy, each distribution is a different world. At the time we started doing this, Bluetooth in KDE was a mess so the highest priority was to have a good experience in all distributions. It should not matter which Bluedevlil version they were using.

Nowadays the situation has changed, we work quite well in all published versions so if a distribution does not upgrade (for whatever reason) the user won’t die.

So, now what?
From now on we are going to maintain only one version, and we are not going to support (or give support) to any other. This means that if a bug is reported with an old version the first thing we are going to ask is to upgrade and test again (if the part that is supposedly broken has been updated).

We are going to release 1.3.1 soon, and possibly another minor release for 1.3 if we have any bugs to fix. Then we will focus on implementing some of the wishes we have been ignoring for years (sorry for that :/)  and release 1.4. Once that happens 1.3 will be automatically deprecated and only 1.4 will be supported.

Personal thoughts:
I find it quite sad that after all this years going the extra mile so distributions can have a good Bluetooth experience, nobody stepped up to maintain stable releases. I guess this means that we are doing the right thing after all.

So, if your distribution is not shipping the latest BlueDevil version or it is not upgrading to it ask them to do so!

If after this blog post somebody feels like taking the job of maintaining the stable releases please, kde-hardware-devel@kde.org is your list !

The XRandR1.1 extension dates from 100B.C and it only knows about one screen on which you can change: size,  refresh and rotation. Luckily all modern drivers implement at least XRandR 1.2 (which know about multiple screens) so you may be wondering why do we bother to support such an old thing?

It turns out that virtualization software usually only support XRandR1.1 and some other tools like Xvnc or Xephyr do as well, so the only way of ensuring that we look good when executed in those software is by implementing support for this old api.

Can you imagine what impression will a potential user get if the first thing we do while executed in a Virtualbox is crashing? not good for sure.

So, we are a step closer to consider ourselves complete

Cheers !

List of unique changes in 1.3 final:

• 308324: Fixes crash in obexftp KDED module
  
• 304785: Fixes crash in obexftp KDED module (yes, another)
• 311152: Fixes crash in network-dun plugin when no adapter is present
• KDED crashes
• Do not show PANU in kiobluetooth since it is not supported
• Use common version number in all components (correct version reporting)

As always you can download it from:

http://download.kde.org/stable/bluedevil/1.3/src/bluedevil-1.3.tar.bz2

md5: 3a90e8826eb9f464084bbdafa549bf3e
sha256: 6dd3cca20da3ab89af1514717b969cf6d549ead4cd4f3b1f7b23ffe7e5d282e3

Hope you enjoy it !

This release comes with two main components, the System Settings module which will let you configure and arrange your screens in any way you desire, and the KDED module which will remember and restore configurations whenever it is needed.

We have decided to release now since we have fixed pretty much all the bugs reported by our early adopters (special thanks and hugs to them) so we feel that it is about time we let power users test it so we can fix any bug that may still exists.

The System Settings module:

KScreen System Settings module from Àlex Fiestas on Vimeo.

The KDED (magic) Module:

New KDE Screen Management from Àlex Fiestas on Vimeo.

You can download tarballs from:

http://download.kde.org/unstable/kscreen/0.0.71/src/kscreen-0.0.71.tar.bz2

http://download.kde.org/unstable/libkscreen/0.0.71/src/libkscreen-0.0.71.tar.bz2

We asked packagers to fill this wiki page with instructions of how to install KScreen in their distributions, so far only Kubuntu and Arch did it :/ so ask your distribution to create packages for it !

We are trying be as smart as possible adapting the behavior of it to each use case making the configuration of monitors as simple as plugging them to your computer.

A video is worth more than a million words:

New KDE Screen Management from Àlex Fiestas on Vimeo.

The behaviors are still not finished and we may change our defaults based on feedback and field test, but eh! it is a start :p

I’d like to personally thanks Red Hat for sponsoring Dan and my employer BlueSystems for letting me squeeze some time to move this forward.

Finally if you want to get this working:

1. Compile libkscreen
2. Compile kscreen
3. qdbus org.kde.kded /kded org.kde.kded.unloadModule randrmonitor
4. qdbus org.kde.kded /kded org.kde.kded.setModuleAutoloading randrmonitor false
5. qdbus org.kde.kded /kded org.kde.kded.loadModule kscreen

Enjoy !

Since I talked about it we have done 2 more shows:

KDE TeaTime #8 – If you could change one default setting, what would it be?
http://www.youtube.com/watch?v=wgv0etfJdNE

KDE TeaTime #9 – When to release?
http://www.youtube.com/watch?v=8-pcPeUsznE

And for the next one in order to properly celebrate the #10 show we have prepared some giveaways !

During the show we will explain how to participate in the raffle so make sure to not miss it!

Cheerz!

My configuration
I’m a heavy email user, every day  I receive and read hundreds of them, and I love to have my email synchronized across devices (laptop, workstation, phone, tablet) and particulary in my laptop and workstation I want to have all my email offline so I can make use of it with or without internet, specially useful on my laptop while traveling. Because of all those reasons I have to use something called Disconnect IMAP.

My EMail account
The account has 5.6GB of data and according to GMail it is split in 700K emails (more or less) 200K of those emails are in a folder (label in GMail) called kde-commits with a size of 1.8GB, then it has 5 folders with more than 25K emails and around 200MB of data each, and finally the rest are just small folders with 500-5000 emails. In total there are 70 folders.

First import experience
The first problem I have with KMail2 is the experience out of the first email import. Since my account is so huge it takes a while (around 15 hours) to make the full import and I can’t use the application while doing it because either the data won’t be available or all my CPU power will be used in the task.

To fix this we designed something called “Spanish sync” which basically consist on splitting the task of “Downloading all email while indexing it” into the following steps:

1. Download all the envelopes (subject,from, to, and some other data) starting from the most recent. Once this is done KMail will be fully functional (full email will be downloaded when user tries to read it).
2. Download in a controlled way all the email bodies (where the content of the email is). Right now this goes as fast as your internet line allows which can be a problem for people having a fast internet connection (100Mb in my case) and slow machine (my laptop is 6yrs old). Once this finishes the email content will be available offline.
3. Finally we will index all emails. If the user tries to search before this is done we will show an progress indicator.

The full synchronization of my email is still going to take 15 hours but I will be able to use my application almost since moment one (since it will import most recent emails first).

KMail not showing email body
Even though I set my account as “Disconnected IMAP”, more or less 50% of my emails were not being downloaded so I kept getting this “loading email” message from KMail. This is specially annoying when I’m on my laptop since the internet availability while traveling is not reliable. We have not been able to identify the reason why 1 out 2 emails is not being downloaded but at least I learned how to diagnose this.

Execute the debugging application “akonadiconsole” and go to the “DB console” tab and execute the following SQL query:

SELECT count(*) FROM parttable WHERE name = “PLD:RFC822″ AND data is null;

The result should be a small amount of your total email (in my workstation it is 4K while in my laptop it is 300K). If you set your account as “Disconnected IMAP” and you are getting a high number you may be suffering the same bug.

Unfortunately there is no way to force Akonadi to download the missing body for all those emails… so you will have to either live with it or re-import your account.

KMail not updating email status, not loading anything, not working !
If all your email is offline and you do not suffer from the bug I mentioned before, you won’t even notice this… but if you are using “Normal IMAP” or you suffer the bug this is the most annoying behavior.

Basically all the actions you perform are put in a queue to be processed, for example if you read 100 emails while offline, those “100 read actions” will be stored locally and pushed to the server once online. Where is the problem? the problem is that right now “pushing” this information blocks any other operation to be sure that we are using fresh data so if for instance email XXX is requested akonadi won’t provide it until the the “pushing” finishes.

In most IMAP servers pushing this data is FAST, but for some reason in GMail each modification takes around 1/2 seconds… so if I set as read 100 email or I delete 2000 make the math :p

The solution for this is conceptually quite easy, we should only block operations that affect email XXX instead of blocking everything. The technical implementation is a little more difficult than that :p

You can use akonadiconsole to check this “todo list”, open it go to “Agents” tab, and in there open the context menu on the agent you want to check and click on “show change-notification log”.

Summary:
Akonadi and Kontact2 are an awesome piece of software, I have no doubts that once the issues I mentioned here are fixed we will offer a better user experience than the one you get either in osx or Thunderbird.

As a note, Thunderbird or iMail take also 15 hour to fetch all my email, with the difference that I can use my email right the way, we are not that far.

Finally, a screenshot of how I’d like KMail to look like by default… and I’m not the only one asking this :p

Edit: to have this config just do:

Settings–>Appearance–>Layout–>Show the message preview pane next to the message list
Settings->Appearance–>Message List–>Default Thene: Fancy with Clickable Status

Though I have met some PIM hackers through the years I have been around KDE, I never had the opportunity to actually work with them, and try to figure things out, and as it is usual in our community they haven’t disappointed me.

I had 2 objectives for this sprint, first get a few bugs that I discover while working on WebAccounts fixed, and secondly try to track down all the KMail issues I have when I run it in my laptop. In this blog post I will only cover the first block.

Collections that can’t be de/activated

This is a really stupid bug, but in my humble opinion these are the kind of things that makes the user feel that they are using inferior quality software.

If you take a look at the following pic, you will see how there is a checkbox left of my email address that apparently will activate or deactivate all the contact groups provided by my Google account, well it doesn’t do anything so clicking on it results on basically nothing.

I tried to fix it and successfully tracked the bug down to a piece of code, but I needed help from the PIM hackers to actually fix it, and of course they didn’t disappointed, in a matter of hours it was fixed

KMail and the “Broken” imap resource

Just after a new IMAP resource was added (doesn’t matter if from KMail or Kontact or any other method) a notification will appear saying that the IMAP resource is broken. Wait what? is it broken? if I have just added it!

Well, not this is fixed since KMail now knows how to differentiate between a broken IMAP resource and one that has not been yet configured.

Activate resources when added

Another small bug or behavior that really bothers me is that when a new resource is added (for example a Google account is configured), the new added Calendars or Agendas won’t be “activated/checked” by default. I think that if you just added something is because you want to use it, don’t you think?

Well, this problem may seem simple but it isn’t, so after taking a look at it with the PIM hackers we thought a good way to fix it, though we didn’t had time to fix it.

http://lists.kde.org/?l=kde-pim&m=135040360317368&w=2

If nobody does, I will try to fix it when possible.

See you in part 2!

My main motivation for having this show is to open a door to the insides of KDE. This door is open both ways so the communication should and must be from Developers to Users and the other way around, so please participate !

Some urls of interest:

• Youtube channel
• Facebook page
• Plus page

In order to have MTP support we needed a “kio-slave”, which has been developed by Philipp Schmidt, and then modify some parts of our workspaces (dolphin, kdelibs and notifier) to integrate the MTP devices as if they were just regular massive storage (pen drives).

As usual, small screencast showing how well it works:

Vimeo link

Direct link

How to install?
To have basic support for MTP you have to install “kio-mtp”, executing the following:

git clone http://anongit.kde.org/kio-mtp
mkdir kio-mtp/build
cd kio-mtp/build
cmake ../ -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=Debugfull #(THIS MAY BE DIFFERENT)
make install

Or simply ask your distribution to package it

As for the Workspaces integration, I expect to get the patches in for 4.9.2 and 4.10

Cheers !

The paper cut is quite simple, before these patches we were using the “device description” for all devices, which make sense for devices always plugged into the computer for example the normal Hard Drive where your operating system is usually installed, but it doesn’t make sense for removable devices.

You will understand this better and quicker with the following screenshots:

 and after 

Patches are under review, if everything goes ok and I’m not breaking anything (little bit concerned about freeBSD support) will backport this to 4.9.

Cheerz !

As you may know, for the last months I have been working on BlueSystems, one of my main projects has been creating a working prototype of “WebAccounts”.

What is WebAccounts?
It is a centralize place where both, users and applications can configure accounts related to various social/cloud services such twitter, identi.ca, google, facebook, dropbox, owncloud, ftp servers…

How is it done?
We have implemented a KCM (module within System Settings) that allows the user to configure a set of accounts (at the moment Google, Facebook, Owncloud and runnersID), once the account is configured you can enable a few services for each account, for example for Google you can enable: email, calendar, contacts, tasks and chat.

Right now, the only integration is from within WebAccounts towards the already existing subsystems such akonadi or telepathy. In the future will be those projects the ones providing plugins and asking WebAccounts for credentials and information.

Is it really worth it?
In Akademy-es 2012 we presented the project to the audience there. One of the points I added in the slide was the amount of steps needed to configure a Google account right now and how many steps were needed to do it in WebAccounts. I don’t remember the exact number but it was something like 25 to 3.

Places where to configure a Google account right now:

• Add the account to Telepathy (one wizard, add credentials)
• Use the KMail wizard to add the account (credentials asked again)
• Configure Contact  (again add the same credentials)
• Configure Calendar, select the account added when Contact was added
• Configure Tasks, can be done in the same step of Calendar

With WebAcounts this would be:

• Click on “Add Google account”
• Introduce credentials (only once)
• Select all services (selected by default)

As you can see, the amount of steps has been reduced drastically actually bringing the possibility of integrating these kind of accounts in the workspace in an easy and clean way.

How it looks like?

Be aware that this is a prototype! I expect the real version to look way nicer !

And how it works?
(Choose 1080 quality for better video)

Vimeo link

Direct Link

Future?

Big part of WebAcounts future is going to be discussed at Akademy2012, where I hope to trace a roadmap together with the rest of people interested on it so we can push this concept further.

From 11jun to 18jun we had an amazing sprint in a small town near Barcelona called Pineda de Mar. This sprint was organized to gather all the developers highly motivated in move the Desktop forward, including those working in areas not strictly related to what the user sees or not strictly known as part of the desktop. We had a week of fun and work lead (as usual :p) by Kevin Ottens.
We had endless discussions about our weak and strong spots , hacked a little bit (some more than others), played table tennis (Yay for the Southern European team vs the British Empire), and enjoyed good quality food done mostly by Dario Freddi (let the italians cook we say) though more people worked in the kitched to prepare delicious disesh (Kevin, Sebas, Clemens, Marco Martin, Lluis Eskerda…).

It is hard to describe what the environment of a sprint is like, just imagine that you are with your best friends a whole week doing what you love only stopping for eating and having fun. In this case KDE is the people and what we love is our software, full week non-distractions equals super productivity of all kinds. It is hard to summarize the whole week, but these are my personal highlights of the sprint:

• Almost everybody attending the sprint would like shorter and more dynamic releases (à la chrome or kernel).
• Everybody agrees that we must be careful when modifying the Desktop, we don’t want to make it worst !
• Common agreement that we have to start looking for alternative to the current windows 95 paradigm.
• Our current notifications suck and we know how to fix’em (1) (2) (3).
• Virtual desktop are a thing from the past in its current state.
• Activities are a super awesome concept, yet we are nowhere close to make them appealing in the desktop (as they are in the tablet)
• Knowledge about Plasma terminology was shared and kind of agreed on (did you know that Plasma Active is about all form factors? yes! that includes the desktop !)
• We need better PulseAudio support
• We need a better screen support
• Lots of stuff to clean and polish! papercut program by Agateau on the way
• Lot of people using icontask (this is more of a personal note :p)
• WebAccounts is supermegaultraimportant, we need it now.
• We want KTp or even better “KPeople” everywhere, it will become one of our new pilars.

On this list (I hope quite close to the reality) you can see more or less the feeling of the Desktop developers, and especially that it is alive in all senses.

Photos taken by Martin Klapetek

I hope you could see a glimpse of how intense a sprint is lived and how useful they are.

Bye !

Besides writing code, I’m starting to be involved in other areas all across our community, one of them is KDE-España.

KDE-España is the legal representation of KDE in Spain, you can consider it as a sister of KDE e.V but only for the local community. One of the activities we do is the Akademy-es, a gathering of users and developers that happens every year in a different city of the country, so far we have had: Barcelona, Saragossa, Coruña, Bilbao, Barcelona, Saragossa (again :p) and sure more to come.

You may think these events are less important than writing software and that I shouldn’t waste my time there. I say you are wrong and that at least they are equally important.

As a personal note, for me it is becoming one of the events I wait the entire year to attend even if it is only to see the group of friends I only see in that conference.

So I’d like to encourage you to organize Akademy’s or smaller events on whatever city/country you live in, building a strong local community is crucial for keeping this global ship alive.

Can’t wit for Akademy-es 2013

The amount of devices we have and we use is increasing and so does the amount of data we manage, some may think that a regular non geek user has few files but if you take a closer look you will see that the average user actually has hundreds of pictures, hundreds of sounds, hundreds of films, dozens of documents… So we have to ask ourselves a question: Can we continue with the model of copying that data around? the answer is no.

Motivated by that need users are starting to setup a central computer or a device such a NAS with the only propose of  storing data and make it available to any device that may need it such: cell phones, players, ebook readers, tv’s, other computers etc. Some times that central place is not even a computer dedicated to do that job but instead the daily used computer, I’m specifically thinking on a laptop.

The file transfer are usually done with protocols such nfs, webdav, ftp or samba being this last the most common at least in commercial devices. The need for supporting this is clear as users of these systems increase, so how well do we support Samba?

We have had a kick ass technology called KIO for years, I believe it was developed in KDE 2 and basically it allows to use remote files as if they were local,  meaning that you can use files in an ftp for example without having to use any special programs for it. Even with KIO, we have identify some issues that need to be solved before we can say that our remote file support has no gaps, for example streaming or support for applications not supporting KIO.

Let’s say for example that we have a collection of music in a NAS device and they are shared through Samba, can we reproduce them using any KDE application? or better, can we stream and reproduce them? the answer is sadly no.

There are a series of technical problems that we have to fix to make KDE software fully capable of streaming music, I won’t bother you with technical details just know that actions are being taken to fix this situation and because of KIO we should be able to stream music on applications that use it in no time hopefully in 4.9.0 or 4.9.1.

What about applications not using KIO, is there any way for making them work ? short answer is it depends.

There are technical mechanisms for making Samba remote files look like local for all applications, for example for this protocol we have cifs, smbnetfs and fusesmb. According to the tests we performed only cifs is fast enough to provide a good experience but still you usually need to know some command or edit a file you are not supposed to modify in order to have a good experience so it is not a solution by itself.

We are designing a solution that will make KIO available to any application, but that will take months of developing and testing  and we needed something fast, something to include in Netrunner 4.2 Dryland SE… So we created samba-mounter.

Samba-mounter is a small piece of code that makes easy the usage of cifs, improving the experience of those who need to access files shared through samba.

Take a look at the following video:

Direct Link

You can download the code from here:

http://quickgit.kde.org/index.php?p=scratch/afiestas/samba-mounter.git

I expect to write a blog post explaining the long-term solution in the following weeks.

I’m glad to say that I will be sponsored by Blue Systems to work on various parts of the Workspace, so far we have defined two areas of work:

• Improve transparent file browsing (KIO) and make it available to all applications.
• Improve web and online services integration into the Workspace, by adding a single point of configuration.

In these two months I have been working already on those areas making the first releases that will be included in the  upcoming netrunner version (4.2 Dryland SE). Both releases are designed to be a first stone of a much complete solution on which I will be working on at least  for the following 6 months.

For those of you who may be wondering, this changes nothing regarding my other KDE implications, I’m going to continue working on BlueDevil (bluetooth) and libsolid and other projects I’m cooking while others sleep :p

Let’s keep rocking !

It was a worm afternoon in Madrid, the meeting I attended was so intensive I didn’t get to login into the KDE Plasma Workspace session but instead I let the laptop on the KDM login page. Once the session finished I closed my laptop and put it in my bag full of battery.

I’m not sure about the amount of time, but probably between 3 to 4 hours later I arrived home, opened my backpack and there it was, I found my laptop burning, hot as hell I even had to grab a cloth to open the lid and move the laptop to some place cool. From that day my new battery went form 98% of capacity to 90.

That night, I  sent an email to some KDE mailist asking for this issue, until today nothing has been done to fix it.

I don’t want anybody to pass from the same I went through, that’s why now with lightdm-kde the computer will suspend if the lid is closed.

Next thing I want to do is show the battery remaining somewhere and suspend the computer after 2 minutes of idle time.

With that, lightdm-kde will have great power management support.

Once I fixed all those damn crashes I proceeded to do bug triage and managed to fix all of the confirmed bugs, or said in another way BlueDevil is virtually bug free bug list :)

There are still a couple of bugs with iPhones, but I will need one of those to be able to confirm and fix the issues. Any donation?

The changelog looks as follow:

Fixes for 1.0.7, 1.1.4, 1.2.3 and 1.3-rc2

• BUG: 298633 // Crash in kded daemon (ObexFtp module)
• BUG: 279911 // Crash after receiving a file
• BUG: 297785 //Not confirmed if it is fixed
• Updated pin databse for more automatic experience

Fixes for 1.1.4. 1.2.3 and 1.3-rc2

• BUG: 286466 // Be able to pair WiiMotes (needs BlueZ 4.96)
• BUG: 276911 // Pairing Keyboards with SSPairing (Bluetooth 2.2)
• BUG: 291708 // Now we show again the small overlay icon

Fixes only for 1.3-rc2

• BUG: 284052 // Nasty crash every time adapter is unplugged

Now I can proceed and create new bugs by continuing with BlueDevil 2.0 and Screen Management.

libbluedevil 1.9.2
md5sum: b492db1825b239e5185c543badb21c26
sha256sum: 00d56fc671fecda1e60aa8231ba167f11002148098d6510df0a409d19e840d59

bluedevil 1.0.7
md5sum: 27e48595679bac72f6ea0d1f496ce524
sha256sum: 2294f921de0a2920dbfe8b3f824abd8b7d468da71a8bce5e4575be311bc0af65

bluedevil 1.1.4
md5sum: b485e0a710146536362cd607bcc3a418
sha256sum: c0bab0d6a505dbe96d3f6acaad8bdf4aea4de84c342e0e6e59b47e0d5bcba6d6

bluedevil 1.2.3
md5sum: e792576d34956d27cd0c3eb3c81a5923
sha256sum: 7744e0544d27960f21073cf4b48ba865162a2643b7e33f7f21fff43705b4e624

bluedevil 1.3-rc2
md5sum: 20452c528ab04c0551f3d8bfc5075c4b
sha256sum: db6735d5a66634ce5d761c70df4ad7c4f39295ac4a6f9b59bcc25777dc720dd5

Cheers !

As far as I know this is the first PA sprint where a lot of community members external to the project attended, this is really great for opening the project to other areas of KDE, such Solid or KDEdu.  My work focus were:

Getting to know the inside of the project
Every project structure is different even between close projects such PowerDevil and BlueDevil. In the case of PA there are a few big differences that have to be taken into account:

 It is important that you agree with the rules of the game before you start to play it, I find PA a really good example of how a professional project can be done together with the community without sacrificing anything. I agree with this rules so I will play this game

• Share/Like/Connect for the desktop must happen
• Having a centralized place for Sharing is important (probably in the shell)
• We need a centralized place to store Web/Online account information
• We need to have a shared platform for streams (twitter, identi.ca, facebook…)
• Having libkpeople finished is crucial, we must have unified personas to work with

I will probably be working on the first point, but we will see about that later.

Finally, a mandatory picture took by Martin K.