I' ve tried to help newcomers to contribute to Plasma Mobile; with @bshah we tried to make phabricator tasks more complete and easier to be assigned to newcomers and, for the same purpose, I 've created the findyourway interactive guide.

Previously introduced "separator mode" removed from AbstractListItem and BasicListItem.

+1
We had a similar discussion in Akademy! Since string tags can't be added, we have to create either a group or a project.
Then, we may use the phabricator API to serve the junior jobs wherever needed. And, why not, create sth similar to the findyourway of plasmobile for KDE junior jobs in general.

It seems that I have no push rights to the website repo. How to proceed?

Ask social media followers to describe why they use KDE software using only 22 words.

Function isSeparator removed

isSeparator function has been added to ensure compatibility with QAction https://doc.qt.io/qt-5/qaction.html#isSeparator. We do not need it?

We should consider using Radio QML Type since it seems that it fits our needs.

Proof of concept repository can be found here.

Great, this was fast! Right, it would also be nice to have a mockup at Pholio, as described in T8963, to let KDE designers review it. You may also find helpful the already in progress design review task M129 (regarding plasma mobile weather app).

I am really excited to see these mockups! Good work! Although not a designer, following Kirigami HIG I would put "location search" and more important settings at the bottom of the page to facilitate one handed navigation.

Unfortunately, for new plasma mobile applications, no relative phabricator place exists for the review to take place. So, for the first reviews and before the new app code reaches KDE repository, we cannot avoid using an external code hosting provider (e.g. gitlab). It is an important issue that we will discuss at Akademy BoF. @nickre if this is not a problem for you, could you please put your code there and put the relative link here so as our devs to review it?

Well, explaining how the weather applet and -in particular- how the data engine code works is more than valuable :)

Let me kindly request for your feedback on this issue. Since @BrokenMutant has expressed his intention to contribute to plasma mobile weather app, it would be nice if we devised an approach either based on the suggestion made above or consider alternatives so as to facilitate the creation of the app :)

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

This task belongs to a series of tasks we created after a discussion with @bshah trying to offer to Plasma Mobile users the features of the existing mobile platforms. Since mobile users expect such an application, we think that offering a standalone application we will fulfill user needs and make PlaMo ecosystem more complete.

Detailed instructions to create a Plasma Mobile emulated environment with:

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

Following a discussion with @bshah about T8685, we opted for revamping Plasma Mobile phabricator tasks. The status of many tasks has been changed in order to avoid offering to the potential contributor a task already done.

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.

In T8685#141924, @aacid wrote:

The translation teams have said various times in the past that translations from random people in the internet with no commitment usually just bring in more work than they help since they totally fail at syntax, style guide, etc. I wouldn't be sure this has changed at all.

I mean would you let people edit code form the internet and submit a patch directly without having them compile and try it whatsoever? Probably not, so why would it be different for translations?

TBH, my suggestion is primarily focused on the facilitation of a really fast and simple first contribution. Like the case when we learn a new programming language, almost always we try to run a "hello world" example, without having any real knowledge of the language or having read (almost) any page of the language reference. After the successful execution of the “hello world” , we feel a little bit more comfortable to continue studying. It's the "hello world" psychological effect accompanied with the feeling of membership and commitment to the KDE family that the solution tries to reproduce .

Find below the merged version of previous comments, as requested.

26. Promotion resources are usually scarce in FOSS communities. Coordinate with FOSS communities that we share technologies or values. KDE people may promote their work and vice versa.

25. Leverage switch to smartphones as main computational device

No prob Aleix :) I ll take care of the commit in a couple of hours!

KHtml is not a dependency anymore, after commit https://cgit.kde.org/parley.git/commit/?id=38c4620041486483449a13a0237c4042c852e41d. Since it is not needed by browser widget as per QWebEngineView approach, from my viewpoint, parley may carry on without such a dependency.