https://community.kde.org/api.php?action=feedcontributions&user=Achim&feedformat=atomKDE Community Wiki - User contributions [en]2024-03-29T00:32:56ZUser contributionsMediaWiki 1.40.2https://community.kde.org/index.php?title=Fireside_chats&diff=90940Fireside chats2021-01-21T16:20:55Z<p>Achim: /* Registration */</p>
<hr />
<div>== '''Upcoming Event:''' ==<br />
==== '''12 February 2021 at 17:00 UTC''' ====<br />
'''Fireside Chat with Luis Falcon about MyGNUHealth'''<br />
Let us know you are attending! Please sign-up at the bottom of the page.<br />
<br />
Luis is a physician, computer scientist, and free software activist. Luis spoke at Akademy this past September, at the Linux App Summit in November, and will be making an appearance at FOSDEM in February.<br />
<br />
For those new to MyGNUHealth, it is an application that gives us control over our own health, keeping a record of our blood pressure, heart rate and so on, thus allowing us to monitor the state of our vitals at all moments.<br />
<br />
With a focus on privacy, the application is Libre software and provides a way of integrating with the larger ecosystem of public healthcare, while ensuring our data is not being leaked to third parties. The application offers different types of functionalities, not only focusing on the physiological aspects of health tracking, but also including trackers for signs of stress – of great importance when monitoring our psychological health.<br />
<br />
Luis’ mission, both with GNU Health and the MyGNUHealth application, is to help us and the healthcare system improve our well-being.<br />
<br />
Once again, please join Luis on February 12th at 17:00 UTC for a fireside chat about the MyGNUHealth application and its future as part of the KDE Family. There is no registration required <br />
<br />
<br />
===== '''Room Link:''' =====<br />
[https://meet.kde.org/b/all-whh-oty Join the Meet Up!] <br />
<br />
''If you are new to KDE & Akademy, you will first need a [https://identity.kde.org/ KDE identity Account]''<br />
<br />
<br />
=== Registration ===<br />
Please let us know you are joining! <br />
<br />
{| class="wikitable"<br />
Edit this area with your name<br />
|-<br />
| Luis || Allyson || || || <br />
|-<br />
| Luna || Jernberg|| || || <br />
|-<br />
| Hutson || || || || <br />
|-<br />
| Achim || Bohnet || || || <br />
|-<br />
| || || || || <br />
|-<br />
| || || || || <br />
|-<br />
| || || || || <br />
|-<br />
| || || || || <br />
|-<br />
| || || || || <br />
|-<br />
| || || || || <br />
|}</div>Achimhttps://community.kde.org/index.php?title=KDE_PIM/Meetings/PIM_Winter_2014_meeting&diff=40399KDE PIM/Meetings/PIM Winter 2014 meeting2014-11-20T16:47:49Z<p>Achim: /* Usability - User stories and scenarios */</p>
<hr />
<div>= Topics =<br />
===Usability - User stories and scenarios===<br />
Enable user-centered design through user stories and scenarios based on actual users form the city administration of Munich.<br />
<br />
Interested: Michael Bohlender; Thomas Pfeiffer; Achim Bohnet<br />
<br />
===QML API===<br />
Discuss the future (architecture) of QML APIs for PIM stuff.<br />
<br />
Interested: Michael Bohlender; Daniel Vrátil, Christian Mollekopf<br />
<br />
===Active Mail/ KMail Mobile===<br />
Discuss the future of Active Mail.<br />
<br />
Interested: Michael Bohlender; Daniel Vrátil; Thomas Pfeiffer<br />
<br />
===Akonadi Framework===<br />
We already discussed this a lot during Akademy, this time I'd like to look into solving specific problems that Kolab guys have run into while preparing Akonadi and KDE PIM for Munich. I also want to actually sit down and design some of the major features/changes we are planning.<br />
<br />
Interested: Daniel Vrátil; Christian Mollekopf<br />
<br />
=== Mail Search Testing ===<br />
Searching within emails still has problems for quite a few people. We could use the collective brainpower present at the sprint to try to get to the bottom of the problem.<br />
<br />
=== Frameworks release schedule & Repository divisions ===<br />
Another discussion on how we exactly split up the repositories for frameworks (we know already many parts, but some are still left). Additionally we should discuss options for the release schedule.<br />
<br />
Interested: Christian Mollekopf; Daniel Vrátil; Aaron Seigo<br />
<br />
=== PIM Architecture and Design ===<br />
I think we should take a high level overview of what parts we have in kdepim, how they fit together and how this structure helps us getting done what we want in the future.<br />
<br />
This becomes especially relevant with changes in akonadi, the QML API etc. We need to know why we implement what where, and be able to draw clear lines between the various components in order to avoid them getting to complex. For this we need to have an idea how the architecture should look like that we are moving towards (even if this cannot be achieved as short-term goal).<br />
<br />
Interested: Christian Mollekopf; Daniel Vrátil; Aaron Seigo; Achim Bohnet<br />
<br />
=== Async library ===<br />
Current async code sucks and we need better tools. I'd like to have a brainstorming session on that so we can stop writing async handlers all over the place. Things that I'd like to see:<br />
* Composable jobs/tasks<br />
* higher order functions to be used with the composable jobs (map/filter/...)<br />
* reactive collections<br />
* transformations in reactive collections<br />
<br />
These building-blocks should result a generic KAsync (?) library. I'd like to see PIM spearheading this (I will anyways), since we are writing loads of async code.<br />
<br />
Interested: Christian Mollekopf;<br />
<br />
=Agenda=<br />
=Meeting Notes=<br />
<br />
=Organization=<br />
<br />
===Venue===<br />
<br />
LiMux Office<br />
<br />
Sonnenstrasse 25<br />
<br />
80331 Munich Altstadt-Lehel<br />
<br />
<br />
From Hauptbahnhof (main station) take the U1/U2 to Sendlinger Tor or the U4/U5 to Stachus (Karlsplatz). Follow the Sonnenstraße until you see the green sign of the Goethe Institut. Enter the passage. The entry is on the right-hand side. The LiMux office is in the 6th and 7th floor of the building; the Sprint is on the 7th floor. Doors should be open, but there will be several Sprint info sheets with phone contacts and directions.<br />
<br />
We can enter the Limux office at Fr 12:00 but the official start of the event is not until 18:00. <br />
There will be some noise as the Limux guys are transforming their regular working place into a meeting space.<br />
<br />
===Accomodation===<br />
<br />
A&O München Laim<br />
<br />
Landsberger Straße 338<br />
<br />
80687 Munich Laim<br />
<br />
<br />
5 minute walking Distance form "Laim" S-Bahn station.<br />
<br />
Checkin from 15:00. Checkout until 11:00.<br />
<br />
===Transit===<br />
<br />
'''Airport -> Hostel:''' take the S1 S-Bahn and exit at "Laim".<br />
<br />
'''Hauptbahnhof -> Hostel:''' take any any S-Bahn except S7 towards "Pasing or Laim" exit at "Laim".<br />
<br />
'''Hostel -> Venue:''' take any S-Bahn towards "Hauptbahnhof". Ride 5 stations till you reach "Karlsplatz/Stachus".<br />
<br />
===Catering===<br />
<br />
We're stacked with a bunch of different non-alcoholic beverages and snacks (sweets, fruits, ...). Coffee and tea will be prepared on demand.<br />
<br />
There will be 3-4 meals (Fri + Sat evening, Sat + Sun lunch), which will be cooked at the venues (needs 4-5 people). If we choose to go out for a dish - in contrast to cooking - this won't be sponsored by the project.<br />
<br />
There'll be a continental oriented breakfast for Sat + Sun available; some rolls, bread, hazelnut spread, jams, a bit of cheese and cold meat.</div>Achimhttps://community.kde.org/index.php?title=KDE_PIM/Meetings/PIM_Winter_2014_meeting&diff=40398KDE PIM/Meetings/PIM Winter 2014 meeting2014-11-20T16:46:48Z<p>Achim: /* PIM Architecture and Design */</p>
<hr />
<div>= Topics =<br />
===Usability - User stories and scenarios===<br />
Enable user-centered design through user stories and scenarios based on actual users form the city administration of Munich.<br />
<br />
Interested: Michael Bohlender; Thomas Pfeiffer<br />
<br />
===QML API===<br />
Discuss the future (architecture) of QML APIs for PIM stuff.<br />
<br />
Interested: Michael Bohlender; Daniel Vrátil, Christian Mollekopf<br />
<br />
===Active Mail/ KMail Mobile===<br />
Discuss the future of Active Mail.<br />
<br />
Interested: Michael Bohlender; Daniel Vrátil; Thomas Pfeiffer<br />
<br />
===Akonadi Framework===<br />
We already discussed this a lot during Akademy, this time I'd like to look into solving specific problems that Kolab guys have run into while preparing Akonadi and KDE PIM for Munich. I also want to actually sit down and design some of the major features/changes we are planning.<br />
<br />
Interested: Daniel Vrátil; Christian Mollekopf<br />
<br />
=== Mail Search Testing ===<br />
Searching within emails still has problems for quite a few people. We could use the collective brainpower present at the sprint to try to get to the bottom of the problem.<br />
<br />
=== Frameworks release schedule & Repository divisions ===<br />
Another discussion on how we exactly split up the repositories for frameworks (we know already many parts, but some are still left). Additionally we should discuss options for the release schedule.<br />
<br />
Interested: Christian Mollekopf; Daniel Vrátil; Aaron Seigo<br />
<br />
=== PIM Architecture and Design ===<br />
I think we should take a high level overview of what parts we have in kdepim, how they fit together and how this structure helps us getting done what we want in the future.<br />
<br />
This becomes especially relevant with changes in akonadi, the QML API etc. We need to know why we implement what where, and be able to draw clear lines between the various components in order to avoid them getting to complex. For this we need to have an idea how the architecture should look like that we are moving towards (even if this cannot be achieved as short-term goal).<br />
<br />
Interested: Christian Mollekopf; Daniel Vrátil; Aaron Seigo; Achim Bohnet<br />
<br />
=== Async library ===<br />
Current async code sucks and we need better tools. I'd like to have a brainstorming session on that so we can stop writing async handlers all over the place. Things that I'd like to see:<br />
* Composable jobs/tasks<br />
* higher order functions to be used with the composable jobs (map/filter/...)<br />
* reactive collections<br />
* transformations in reactive collections<br />
<br />
These building-blocks should result a generic KAsync (?) library. I'd like to see PIM spearheading this (I will anyways), since we are writing loads of async code.<br />
<br />
Interested: Christian Mollekopf;<br />
<br />
=Agenda=<br />
=Meeting Notes=<br />
<br />
=Organization=<br />
<br />
===Venue===<br />
<br />
LiMux Office<br />
<br />
Sonnenstrasse 25<br />
<br />
80331 Munich Altstadt-Lehel<br />
<br />
<br />
From Hauptbahnhof (main station) take the U1/U2 to Sendlinger Tor or the U4/U5 to Stachus (Karlsplatz). Follow the Sonnenstraße until you see the green sign of the Goethe Institut. Enter the passage. The entry is on the right-hand side. The LiMux office is in the 6th and 7th floor of the building; the Sprint is on the 7th floor. Doors should be open, but there will be several Sprint info sheets with phone contacts and directions.<br />
<br />
We can enter the Limux office at Fr 12:00 but the official start of the event is not until 18:00. <br />
There will be some noise as the Limux guys are transforming their regular working place into a meeting space.<br />
<br />
===Accomodation===<br />
<br />
A&O München Laim<br />
<br />
Landsberger Straße 338<br />
<br />
80687 Munich Laim<br />
<br />
<br />
5 minute walking Distance form "Laim" S-Bahn station.<br />
<br />
Checkin from 15:00. Checkout until 11:00.<br />
<br />
===Transit===<br />
<br />
'''Airport -> Hostel:''' take the S1 S-Bahn and exit at "Laim".<br />
<br />
'''Hauptbahnhof -> Hostel:''' take any any S-Bahn except S7 towards "Pasing or Laim" exit at "Laim".<br />
<br />
'''Hostel -> Venue:''' take any S-Bahn towards "Hauptbahnhof". Ride 5 stations till you reach "Karlsplatz/Stachus".<br />
<br />
===Catering===<br />
<br />
We're stacked with a bunch of different non-alcoholic beverages and snacks (sweets, fruits, ...). Coffee and tea will be prepared on demand.<br />
<br />
There will be 3-4 meals (Fri + Sat evening, Sat + Sun lunch), which will be cooked at the venues (needs 4-5 people). If we choose to go out for a dish - in contrast to cooking - this won't be sponsored by the project.<br />
<br />
There'll be a continental oriented breakfast for Sat + Sun available; some rolls, bread, hazelnut spread, jams, a bit of cheese and cold meat.</div>Achimhttps://community.kde.org/index.php?title=Plasma/Active/WeTab&diff=34366Plasma/Active/WeTab2013-09-13T14:34:24Z<p>Achim: /* Mer Plasma Active Live (Installable) Image */ replace link to notmarts iso with the one by basyskcom as advised on irc</p>
<hr />
<div><br />
=== Mer Plasma Active Live (Installable) Image ===<br />
<br />
[http://basyskom.com basysKom] provides a [http://community.kde.org/Plasma/Active/Installation#WeTab_.2F_ExoPC bootable image] of Plasma Active 4 for x86 based devices like '''WeTab''', '''ExoPC''' or the '''Idea Pad'''. Login Data: User ''mer'' password ''mer''; User ''root'' password ''mer''<br />
<br />
Follow the instructions below to create a bootable USB flashdrive.<br />
<br />
Further [http://basyskom.com basysKom] creates weekly Plasma Active Mer development and testing images. <br />
<br />
You can also try the installable Mer Live ISO for a USB flash drive or CD/DVD from [http://share.basyskom.com/plasma-active/wetab.html basysKom download center]. <br />
<br />
<!--<br />
=== Validate and Deploy on Microsoft Windows ===<br />
On Windows you can compare the hash on equality between image and related checksum file by the [http://support.microsoft.com/kb/841290 fciv.exe] tool. You will find all needed information about<br />
usage on this site.<br />
<br />
With the [https://launchpad.net/win32-image-writer win32-image-writer] tool you can easily deploy a plasma active image to a USB Flashdrive. For a detailed description how to work with this tool please see the MeeGo [https://meego.com/devices/netbook/installing-meego-netbook/windows-instructions Windows instructions]. --><br />
<br />
<br />
On Linux you can compare the hash between the image and related checksum file using the following command (with both the image and the checksum file in the same directory):<br />
<br />
user@host# '''sha1sum -c ''<checksum file>'''''<br />
<br />
user@host# '''md5sum -c ''<checksum file>'''''<br />
<br />
If the command returns "<image name>: FAILED", please download the image one more time and check again.<br />
<br />
<br />
After validation feel free to deploy the image to a '''not mounted''' USB flashdrive. In the following example we use the tool 'dd' for this:<br />
<br />
root@host# '''dd if=''<image file>'' of=/dev/''<USB flashdrive>'' bs=1M'''<br />
<br />
'''Please note, the usage of this tool is potentially dangerous! In case of a mistaken output device, all data on it will be irrecoverably lost'''.<br />
<br />
'''To get the correct output device for this tool, please follow the steps below:'''<br />
<br />
1. Remove all mobile flashdrives from your host system.<br />
<br />
2. Enter the command below and note the output.<br />
user@host# '''cat /proc/partitions'''<br />
<br />
major minor #blocks name<br />
8 0 3000000 sda<br />
8 1 2999998 sda1<br />
<br />
3. Plug the Flashdrive for deploying into the host system.<br />
<br />
4. Enter the following command and note the output again.<br />
user@host# '''cat /proc/partitions'''<br />
<br />
major minor #blocks name<br />
8 0 30000000 sda<br />
8 1 29999998 sda1<br />
8 16 3872256 '''sdb'''<br />
8 17 594944 sdb1<br />
<br />
5. In this example the correct dd parameter is '''sdb''' in the position of '''<USB flashdrive>'''.<br />
<br />
=== Booting the Live Image on a WeTab/ExoPC ===<br />
<br />
1. Plug the flashdrive into the WeTab/ExoPC (In some cases WeTab only works with special flashed BIOS from ExoPC).<br />
<br />
2. Press the power button <br />
<br />
3. Once the WeTab starts to boot (Blue LED on WeTab lights up or LED on stick lights up) press power button together with softtouch button (round area in top left corner of touch screen) for approximately 1 second (longer press will shut it down again)<br />
<br />
4. Press the softtouch button until it boots<br />
<br />
''Alternative instructions: Put usb stick in tablet and boot up, press BBS (on the touchscreen). You can go through the bootloader using the button in the top left corner of the screen, short press to move to the next entry, long press to boot it. A USB keyboard is needed to select the options during the install"<br />
<br />
==== Installation with USB keyboard ====<br />
<br />
1. Connect a USB keyboard to the WeTab<br />
<br />
2. Follow steps 1-3 above to get to the boot menu<br />
<br />
3. Press the softtouch button shortly to select "Installation"<br />
<br />
4. Hold the softtouch button until the boot procedure starts<br />
<br />
5. When the boot procedure stops, press enter on the USB keyboard and a message saying "Select one disk to install" will appear<br />
<br />
6. Type the number of the local SSD and hit <Enter><br />
<br />
7. Select "Full disc install" <Enter><br />
<br />
8. Confirm with <y> <Enter><br />
<br />
9. After the installation has finished, remove the USB stick and USB keyboard and press the power button until it shuts down. <br />
<br />
==== Installation without USB keyboard ====<br />
Please choose via 6 second tab on frontside sensor button the 'Boot MeeGo' instead of 'Installation' entry. Wait until Plasma Active is boot completely into the user interface. Open the 'Konsole' application from the peek area by pulling down the top bar. Enter following commands via virtual keyboard to call the installer (password is 'mer'):<br />
<br />
<nowiki><br />
su <br />
export PATH=${PATH}:/sbin:/usr/sbin <br />
installer-shell <br />
reboot<br />
</nowiki></div>Achimhttps://community.kde.org/index.php?title=Plasma/Active/WeTab&diff=34365Plasma/Active/WeTab2013-09-13T13:13:12Z<p>Achim: /* Mer Plasma Active Live (Installable) Image */</p>
<hr />
<div><br />
=== Mer Plasma Active Live (Installable) Image ===<br />
<br />
[http://basyskom.com basysKom] provides an [http://community.kde.org/Plasma/Active/Installation#WeTab_.2F_ExoPC|bootable image of Plasma Active 4] for x86 based devices like '''WeTab''', '''ExoPC''' or the '''Idea Pad'''. Login Data: User ''mer'' password ''mer''; User ''root'' password ''mer''<br />
<br />
Follow the instructions below to create a bootable USB flashdrive.<br />
<br />
Further [http://basyskom.com basysKom] creates weekly Plasma Active Mer development and testing images. <br />
<br />
You can also try the installable Mer Live ISO for a USB flash drive or CD/DVD from [http://share.basyskom.com/plasma-active/wetab.html basysKom download center]. <br />
<br />
<!--<br />
=== Validate and Deploy on Microsoft Windows ===<br />
On Windows you can compare the hash on equality between image and related checksum file by the [http://support.microsoft.com/kb/841290 fciv.exe] tool. You will find all needed information about<br />
usage on this site.<br />
<br />
With the [https://launchpad.net/win32-image-writer win32-image-writer] tool you can easily deploy a plasma active image to a USB Flashdrive. For a detailed description how to work with this tool please see the MeeGo [https://meego.com/devices/netbook/installing-meego-netbook/windows-instructions Windows instructions]. --><br />
<br />
<br />
On Linux you can compare the hash between the image and related checksum file using the following command (with both the image and the checksum file in the same directory):<br />
<br />
user@host# '''sha1sum -c ''<checksum file>'''''<br />
<br />
user@host# '''md5sum -c ''<checksum file>'''''<br />
<br />
If the command returns "<image name>: FAILED", please download the image one more time and check again.<br />
<br />
<br />
After validation feel free to deploy the image to a '''not mounted''' USB flashdrive. In the following example we use the tool 'dd' for this:<br />
<br />
root@host# '''dd if=''<image file>'' of=/dev/''<USB flashdrive>'' bs=1M'''<br />
<br />
'''Please note, the usage of this tool is potentially dangerous! In case of a mistaken output device, all data on it will be irrecoverably lost'''.<br />
<br />
'''To get the correct output device for this tool, please follow the steps below:'''<br />
<br />
1. Remove all mobile flashdrives from your host system.<br />
<br />
2. Enter the command below and note the output.<br />
user@host# '''cat /proc/partitions'''<br />
<br />
major minor #blocks name<br />
8 0 3000000 sda<br />
8 1 2999998 sda1<br />
<br />
3. Plug the Flashdrive for deploying into the host system.<br />
<br />
4. Enter the following command and note the output again.<br />
user@host# '''cat /proc/partitions'''<br />
<br />
major minor #blocks name<br />
8 0 30000000 sda<br />
8 1 29999998 sda1<br />
8 16 3872256 '''sdb'''<br />
8 17 594944 sdb1<br />
<br />
5. In this example the correct dd parameter is '''sdb''' in the position of '''<USB flashdrive>'''.<br />
<br />
=== Booting the Live Image on a WeTab/ExoPC ===<br />
<br />
1. Plug the flashdrive into the WeTab/ExoPC (In some cases WeTab only works with special flashed BIOS from ExoPC).<br />
<br />
2. Press the power button <br />
<br />
3. Once the WeTab starts to boot (Blue LED on WeTab lights up or LED on stick lights up) press power button together with softtouch button (round area in top left corner of touch screen) for approximately 1 second (longer press will shut it down again)<br />
<br />
4. Press the softtouch button until it boots<br />
<br />
''Alternative instructions: Put usb stick in tablet and boot up, press BBS (on the touchscreen). You can go through the bootloader using the button in the top left corner of the screen, short press to move to the next entry, long press to boot it. A USB keyboard is needed to select the options during the install"<br />
<br />
==== Installation with USB keyboard ====<br />
<br />
1. Connect a USB keyboard to the WeTab<br />
<br />
2. Follow steps 1-3 above to get to the boot menu<br />
<br />
3. Press the softtouch button shortly to select "Installation"<br />
<br />
4. Hold the softtouch button until the boot procedure starts<br />
<br />
5. When the boot procedure stops, press enter on the USB keyboard and a message saying "Select one disk to install" will appear<br />
<br />
6. Type the number of the local SSD and hit <Enter><br />
<br />
7. Select "Full disc install" <Enter><br />
<br />
8. Confirm with <y> <Enter><br />
<br />
9. After the installation has finished, remove the USB stick and USB keyboard and press the power button until it shuts down. <br />
<br />
==== Installation without USB keyboard ====<br />
Please choose via 6 second tab on frontside sensor button the 'Boot MeeGo' instead of 'Installation' entry. Wait until Plasma Active is boot completely into the user interface. Open the 'Konsole' application from the peek area by pulling down the top bar. Enter following commands via virtual keyboard to call the installer (password is 'mer'):<br />
<br />
<nowiki><br />
su <br />
export PATH=${PATH}:/sbin:/usr/sbin <br />
installer-shell <br />
reboot<br />
</nowiki></div>Achimhttps://community.kde.org/index.php?title=Plasma/Active/Installation&diff=34364Plasma/Active/Installation2013-09-13T12:54:33Z<p>Achim: /* Plasma Active Images */ this iso is only for wetab/exopc: Move to corresponding paragraph</p>
<hr />
<div>= Plasma Active Images =<br />
<br />
The Plasma Active team provides official Images based on Mer for some devices.<br />
<br />
== Supported ==<br />
<br />
=== WeTab / ExoPC ===<br />
<br />
The hardware is a little outdated but you will get the most polished Plasma Active experience on this device. <br />
<br />
* [https://share.basyskom.com/plasma-active/deployment/wetab-exopc/tablet/mer/stable/basyskom-plasma-active-four-wetab-exopc-tablet-mer-release.iso Download ISO]<br />
* [https://share.basyskom.com/plasma-active/deployment/wetab-exopc/tablet/mer/stable/basyskom-plasma-active-four-wetab-exopc-tablet-mer-release-iso.sha1 Checksum] (sha1: 51bd1ac2aea097d8e17503a92ce2781a6532491d)<br />
* [https://share.basyskom.com/plasma-active/deployment/wetab-exopc/tablet/mer/stable/ Download Archive]<br />
<br />
Take a look at the installation instructions [http://community.kde.org/Plasma/Active/WeTab here].<br />
<br />
== Preview ==<br />
<br />
=== Nexus 7 ===<br />
<br />
Event though very much already works reasonably well, there are still some glitches. So, please don’t expect a 100% working system. For detailed installation instructions, see the article on the [https://wiki.merproject.org/wiki/Community_Workspace/Tegra3/Nexus7/PA_installation Mer Wiki]<br />
<br />
=== Archos G9 ===<br />
<br />
Take a look at [http://ruedigergad.com/2013/02/24/plasma-active-archos-g9-armv7hl-rootfs-tarballs/ Ruedigers Blog] for more information.<br />
<br />
=== Nokia N950 ===<br />
<br />
Take a look at [http://www.osnews.com/story/25307/Nokia_N950_Running_Plasma_Active_on_Mer this OSnews article] for more information.<br />
<br />
=== VirtualBox ===<br />
<br />
When running Plasma Active in a virtual machine, consider that performance will not be as good as when it runs naively on the devices it has been designed for. For testing, we strongly recommend running Plasma Active on a device. The following limitations need consideration when using a virtual machine instead of a real device:<br />
* Performance, especially graphics, boot and application startup might be reduced<br />
* Advanced visual effects might not be available or work correctly in the virtual machine. This can lead to degradation of certain features, performance, visual effects and possibly stability<br />
* User interfaces designed for touch-screens often work less efficiently for mouse and keyboard based input methods, or feel less natural.<br />
<br />
<br />
For detailed installation instructions, see this [http://community.kde.org/Plasma/Active/VirtualBox installation manual].<br />
<br />
= Downstream Plasma Active =<br />
<br />
Some distributions provide Images with Plasma Active for x86 Systems.<br />
<br />
== Kubuntu Active ==<br />
<br />
Current stable release of a Kubuntu remix with Plasma Active is available at<br />
<br />
http://cdimage.ubuntu.com/kubuntu-active/releases/13.04/release/<br />
<br />
Daily unstable images of a Kubuntu Active are at<br />
<br />
http://cdimage.ubuntu.com/kubuntu-active/daily-live/ <br />
<br />
You can burn image to CD (e.g. with k3b) or USB (e.g. with usb-creator-kde)<br />
<br />
https://help.ubuntu.com/community/BurningIsoHowto#Kubuntu<br />
<br />
It includes an installer '''ubiquity'''.<br />
<br />
== openSUSE ==<br />
<br />
PlasmaActive has been packaged for opensuse in the KDE:Active OBS Repository.<br />
Mind that it is ALPHA Quality. The apps that come with a Mer-based image might not be available and there may be bugs. Feel free to report (and fix) them or improve the packaging process. Help will be welcome!<br />
<br />
It can be installed as follows:<br />
<br />
zypper ar http://download.opensuse.org/repositories/KDE:/Active/openSUSE_12.3 PA<br />
<br />
zypper ref && zypper install plasma-mobile declarative-plasmoids bodega-client<br />
<br />
If the Maliit onscreen keyboard is wanted, additionally install maliit-framework maliit-plugins maliit-inputcontext-qt4<br />
<br />
Only i586 has been tested. To run PA4 the preferred method is to create a .xinitrc file in the home directory and add a line saying 'startactive'. Then a call to 'startx' will bring it up.<br />
<br />
There currently is an issue with plasma-desktop beeing started automatically so the file '/usr/share/autostart/plasma-desktop.desktop' needs to be (re)moved before running PlasmaActive.<br />
<br />
There is also a LiveCD available at http://susestudio.com/a/GzMWEV/activesuse<br />
<br />
= Get started after install =<br />
<br />
[http://community.kde.org/Plasma/Active/Info Suggestions, FAQ, additional information]</div>Achim