Task is done, if it needs changes, a new task can be opened.

Findyourway web page has been created. We may use this task for any change needed.

A while ago, I did some research on how convergence might work. I ended up with an overview of possible device types and a description of the corresponding user experience. I also tried to identify common elements in the UI that would need to be converted in order to move from one device's UX to another. I've documented this on the community wiki:
https://community.kde.org/Plasma/Convergence_Overview
I also created a forum topic for feedback, which you can find here:
https://forum.kde.org/viewtopic.php?f=285&t=131170

I had a rough day today (technically, it's not over yet), so I spent about $80 on a used LG V500 Android tablet that will run LineageOS. We have a wiki page for how to get PM up and running on a Lineage-powered device.

A plasma-modbile focused guide has been created covering topics like:

I can reproduce it on the phone. It may be related to that I cannot see notifications, only their count.

Closing this as bullhead port works reasonably well.

This is now fixed.

In T7790#134887, @sharvey wrote:

Has the list of supported devices for Plasma Mobile been updated lately? https://community.kde.org/Plasma/Mobile/FAQ only lists the LG Nexus 5 and LG Nexus 5X phones. I don't need another phone (sorry, dedicated iPhone user), but I'd be willing to shop for a compatible tablet if there are any that can run Plasma Mobile.

Adding 127.0.0.1 localhost.localdomain does the trick.

Has the list of supported devices for Plasma Mobile been updated lately? https://community.kde.org/Plasma/Mobile/FAQ only lists the LG Nexus 5 and LG Nexus 5X phones. I don't need another phone (sorry, dedicated iPhone user), but I'd be willing to shop for a compatible tablet if there are any that can run Plasma Mobile.

@asghaier Actually the best point for starting a device port is the Halium documentation and the Halium Telegram group. But of course the Plasma Mobile group is also helpful! :)

@bshah is probably your man. Also, join the Plasma Mobile Telegram group.

I am interested in porting plasma mobile to Oneplus 5t, can you point me to someone who can provide some assistance (mentoring)?
I will document all the steps required, contribute to the docs, blog about it and then maybe take some dev tickets or port to another device or assist others in porting.
I think this is very important to get better promotion and have more developers join.

Killed as it is now essentially halium porting guide.

I published Plasma Mobile projects for GSoC: https://community.kde.org/GSoC/2018/Ideas#Plasma_Mobile
Hope they get selected and students give us a nice blog post coverage :)

I'd consider this task as done : http://blog.bshah.in/2018/01/26/trying-out-plasma-mobile/

First impression: That is MUCH better, @ngraham. It is late here, but I will look over it in depth tomorrow.

I had a crack at re-organizing and rewriting parts of https://community.kde.org/Get_Involved to make it more approachable. What do you guys think?

In T7779#124502, @paulb wrote:

@PureTryOut, after following your instructions, this what I get when running the virtual machine:

What am I doing wrong?

For completeness repeating what was said on Telegram, yes that installation guide will do. We also have https://wiki.postmarketos.org/wiki/Plasma_Mobile for Plasma Mobile specific, but the former will do nicely. I assume most people understand they need to choose "plasma-mobile" when promped for a UI choice.

Should never become a public slogan, though 😬

"Plama Mobile: More than a vision"?

"Plasma Mobile is not only a vision" is a very, very strong point, and I feel that's what our internal slogan should be...

• I think it would be very important to have a CI (http://mobile.neon.pangea.pub:8080 ?) for building the halium images (boot and system),
• then we could write a simple tool that will download them and flash them to your device,
• and then we could write a simple tutorial for it and publish it in the wiki.

As for https://community.kde.org/Get_Involved, I think this would be a good step 2, but the text again needs some serious editing. The parts about Phabricator, for example, need cleaning up, taking out the section where the author mentions what it is built on and other irrelevant bits, and focusing on the features which will be immediately interesting for a newcomer. Also, illustrating with some images would help clarify things for people unfamiliar with the platform.

@PureTryOut I copied a list of devices with screen working, where should we point testers for installation instructions?
EDIT: this page seems nice: https://wiki.postmarketos.org/wiki/Installation_guide

Yeah, that's a good one!
Forums are in a sad state, so as a way to contact, we'd better provide #plasmamobile:matrix.org and https://t.me/plasmamobile.

Apart from the developer guide that @bshah linked above, there's also this:

https://community.kde.org/Plasma/Mobile

and its subpages. Not sure how up-to-date all this informat

Apart from the developer guide that @bshah linked above, there's also this:

*nod*

Not especially thinking of new ways, @lydia , more along the lines @ngraham points out, that is, the best guide we can find so we can, if possible, improve it and point new potential contributors to it.

It would be awesome if we could have a page like https://whatcanidoformozilla.org/#!/progornoprog/advocate
(even on wiki)

@lydia I've been pointing people to https://community.kde.org/Get_Involved, which is really good. We might consider centralizing information there and deprecating all of our other redundant points of entry.

Before we start introducing more ways of getting people in board let's please consolidate and improve what we have. At the end there should be one place where people get started for contributing to KDE and then only additional guides to that that explain things relevant for the project in particular.

Work in progress..

https://phabricator.kde.org/T584 <- is general Plasma developer guide.

Working on ISO image right now.. :-)

That's hilarious. I'm on Tumbleweed as well (most of my systems are either Tumbleweed or Leap, and just a few specialised ones are Gentoo). So why don't we already have it packaged in openSUSE? :D

Just for completeness: wanted to check the script, too, but I have openSUSE Leap, so yeah xD

I tried out the script on openSUSE Tumbleweed

@skadinna, you are the wiki-whisperer... Do you know if there is a document anywhere that explains how to become a full-fledged Plasma Mobile contributor? Or anything else we can use and adapt?

I tried out the script on openSUSE Tumbleweed and also noticed that the .py is missing and also got the endless SDL segfaults. I waited several minutes before I closed the window.

Regarding the part about increasing the number of contributions, we must dovetail this project with T7116. It is beyond the scope of promo to intervene in the processes by which potential contributors become actual contributors, but we cannot invite contributors to help and find there is not a protocol in place to help them become active coding members of the community.

I also think about apps that do not target Android but would fit well on mobile, e.g. KTimer. In my opinion, packaging all apps that could run on Plasma Mobile for it would help raise community's internal interest and also showcase more projects to the public.

Also any application that now is targetting Android should be there too: kstars, minuet, kalgebra, KDE Connect...

Perhaps for the camera, we could use Kamoso? It uses Kirigami and is developed by @apol, who does Discover.

@PureTryOut, after following your instructions, this what I get when running the virtual machine:

Ok, so with a lot of help from @bshah, we have the following data.

Thanks @PureTryOut ! This is very useful.