identification service , designed to unify user login to various KDE project sites. MyKDE replaced the identity.kde.org single sign-on system, which was implemented as a simple PHP add-on to OpenLDAP. As a reason for creating a new service, identity.kde.org is tied to outdated technologies that prevent updates to some other KDE systems, as well as such , as a time-consuming manual process of deleting accounts, very long delays before completing registration (up to 30 seconds), inefficient group scaling, too clumsy anti-spam measures.
MyKDE in Python using Django framework and module . MySQL is used to store accounts. The MyKDE code is an offshoot of the system distributed under the GPLv3.0 license. In addition to the organization of the entrance to MyKDE, support for public profiles is also implemented, which allows, if the user wishes, to make some information about himself visible to other participants, such as his full name, avatar, list of projects and links to social networks and a personal website.
Currently, the MyKDE identity system can already be used to connect to the KDE Wiki and will soon be adapted to sign in to other project sites. Existing identity.kde.org accounts, as well as group association information, will be automatically migrated the first time a user logs in through MyKDE. Registration of new accounts is disabled for the duration of the migration, but a user can register on the old identity.kde.org site and will be migrated when logging in with MyKDE. After the end of the migration period, non-migrated accounts will be frozen.
Additionally, it can be noted an optional mechanism that allows you to run the KDE Plasma desktop using systemd. It is noted that the use of systemd allows you to solve problems with setting up the startup process - the standard initialization script includes rigidly defined operation parameters that do not allow variation. For example, there is no way to start krunner with different environment variables, control system resource allocation, add a custom script to run on shell restart, or display the initial configuration dialog after kwin is loaded but before Plasma is started. The current script requires code editing for any such change, and systemd provides ready-made tools for customization for both distribution developers and end users.
Target file prepared to run under systemd
plasma-workspace.target and a set of services to run various KDE subsystems. Support for the old autostart mechanism (/etc/xdg/autostart or ~/.config/autostart) has been retained unchanged, thanks to the use of the automatic service generation mechanism introduced in (based on the .desktop files, the corresponding systemd services are automatically created). The implemented code is planned to be included in the KDE Plasma 5.21 release. By default, the old script will be saved, but in the future, after testing and analyzing reviews, it will not be excluded from its activation by default. To switch to systemd-based startup and view the boot status, you can use the commands:
kwriteconfig5 --file startkderc --group General --key systemdBoot true
systemctl --user status plasma-plasmashell.service
Source: opennet.ru