In T8871#173056, @ndavis wrote:

There's no pattern behind the choice to tie the 2 together other than the desire to put everything on one level. They mostly have no relation to each other except that the emoticons KCM lets you choose a set of images.

Hmm, you seem to put emoticons to icons, too, so what's the difference?

In T8871#173043, @ngraham wrote:

Are you proposing merging the three Application-specific KCMs into one though?

Window decorations I separated; for Qt and GTK I'm not sure, it feels like they can be merged (on my 15'' screen most space's taken by stretched combo boxes).

What about the Emoticons KCM? It's pretty useless, but still where should it go?

I think it can become a tab in icons, we have 2 tabs there anyway

And moving Font management somewhere else?

Oh, font management I've missed... Maybe having 2 KCMs inside "Fonts" as we have now is ok... Or it could be a tab in Fonts since font configuration and font management is essentially the same... Not sure how far we can go with tabs though, and whether this will have to be reconsidered on phones.

In T8871#173017, @ndavis wrote:

Another con is that a single level means a lot of used up, unscrollable, horizontal space in Icon View.

Icon view is not supposed to be horizontally scrollable, but it can move icons to next row when necessary.

In sidebar view, it's not as bad because it's scrollable, but it would still take up a lot of vertical space.

My suggestion was (supported by @rooty):

Appearance
- Theme
- Plasma
- Applications
- Window Decorations
- Splash Screen
- Icons
- Cursors
- Colors
- Fonts

Pros: one-level structure, to me, gives a lot more clarity than nested menus (like Applications -> Application Theme). Putting Applications as opposed to Workspace, and then separating Colors even further aside would personally confuse me if I were exploring the Settings.
Also, I think it'd be a positive change for Plasma Mobile, as mobile users will have real trouble understanding theming as we have it now.
Hopefully, it'll also be easier to choose icons for these sections, as we currently have some weird matches (e.g. Application Style — LnF / "Global" theme).

FWIW I disagree in that the values are hardcoded; Qt uses device-independent pixels, so it's a problem of Plasma Mobile's scaling, not dialer's code.

I personally like single click so much that it's basically annoying me when I hear someone double-clicking with a mouse loudly nearby :)

Closed by 8691651c1f0d09430416ba5fe2130647554b06a9

I have been working on Halium and Plasma Mobile Debian packages for more than a year now, mostly building and testing things. I have been helping to promote Plasma Mobile in social networks, then presented at a conference in St Petersburg. I've just finished working on KDE Russia's website and switched to Kaidan, a Kirigami XMPP messenger, in hope to improve my programming skills to participate in development.

I'm not sure... You can try building a Kirigami application that uses Kirigami as a qmake submodule, like Kaidan.

Indeed, thanks @alexeymin!

Black navigation links lack contrast on blue background, consider adding:

#kHeaderNav .nav-link.active {
  color: #fff;
}

Also, a typo in the footer: KDE © a the K Desktop Environment

Your help would be appreciated.

The website has been moved: https://cgit.kde.org/sysadmin/dns.git/commit/?id=edcfb7cf97cf1c851a3734c44a65372ddbb1a1e1

I think this line's goal is not really to separate the title bar from window content, but instead to make the transition smoother and emphasize style consistency.

I'll be that one person here who likes the separator and notices it easily on the Breeze theme.

Hello! :)
Indeed it was. You might like what the Plasma Mobile project came up with: https://www.plasma-mobile.org/findyourway/

The website has been reviewed by KDE VDG and Promo, no important issues were found, so there are no objections against moving forward with the transition.

Some small fixes for day 2 of beta:
https://cgit.kde.org/scratch/ilyabizyaev/kde-ru.git/diff/?id2=6d52111d013a9428591da10bd17a8c69988777bd&id=a5d9dfd212d20631cd394b0aaf27dfe4cf2f80f8

Applied day 1 fixes
https://cgit.kde.org/scratch/ilyabizyaev/kde-ru.git/commit/?id=6d52111d013a9428591da10bd17a8c69988777bd

Russian-speaking community progress:

• Increased subscriber count by 40% (374 people)
• Created a chat to facilitate involvement, ~180 participants at the moment
• Translated most of the news from official accounts and Planet this year, as well as Plasma and Applications announcements
• A new website, kde.ru, is currently in development. It is planned to shut down the old forum and wiki in favor of the new chat and https://community.kde.org/RU

It's not quite clear when the announcement should happen, so I started to write social media messages. @cfeck Could you remove the embargo?

I think I've finished writing the announcement at https://notes.kde.org/p/_applications_18.08.0_announcement, but it needs to be verified by someone more experienced.

The most visible performance pitfall is in non-Qt XWayland apps, e.g. Chromium. They are mostly built with desktop OpenGL, so they fall back to software rendering. I also think some X components use software rendering where normally things are accelerated, but I haven't researched yet.

Here are the resources you may need:

Hello and welcome :)

That sounds like a good plan for the future, but currently, the functionality is split. Koversation provides IRC and Matrix capabilities, Kaidan is used for XMPP, Telegram is supported by the official app, and there is a basic app for telephony.

I think for photos, we already have a basic gallery. Vvave can be used as a music player.
For the rest, tasks seem to exist already: https://phabricator.kde.org/project/view/28/

An amazing addition would be to also help make use of additional device buttons (e.g. physical home and Bixby buttons on Samsung phones, virtual back-home-recent keys on ASUS, Alcatel and other devices).

A related project might be Prison, which is a KDE Framework for barcode generation.

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

Another website like that is https://whatcanidoformozilla.org

...and name stylisation/pronunciation :D

I'm not sure if that is a related issue, but it would be nice if the keyboard also did not overlap the bottom panel (if any). On Plasma Mobile, that's a matter of basic UI navigation.

At the moment, the group I suit best is probably "Pen-pushing writers / editors / proofreaders", as I localize community news for Russia (and write some myself). I also plan to produce a number of blogposts soon as I get to a more stable point with Plasma Mobile.

Ok, assuming it can be made a menu later if the button fails, I'm good to move on :)

My personal favorite here is Mozilla; I think they've done the download banner just right:

As I suggested in the chat, we could use the experience of other projects and make it a button, not a menu.

@paulb Yes, probably to "Community". And I would reorder "KDE e.v." and "Community" in "About".

Another link to have is to a page with international websites (currently it is https://www.kde.org/support/international.php).

Outdated, was superceded by D3591.

Merged by 389f4c29acc3.

I understand what you mean, but my comments to colors and the label still apply (a nice-looking store / desktop icon and a pretty label in "About" menu would be nice to have).

Is it a requirement for the letters to be all uppercase? That moves visual focus away from the logo... On @januz mockups, the project name is in harmony with the logo.

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 :)

The recently introduced KWallet support in VLC is cool; can it also be implemented for Firefox? When a master password is set, Firefox asks for it on every launch, which for me is usually just after unlocking my Wi-Fi passwords with KWallet. If Firefox could make use of KWallet (like Chrome and Opera do), it'd be one password prompt less on every device boot :)

I see your point, I am just afraid of the opposite effect: the general structure of current settings has even more mobile in mind that the proposed one. And as there currently is not much development on that side, I am trying to not let it slip out of the way completely, as this year could well be our last chance to jump into mobile.

The mockups are nice, although there is a part I do not particularly like: all of them have a lot of empty areas, which means they are planned for big screens. By just scaling the pictures so that fonts had normal size, I get a window higher than my 15'' 16:9 laptop! :)
Also, I am concerned about those designs on mobile... Is the spacing supposed to scale? How would the 2-level drawer look on a phone? Could you picture those?

Should never become a public slogan, though 😬

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

@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.

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

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

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

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.

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

As you know, we are participating in GSoC, and ideas are being collected right now for the organization proposal.
How profitable would it be to have a student work on Plasma Mobile? Is that a way to introduce a new contributor and get more work done or extra workload for Bhushan?

Yeah, and we also probably need to ask developers fix most annoying issues there (i.e. those not present on real devices)

In a day, the post on the Russian community page has collected 300 votes.
Here are the results:

Just started a poll, it got widespread quickly. Hoping to get a lot of feedback.

I hope so... It may be not the best time for me right now, but I'll be able to get this started.

As discussed, my points here are:

• To count contributors and set realistic goals, we need to define what Plasma Mobile is. Currently, I think of it as Halium (hardware abstraction), Kirigami as UI SDK, Plasma & whole stack as DE, some entry-level apps
• To be able to attract new contributors, we need to prepare for them internally: collect open tasks from participating projects; collect information on what devices can be used for testing already; prepare instructions for deployment and emulating
• Finally, to be able to promote Plasma Mobile, we need to know its strong points. As far as I know, it is far from being a daily driver, so we probably need to mention architectural strengths, design concepts, and wide opportunities

+1 for Junior Jobs!

Closed by b0bf6b8.

Updated the revision to reflect the last commit in Kirigami

No, I don't

Turns out some files have been removed from Kirigami while I've been sending a patch xD

In T6919#110691, @paulb wrote:

Russian:

https://www.kaldata.com/телефони/​kde-и-purism-искат-да-създадат-линукс-смартфо-259440.html
https://www.kaldata.com/телефони/​kde-и-purism-искат-да-създадат-линукс-смартфо-259440.html

Oops, that's actually Bulgarian :)