https://community.kde.org/api.php?action=feedcontributions&user=Pontaos&feedformat=atomKDE Community Wiki - User contributions [en]2024-03-28T10:45:20ZUser contributionsMediaWiki 1.40.2https://community.kde.org/index.php?title=Akademy/2021/Monday&diff=92210Akademy/2021/Monday2021-06-19T05:07:10Z<p>Pontaos: /* Room 02 - 21st June */</p>
<hr />
<div>= BoF sessions on Monday, 21st June 2021 =<br />
<br />
<br />
Please put your name and email address in the Host/Notes section. There is no length limitation; text will wrap. <br />
<br />
'''KDE eV AGM'''<br />
Following on from the reports during the weekend the private part of the KDE eV AGM, for eV members only, will be held during 11:00 - 13:00 UTC in its own room.<br />
<br />
The Akademy team might reassign BoFs based on operational needs<br />
<br />
[https://community.kde.org/Akademy/2021/AllBoF Back to all BoFs]<br />
<br />
=== AGM ===<br />
{| class="table table-striped"<br />
|-<br />
! Private Room<br />
!<br />
!<br />
|-<br />
! Time<br />
! Subject<br />
! Host/Notes<br />
|-<br />
| 11:00 - 13:00 UTC<br />
| [https://ev.kde.org/generalassembly/ KDE eV AGM]<br />
| Only for KDE eV association members<br />
|}<br />
<br />
=== Room 01 - 21st June ===<br />
{| class="table table-striped"<br />
|-<br />
! [https://meet.kde.org/b/akademy-bof-1 Link to Room 1]<br />
!<br />
! <br />
|-<br />
! Time <br />
! Subject <br />
! Host/Notes<br />
|-<br />
| width="100pt" | 9:00 UTC<br />
| width="200pt" | KF6<br />
| width="400pt" | several Davids and Kévin<br />
|-<br />
| 10:00 UTC<br />
| KF6 (continued)<br />
|<br />
|-<br />
| 11:00 UTC<br />
| '''Qt for Python''' : Cross Platform application development with Qt, Qml and Python<br />
| Anupam Basak<br />
|-<br />
| 12:00 - 16:00 UTC <br />
| Break<br />
| <br />
|- <br />
| 16:00 UTC<br />
| KDE Goal: All about the apps - macOS / Homebrew platform<br />
| Yurii Kolesnykov<br />
|-<br />
| 17:00 UTC<br />
| KDE Goal: All about the apps - Linux platform<br />
| Aleix Pol<br />
|-<br />
| 18:00 UTC<br />
| KDE Goals - selecting the new Goals<br />
| Adam Szopa<br />
|-<br />
| 19:00 UTC<br />
| Prep for BoF Wrap Up<br />
| <br />
|-<br />
| 19:30 UTC<br />
| BoF Wrap Up<br />
|<br />
|}<br />
<br />
=== Room 02 - 21st June ===<br />
{| class="table table-striped"<br />
|-<br />
! [https://meet.kde.org/b/akademy-bof-2 Link to Room 2]<br />
!<br />
! <br />
|-<br />
! Time <br />
! Subject <br />
! Host/Notes<br />
|-<br />
| width="100pt" | 9:00 UTC<br />
| width="200pt" | <br />
| width="400pt" | <br />
|-<br />
| 10:00 UTC<br />
|<br />
|<br />
|-<br />
| 11:00 UTC<br />
|<br />
|<br />
|-<br />
| 12:00 - 16:00 UTC <br />
| Break<br />
| <br />
|- <br />
| 16:00 UTC<br />
| LGBTQ+ community check-in and socialization hour<br />
| Host: Torrie Fischer <tdfischer@kde.org><br />
Matrix room: https://matrix.to/#/#kde-lgbt:kde.org?via=libera.chat&via=kde.org<br />
<br />
Come to say hi; stay for the warm fuzzies, camaraderie, and world-domination plotting.<br />
|-<br />
| 17:00 UTC<br />
| Shared chat components library<br />
| Janet Blackquill <uhhadd@gmail.com>; reduce duplication in KDE's chat apps using a shared library<br />
|-<br />
| 18:00 UTC<br />
| <br />
| <br />
|-<br />
| 19:00 UTC<br />
| Prep for BoF Wrap Up<br />
| <br />
|-<br />
| 19:30 UTC<br />
| BoF Wrap Up<br />
| Go to Room 1<br />
|}<br />
<br />
=== Room 03 - 21st June ===<br />
{| class="table table-striped"<br />
|-<br />
! [https://meet.kde.org/b/akademy-bof-3 Link to Room 3]<br />
!<br />
! <br />
|-<br />
! Time <br />
! Subject <br />
! Host/Notes<br />
|-<br />
| width="100pt" | 9:00 UTC<br />
| width="200pt" | <br />
| width="400pt" | <br />
|-<br />
| 10:00 UTC<br />
|<br />
|<br />
|-<br />
| 11:00 UTC<br />
|<br />
|<br />
|-<br />
| 12:00 - 16:00 UTC <br />
| Break<br />
| <br />
|- <br />
| 16:00 UTC<br />
|<br />
| <br />
|-<br />
| 17:00 UTC<br />
| <br />
| <br />
|-<br />
| 18:00 UTC<br />
| <br />
| <br />
|-<br />
| 19:00 UTC<br />
| Prep for BoF Wrap Up<br />
| <br />
|-<br />
| 19:30 UTC<br />
| BoF Wrap Up<br />
| Go to Room 1<br />
|}</div>Pontaoshttps://community.kde.org/index.php?title=Telegram&diff=91007Telegram2021-01-28T19:27:43Z<p>Pontaos: restructure and remove non-functioning links</p>
<hr />
<div>'''Telegram''' is a real-time chat program, similar to instant messages and [[Internet Relay Chat | IRC]]. Telegram offers a mobile, desktop and [https://web.telegram.org web client]. You can install the Telegram desktop client using the [https://userbase.kde.org/Discover KDE Discover Software Store] or using the command line, which differs based on which GNU/Linux distribution you're using:<br />
<br />
* Arch/Antergos/Manjaro: <code>sudo pacman -S telegram-desktop</code><br />
* Debian/Ubuntu/Kubuntu/KDE Neon: <code>sudo apt install telegram-desktop</code><br />
* Fedora: <code>sudo dnf install telegram-desktop</code><br />
* Gentoo: <code>sudo emerge telegram-desktop-bin</code><br />
* openSUSE: <code>sudo zypper install telegram-desktop</code><br />
* Flatpak: <code>flatpak install flathub org.telegram.desktop</code><br />
<br />
==Design Groups==<br />
<br />
* KDE Visual Design Group: https://t.me/vdgmainroom<br />
<br />
==Development Groups==<br />
<br />
* KDE Development: https://t.me/kdedevel<br />
* KDE Rust: https://t.me/kderust<br />
* KDE Craft: https://t.me/KDECraftPackager<br />
* KDE Maui: https://t.me/mauiproject<br />
* KDE Basket: https://t.me/kdebasket<br />
* KDE Kirigami: https://telegram.me/joinchat/BbOuVj6l7b5aZ_WbupyFFw<br />
* KDE Web: https://t.me/kdeweb<br />
* KDE Windows: https://t.me/KDEWindows<br />
* Plasma Mobile: https://t.me/plasmamobile<br />
* KDevelop Development: https://telegram.me/joinchat/BwCsygZhPebf8SrpG_9RpQ<br />
* Kontact: https://t.me/KDE_Kontact<br />
* WikiToLearn: https://t.me/wikitolearn<br />
<br />
==Application Groups==<br />
<br />
* Kdenlive: https://t.me/kdenlive<br />
* KEXI: https://t.me/kexi_project<br />
* Kirogi: https://t.me/kde_kirogi<br />
* Basket: https://t.me/kdebasket<br />
<br />
==Non-English==<br />
<br />
* KDE Brazil (KDE Brasil): https://t.me/kdebrasil<br />
** KDE Brasil Desenvolvimento: https://t.me/KdeBrasilDesenvolvmiento<br />
** Komunidade: https://t.me/komunidade<br />
** Krita Brasil: https://t.me/kritabraasil<br />
* KDE Spanish: https://t.me/kde_canasbravas<br />
* KDE Russia (KDE Россия): https://t.me/kde_ru<br />
<br />
==Other Groups==<br />
<br />
* KDE Promo: https://t.me/joinchat/AEyx-0O8HKlHV7Cg7ZoSyA<br />
* KDE Sysadmin: https://t.me/KDESysadminDiscuss<br />
* KDE Soc: https://telegram.me/joinchat/A-9tjgavn9YJ2myF1aTK4A<br />
* KDE Akademy Attendees: https://t.me/KDEAkademy<br />
<br />
==Offtopic Groups==<br />
<br />
* KDE Chat: https://t.me/kdechat<br />
* KDE Werewolf: https://t.me/kdewerewolf<br />
<br />
==Plasma-using Distros==<br />
<br />
===Kubuntu===<br />
* Support: https://t.me/kubuntu_support<br />
* Spanish: https://t.me/kubuntues<br />
* Brasil: https://t.me/kubuntubrasil<br />
<br />
===Neon===<br />
* General: https://t.me/kdeneon<br />
* Brasil: https://t.me/kdeneonbrasil<br />
<br />
===openSUSE===<br />
* General: https://t.me/openSUSE_Group<br />
* Español: https://t.me/openSUSE_ES<br />
<br />
==Channels==<br />
<br />
* All KDE Commits: https://t.me/kdecommits<br />
* Plasma Commits: https://t.me/kdeplasmacommits<br />
* Wayland-related Commits: https://t.me/kdewaylandcommits<br />
* Planet KDE: https://t.me/kdeplanet<br />
* KDE Sysadmin Notifications https://t.me/KDESysadmin<br />
<br />
==Community Channels==<br />
<br />
* KDE users group: @kdeplasma</div>Pontaoshttps://community.kde.org/index.php?title=Telegram&diff=90986Telegram2021-01-27T19:33:03Z<p>Pontaos: </p>
<hr />
<div>'''Telegram''' is a real-time chat program, similar to instant messages and [[Internet Relay Chat | IRC]]. Telegram offers a mobile, desktop and [https://web.telegram.org web client]. You can install the Telegram desktop client using the [https://userbase.kde.org/Discover KDE Discover Software Store] or using the command line, which differs based on which GNU/Linux distribution you're using:<br />
<br />
* Arch/Antergos/Manjaro: <code>sudo pacman -S telegram-desktop</code><br />
* Debian/Ubuntu/Kubuntu/KDE Neon: <code>sudo apt install telegram-desktop</code><br />
* Fedora: <code>sudo dnf install telegram-desktop</code><br />
* Gentoo: <code>sudo emerge telegram-desktop-bin</code><br />
* openSUSE: <code>sudo zypper install telegram-desktop</code><br />
* Flatpak: <code>flatpak install flathub org.telegram.desktop</code><br />
<br />
An active directory of KDE-related Telegram channels is maintained on Telegram at https://t.me/kdechannels. Contact https://t.me/kdechat to add entries to the listing. None of these are officially KDE channels, as KDE does not officially use proprietary communication mediums. Instead, check out KDE Matrix at https://webchat.kde.org or [https://userbase.kde.org/IRC_Channels KDE's presence on Freenode (IRC)].<br />
<br />
Note that a lot of Telegram channels have IRC or Matrix rooms that are bridged to, especially if ran by KDE developers. These channels will typically note so in their descriptions.</div>Pontaoshttps://community.kde.org/index.php?title=Telegram&diff=90985Telegram2021-01-27T19:17:20Z<p>Pontaos: </p>
<hr />
<div>'''Telegram''' is a real-time chat program, similar to instant messages and [[Internet Relay Chat | IRC]]. Telegram offers a mobile, desktop and [https://web.telegram.org web client]. You can install the Telegram desktop client using the [https://userbase.kde.org/Discover KDE Discover Software Store] or using the command line, which differs based on which GNU/Linux distribution you're using:<br />
<br />
* Arch/Antergos/Manjaro: <code>sudo pacman -S telegram-desktop</code><br />
* Debian/Ubuntu/Kubuntu/KDE Neon: <code>sudo apt install telegram-desktop</code><br />
* Fedora: <code>sudo dnf install telegram-desktop</code><br />
* Gentoo: <code>sudo emerge telegram-desktop-bin</code><br />
* openSUSE: <code>sudo zypper install telegram-desktop</code><br />
* Flatpak: <code>flatpak install flathub org.telegram.desktop</code><br />
<br />
An active directory of KDE-related Telegram channels is maintained on Telegram at https://t.me/kdechannels. Contact https://t.me/kdechat to add entries to the listing. None of these are officially KDE channels, as KDE does not officially use proprietary communication mediums. Instead, check out KDE Matrix at https://webchat.kde.org or KDE's presence on Freenode (IRC).<br />
<br />
Note that a lot of Telegram channels have IRC or Matrix rooms that are bridged to, especially if ran by KDE developers. These channels will typically note so in their descriptions.</div>Pontaoshttps://community.kde.org/index.php?title=Telegram&diff=90984Telegram2021-01-27T19:16:24Z<p>Pontaos: point to t.me/kdechannels which has an actively maintained directory of still-active groups</p>
<hr />
<div>'''Telegram''' is a real-time chat program, similar to instant messages and [[Internet Relay Chat | IRC]]. Telegram offers a mobile, desktop and [https://web.telegram.org web client]. You can install the Telegram desktop client using the [https://userbase.kde.org/Discover KDE Discover Software Store] or using the command line, which differs based on which GNU/Linux distribution you're using:<br />
<br />
* Arch/Antergos/Manjaro: <code>sudo pacman -S telegram-desktop</code><br />
* Debian/Ubuntu/Kubuntu/KDE Neon: <code>sudo apt install telegram-desktop</code><br />
* Fedora: <code>sudo dnf install telegram-desktop</code><br />
* Gentoo: <code>sudo emerge telegram-desktop-bin</code><br />
* openSUSE: <code>sudo zypper install telegram-desktop</code><br />
* Flatpak: <code>flatpak install flathub org.telegram.desktop</code><br />
<br />
An active directory of KDE-related Telegram channels is maintained on Telegram at https://t.me/kdechannels. Contact https://t.me/kdechat to add entries to the listing.<br />
<br />
Note that a lot of Telegram channels have IRC or Matrix rooms that are bridged to, especially if ran by KDE developers. These channels will typically note so in their descriptions.</div>Pontaoshttps://community.kde.org/index.php?title=Plasma/Environment_Variables&diff=90952Plasma/Environment Variables2021-01-22T21:09:21Z<p>Pontaos: /* PLASMA_ENABLE_QML_DEBUG */</p>
<hr />
<div>= Available Environment Variables =<br />
Plasmashell supports a number of environment variables to overwrite some settings or checks. The following variables are supported:<br />
<br />
=DEBUGGING=<br />
<br />
==PLASMA_TRACK_STARTUP==<br />
Tracks startup time in a log file in /tmp<br />
<br />
==PLASMA_PRELOAD_POLICY==<br />
whether we want to preload the popups of all plasmoids in the session<br />
can have 3 values (case insensitive)<br />
* "none": never preload popups<br />
* "adaptive": preload popups of most frequently used plasmoids<br />
* "aggressive" preload popups of every plasmoid<br />
<br />
==PLASMA_ENABLE_QML_DEBUG==<br />
'''(Since Plasma 5.19'<br />
<br />
Enables various debugging features:<br />
<br />
* QQmlDebuggingEnabler (see Qt docs for how to connect to Plasma)<br />
* Expanded error information when an applet fails to load<br />
<br />
==KDE_NO_GLOBAL_MENU==<br />
''(since Plasma 5.11)''<br />
<br />
Disable global menu, even if it is enabled in settings. This only affects Qt-based applications using Plasma-Integration.<br />
<br />
It can be useful to disable global menu for individual applications that have issues with global menu support (please do file bug reports about this to either the application or global menu in plasmashell!).<br />
<br />
<code>KDE_NO_GLOBAL_MENU=1 kwrite</code><br />
<br />
You can disable global menu for all application in System Settings → Application Appearance → Widget Style → "Fine Tuning" tab.</div>Pontaoshttps://community.kde.org/index.php?title=Plasma/Environment_Variables&diff=90951Plasma/Environment Variables2021-01-22T21:07:51Z<p>Pontaos: /* PLASMA_ENABLE_QML_DEBUG */</p>
<hr />
<div>= Available Environment Variables =<br />
Plasmashell supports a number of environment variables to overwrite some settings or checks. The following variables are supported:<br />
<br />
=DEBUGGING=<br />
<br />
==PLASMA_TRACK_STARTUP==<br />
Tracks startup time in a log file in /tmp<br />
<br />
==PLASMA_PRELOAD_POLICY==<br />
whether we want to preload the popups of all plasmoids in the session<br />
can have 3 values (case insensitive)<br />
* "none": never preload popups<br />
* "adaptive": preload popups of most frequently used plasmoids<br />
* "aggressive" preload popups of every plasmoid<br />
<br />
==PLASMA_ENABLE_QML_DEBUG==<br />
'''(Since Plasma 5.19'<br />
<br />
Enables various debugging features:<br />
<br />
- QQmlDebuggingEnabler (see Qt docs for how to connect to Plasma)<br />
- Expanded error information when an applet fails to load<br />
<br />
==KDE_NO_GLOBAL_MENU==<br />
''(since Plasma 5.11)''<br />
<br />
Disable global menu, even if it is enabled in settings. This only affects Qt-based applications using Plasma-Integration.<br />
<br />
It can be useful to disable global menu for individual applications that have issues with global menu support (please do file bug reports about this to either the application or global menu in plasmashell!).<br />
<br />
<code>KDE_NO_GLOBAL_MENU=1 kwrite</code><br />
<br />
You can disable global menu for all application in System Settings → Application Appearance → Widget Style → "Fine Tuning" tab.</div>Pontaoshttps://community.kde.org/index.php?title=Infrastructure/GitLab&diff=89275Infrastructure/GitLab2020-07-29T22:49:30Z<p>Pontaos: Add tip with git push options</p>
<hr />
<div>KDE uses a GitLab instance at https://invent.kde.org for code review (as well as hosting and other important collaboration tasks). This page is intended to serve as a general-purpose introduction to the most important aspects: submitting and reviewing Merge Requests.<br />
<br />
{{Info|The KDE community does not generally use GitLab for bug reporting. Please continue to submit bug reports on https://bugs.kde.org. Task management is transitioning to Invent/GitLab but most projects still use https://phabricator.kde.org for now.}}<br />
<br />
<br />
= Workflow =<br />
The sanest and easiest way to submit code to KDE is by following a typical '''feature branch workflow''': keep your master branch synchronized with the origin repository, and make all changes on separate branches. '''Each Merge Request needs its own private, temporary branch.''' Once your Merge Request has been merged, delete the feature branch, and make another new branch for the next Merge Request. In this way, you can be working on multiple changes at once without them colliding with one another because each one lives on its own branch.<br />
<br />
<br />
= Logging in =<br />
Navigate to https://invent.kde.org/users/sign_in and log in using the username and password for your KDE Identity account. If you don't have one, you can [https://identity.kde.org/index.php?r=registration/index sign up for one here].<br />
<br />
== Setting up git ==<br />
<br />
You will need to set up git to use you account details to help identify your work: <br />
<br />
<syntaxhighlight lang="bash"><br />
git config user.name <Your Real Name><br />
git config user.email <Your identity.kde.org email><br />
</syntaxhighlight><br />
<br />
(You can set it up globally with --global)<br />
<br />
= Submitting a merge request =<br />
Contributing to KDE code using GitLab involves '''submitting a Merge Request'''. A Merge Request is a request to merge some of your code into the project's permanent source code repo. Here's how:<br />
<br />
== Build the project from source and make your change ==<br />
First you need to check out the project, compile it from source, and make some changes that you would like to submit to KDE! Instructions for doing this can be found at [[Get Involved/development]]. You will wind up with a checkout of the project at <tt>~/kde/src/[the project name]</tt> with some local changes applied to it.<br />
<br />
{{Info|If you prefer a different organizational structure for source code on your machine, you can of course check out the local copy of your KDE repos wherever you want. However for the purposes of this documentation, we will assume that they are located inside <tt>~/kde/src/</tt>}}<br />
<br />
== Fork the project ==<br />
Once you have made some local changes that you would like to submit to KDE, you need to create a personal fork of the project and push your changes to the forked copy.<br />
<br />
Navigate to https://invent.kde.org/kde and locate the project. If it is not visible in the list, you can use the search field. Once you find the project, click on it:<br />
<br />
[[File:Find_the_project.png|600px]]<br />
<br />
On the project's page, click on the "Fork" button in the top-right corner of the screen:<br />
<br />
[[File:Click_the_Fork_button.png|300px]]<br />
<br />
This will take you to a page asking you what namespace you want to create the project under. Click on yourself: <br />
<br />
[[File:Choose_the_fork_namespace.png|400px]]<br />
<br />
After a moment, the system will finish creating the fork and take you to the page for your fork. On that page, click on the blue "Clone" button in the top-right corner:<br />
<br />
[[File:Click_the_Clone_button.png|300px]]<br />
<br />
In the pop-up that appears, click on the "copy" button to the right of the upper text field. This will copy the URL for the fork onto your clipboard.<br />
<br />
[[File:Copy_the_URL.png|300px]]<br />
<br />
== Add the fork to your source checkout ==<br />
Next, open your terminal app and navigate to the location where the project's repo lives (i.e. <tt>~/kde/src/[the project name]</tt>).<br />
<br />
You need to add your fork as a '''remote''' to the existing repo:<br />
<br />
{{Input|1=<nowiki><br />
git remote add fork [the URL you copied to your clipboard]<br />
</nowiki>}}<br />
<br />
Run <tt>git remote -v</tt>. You should see something like this:<br />
<br />
<pre><br />
$ git remote -v<br />
fork git@invent.kde.org:ngraham/kid3.git (fetch)<br />
fork git@invent.kde.org:ngraham/kid3.git (push)<br />
origin https://invent.kde.org/kde/kid3.git (fetch)<br />
origin https://invent.kde.org/kde/kid3.git (push)<br />
</pre><br />
<br />
This means you have two remotes set up for your repo: "origin" points to the original repo, and "fork" points to your fork of it.<br />
<br />
== Make a branch and commit ==<br />
Now that you have your fork set up, it's time to create a branch to track your work and make a commit.<br />
<br />
{{Input|1=<nowiki><br />
git checkout -b my_awesome_feature<br />
git add [the files you changed]<br />
git commit<br />
</nowiki>}}<br />
<br />
== Write a good commit message ==<br />
With Gitlab, once a merge request is merged, the first commit in the merge request will wind up in the Git history, so it is very important that the first commit in the merge request be formatted properly.<br />
<br />
Please follow [https://chris.beams.io/posts/git-commit/#seven-rules commit message best practices]: write a descriptive title in the form of an imperative sentence (e.g. "Fix button disappearing when view is changed") and on the next line, write at least one sentence describing your change and why it is necessary, adding more details if necessary.<br />
<br />
If your patch is intended to fix a Bugzilla ticket, include the following on its own line:<br />
<pre><br />
BUG: 385942<br />
</pre><br />
(The number should be just the Bugzilla ticket number, '''not the full URL''')<br />
<br />
[https://community.kde.org/Policies/Commit_Policy#Special_keywords_in_GIT_and_SVN_log_messages Here is more information] about other special messages that interact with Bugzilla tickets.<br />
<br />
{{Note|These keywords will only work if the email address in your <tt>~/.config/git/config</tt> file matches the email address used for your https://bugs.kde.org account (See [https://techbase.kde.org/Development/Git/Configuration#Basic_Settings this page] for more information).}}<br />
<br />
{{Note|If a merge request has only a single commit in it, then this commit will be added to the immutable git history with no opportunity to change it from the web interface before merging. This is different from Phabricator, in which the patch's title and summary are transformed into a commit message, overwriting the underlying commit message itself. So it is very important to format your commit message well. The web interface can only be used to rewrite a commit message when a merge request has at least two commits, and they are squashed when merging, and the person doing the merging writes a new commit message in the process of squashing.}}<br />
<br />
== Push to your fork ==<br />
At this point you have a branch in your local repo called "my_awesome_feature" (Hopefully in reality it is named something a bit more appropriate!) that has a commit on it with your work. Now push it to your fork:<br />
<br />
{{Input|1=<nowiki><br />
git push fork my_awesome_feature<br />
</nowiki>}}<br />
<br />
This will produce a message somewhat like this:<br />
<br />
<pre><br />
$ git push fork my_awesome_feature<br />
Enumerating objects: 5, done.<br />
Counting objects: 100% (5/5), done.<br />
Delta compression using up to 4 threads<br />
Compressing objects: 100% (3/3), done.<br />
Writing objects: 100% (3/3), 303 bytes | 303.00 KiB/s, done.<br />
Total 3 (delta 2), reused 0 (delta 0)<br />
remote: This commit is available for viewing at:<br />
remote: https://invent.kde.org/ngraham/kid3/commit/23a702439f494806cf3cfe14f212df58a0075bba<br />
remote: <br />
remote: To create a merge request for my_awesome_feature, visit:<br />
remote: https://invent.kde.org/ngraham/kid3/merge_requests/new?merge_request%5Bsource_branch%5D=my_awesome_feature<br />
remote: <br />
To invent.kde.org:ngraham/kid3.git<br />
* [new branch] my_awesome_feature -> my_awesome_feature<br />
</pre><br />
<br />
Tip: If you want to open a merge request immediately, add <pre>-o merge_request.create -o merge_request.target=[target branch here]</pre> to the git push command.<br />
<br />
== Create the Merge Request ==<br />
Notice the "To create a merge request for my_awesome_feature..." message in the output of the push command (explained in the previous section). You can copy-and-paste the URL shown below it into a web browser. On some terminal apps, such as Konsole and Yakuake, you can ctrl+click on the link to go right there!<br />
<br />
You will be taken to a web page that looks like this:<br />
<br />
[[File:Merge_Request_info.png|800px]]<br />
<br />
In the Description section, write at least one sentence describing your change and why it is necessary, adding more details if needed. For Merge Requests that change something about the appearance or user interface, it's customary to include a screenshot of how the interface looks after your change has been applied. Bonus points for including a "Before" image too, so reviewers can easily compare them.<br />
<br />
If your patch is intended to fix a Bugzilla ticket, include the ticket number at the bottom of the description as follows:<br />
<pre><br />
BUG: 385942<br />
</pre><br />
As soon as the Merge Request is created, the Bugzilla ticket is notified that a relevant Merge Request has been started.<br />
<br />
{{Note|The <code>BUG:</code> keyword must be added both in the Merge Request description, to notify the bug ticket of the Merge Request creation, and in the message of the first commit (as explained in [[Infrastructure/GitLab#Write_a_good_commit_message]]), to close the bug ticket once the Merge Request is merged.}}<br />
<br />
In the section below, it is very important that you make sure all three checkboxes are checked:<br />
<br />
[[File:Check_all_checkboxes!.png|500px]]<br />
<br />
Once you're done with that, click the "Submit Merge Request" button!<br />
<br />
[[File:Submit_Merge_Request.png|400px]]<br />
<br />
== What happens next? ==<br />
After you've submitted your Merge Request, KDE developers who work with the software in question will review it and provide feedback. This can often take a few days. However, if nobody has responded after a week, it's likely that the review was overlooked (sorry about that!) and it's appropriate to make a comment saying, "Ping!" or something to that effect.<br />
<br />
Once the Merge Request is accepted, KDE Developers will merge it for you!<br />
<br />
== Making changes to a Merge Request ==<br />
Oftentimes, reviewers will request changes before the Merge Request can be merged. To accomplish this, you make the requested changes locally, then create a new commit including your changes. First, stage all changed files:<br />
<br />
{{Input|1=<nowiki><br />
git add -u<br />
</nowiki>}}<br />
<br />
Now make a new commit with the staged files:<br />
<br />
{{Input|1=<nowiki><br />
git commit<br />
</nowiki>}}<br />
<br />
Then push the local branch with the new commit on it up to the remote branch:<br />
{{Input|1=<nowiki><br />
git push fork<br />
</nowiki>}}<br />
<br />
== Rebasing a Merge Request ==<br />
When other changes have been made to the project's source code repo since you submitted your merge request, you will need to ''rebase'' the Merge Request to incorporate those changes. Here's how you do so:<br />
<br />
{{Input|1=<nowiki><br />
# First, make sure you are on the branch for your merge request<br />
git fetch<br />
git pull --rebase origin master<br />
</nowiki>}}<br />
<br />
At this point, there may be merge conflicts. If there are, git will tell you which files have conflicts. Open each file and resolve the conflict by exiting the contents to keep only the appropriate change. Then run <tt>git add [file path]</tt> on each conflicted file once all the conflicts have been resolved.<br />
<br />
Now, you need to overwrite the version of the Merge Request on your remote branch with the version on your local branch. To do this, you have to force-push:<br />
<br />
{{Input|1=<nowiki><br />
git push --force fork<br />
</nowiki>}}<br />
<br />
<br />
= Testing someone else's Merge Request =<br />
First you'll need a development environment set up. If you haven't done that yet, it's time to do so. Follow the instructions on [[Get_Involved/development#Set_up_your_development_environment]]. It is also advisable to set up the <tt>git mr</tt> tool, which makes testing Merge Requests a breeze. Here's how to install it, depending on your operating system:<br />
<br />
''' Arch / Manjaro '''<br />
{{Input|1=<nowiki><br />
yay -S git-mr<br />
</nowiki>}}<br />
<br />
'''Debian/Ubuntu/KDE Neon'''<br />
{{Input|1=<nowiki><br />
sudo apt install git-extras<br />
</nowiki>}}<br />
<br />
''' Fedora '''<br />
{{Input|1=<nowiki><br />
sudo dnf install git-extras<br />
</nowiki>}}<br />
<br />
''' OpenSUSE '''<br />
{{Input|1=<nowiki><br />
sudo zypper install git-mr<br />
</nowiki>}}<br />
<br />
== Check out the Merge Request and compile the software ==<br />
First check out or enter the source repository for the software that's being patched. For example, let's say you want to test a Merge Request for Okular. If you've never built it before, check it out and build it once first:<br />
{{Input|1=<nowiki><br />
kdesrc-build okular<br />
</nowiki>}}<br />
<br />
Now go to its source directory:<br />
{{Input|1=<nowiki><br />
cd ~/kde/src/okular<br />
</nowiki>}}<br />
<br />
Find the Merge Request's ID. For example, for https://invent.kde.org/kde/okular/merge_requests/80, the ID is <tt>80</tt>.<br />
<br />
...and apply the Merge Request:<br />
{{Input|1=<nowiki><br />
git mr 80<br />
</nowiki>}}<br />
<br />
Now it's time to compile and run the software to make sure that the Merge Request does what it says it does and doesn't cause any regressions! Compile the patched source code:<br />
{{Input|1=<nowiki><br />
kdesrc-build okular --no-src --resume-from okular<br />
</nowiki>}}<br />
Those arguments will tell <tt>kdesrc-build</tt> to not update the source code and to not build any dependencies.<br />
<br />
If it didn't compile, that's reason alone to reject the Merge Request! Go to the web page for the Merge Request and report your findings.<br />
<br />
== Perform QA ==<br />
If it did compile, then it's time to perform QA, because it's important to thoroughly test Merge Requests to ensure that bad code and regressions don't slip in. '''This is the entire purpose of having a review infrastructure'''; it is very important.<br />
<br />
First make sure the unit tests all pass:<br />
{{Input|1=<nowiki><br />
cd ~kde/build/kde/applications/okular<br />
ctest<br />
</nowiki>}}<br />
<br />
If any tests fail, report this through a comment on the Merge Request's web page.<br />
<br />
Does everything all still work for you? If not, return to the web page and request changes, writing a detailed comment explaining what didn't work. It is permissible to do this even if you have not been specified as a reviewer! '''Anyone can reject a Merge Request on the grounds that it does not work, does not do what it says it does, or causes regressions.'''<br />
<br />
Next, try to break the Merge Request. Here are some ideas:<br />
# Remove the program's configuration file (<tt>~/.config/<program name>rc</tt> ) and re-open it<br />
# Try the program with a HiDPI scale factor (or without one) or with a different default font size<br />
# If it's a new feature, feed it unexpected input<br />
# Test related functionality<br />
<br />
A good Merge Request will handle corner cases and variations in configuration. The price of configurability is vigilant testing! We owe it to our users to test using many configurations, not just the defaults or our personal settings.<br />
<br />
== Perform code review ==<br />
{{Note|1= Need a section on code review here, preferably written by a core KDE developer or another very experienced developer}}<br />
<br />
== Engage with the author and other reviewers ==<br />
After you have run the program and evaluated the Merge Request, it's time to leave some review comments on the webpage. If you have been specified as a reviewer, or are a member of a group that has been specified as a reviewer, it is permissible to Accept the Merge Request. But keep in mind that reviewing involves responsibility: you are giving a thumbs-up to code that will be run potentially by millions of people. If you accept and land a Merge Request that causes regressions, you will be expected to help fix it if the original author cannot or has disappeared. It's important to take the reviewer role seriously.<br />
<br />
== Make sure the target branch is set correctly ==<br />
When the "Merge" button is clicked, the Merge Request will be landed on the target branch. If the target branch is not correct, or reviewers have decided that it should be landed on a different branch (for example, perhaps the change is a low-risk bugfix suitable for landing on the stable branch), then the target branch must be changed before merging. To do this, edit the merge request by clicking the "Edit" button in the top-right corner of the page and choose a different target branch:<br />
<br />
[[File:Editing_merge_request_target_branch.png]]<br />
<br />
If this results in conflicts, then pull down the remote branch, rebase it locally, and push to the remote branch.<br />
<br />
Note that after committing to the stable branch you are expected to merge that branch to <tt>master</tt> afterwards:<br />
{{Input|1=<nowiki><br />
git checkout release/19.12<br />
git pull<br />
git checkout master<br />
git pull<br />
git merge -s recursive -Xours release/19.12<br />
git push<br />
</nowiki>}}<br />
<br />
{{warning|If at any time you feel nervous or run into trouble, ask your reviewers for help. This can be tricky, and undoing bad merges is a pain in the neck.}}<br />
<br />
= Pushing commits to somebody else's fork =<br />
Sometimes someone will say "hey let's work on my branch together." So you will be pushing commits not to origin, and not to your fork, but to someone else's fork. Let's say you want to work on joliveira's "gsoc2019_numberFormat" branch.<br />
<br />
First you would need to add the URL for his fork as a remote:<br />
<br />
<pre><br />
$ cd ~/kde/src/okular<br />
$ git remote add joliveira_fork git@invent.kde.org:joliveira/okular.git<br />
$ git remote -v<br />
aacid_fork git@invent.kde.org:aacid/okular.git (fetch)<br />
aacid_fork git@invent.kde.org:aacid/okular.git (push)<br />
joliveira_fork git@invent.kde.org:joliveira/okular.git (fetch)<br />
joliveira_fork git@invent.kde.org:joliveira/okular.git (push)<br />
origin https://invent.kde.org/kde/okular.git (fetch)<br />
origin https://invent.kde.org/kde/okular.git (push)<br />
</pre><br />
<br />
Notice how there are now multiple forks set up as remotes.<br />
<br />
Next, you need to fetch all the repo metadata from the new remote:<br />
<br />
{{Input|1=<nowiki><br />
git fetch joliveira_fork<br />
</nowiki>}}<br />
<br />
This will download the list of branches. The next step is to switch to the one you want to collaborate on:<br />
<br />
{{Input|1=<nowiki><br />
git checkout --track joliveira_fork/gsoc2019_numberFormat<br />
</nowiki>}}<br />
<br />
This will create a local branch named "gsoc2019_numberFormat" from the contents of the remote branch joliveira_fork/gsoc2019_numberFormat and that also "tracks" it. This means that if someone else pushes changes to a remote version of that branch, you can run <tt>git pull --rebase</tt> while on your local "gsoc2019_numberFormat" branch to bring it up to date.<br />
<br />
Next, make your changes, add and commit. Then push the changes to the remote joliveira_fork remote:<br />
<br />
{{Input|1=<nowiki><br />
git push joliveira_fork gsoc2019_numberFormat<br />
</nowiki>}}<br />
<br />
= Generating "eternal" URLs to commits or objects in a repository =<br />
<br />
History has taught that no system used by KDE around the code repositories stays forever.<br />
Quickgit, CGit, Phabricator & Co. came and at one point were replaced again. Sadly also taking with them the service-specific URLs (and host names).<br />
<br />
To give documentation, blog posts, commit messages and other long-living documents a way to reference commits or objects in the repository like directories or files, at given branches or at given tags, the service commits.kde.org exists. It maps and forwards URLs to the respective current service URLs.<br />
<br />
The pattern for URLs to commits is this:<br />
<pre><br />
https://commits.kde.org/<repo-id>/<commit-id><br />
</pre><br />
<br />
Example:<br />
<pre><br />
https://commits.kde.org/kcoreaddons/d2f4d353327b322ee6bfcc303169190ae44393f0<br />
</pre><br />
<br />
The pattern for URLs to objects is like this:<br />
<pre><br />
https://commits.kde.org/<repo-id>[?[path=<pathToFileOrDirectory]&[branch=<branch>|tag=<tag>]]<br />
</pre><br />
<path> should be without a leading /. It defaults to the top-level directory if not set. Either a branch or tag can be passed at which the objects should be shown. It defaults to the main branch (master usually).<br />
<br />
Examples:<br />
<pre><br />
https://commits.kde.org/kcoreaddons?path=src # points to src/ directory in master branch<br />
https://commits.kde.org/kcoreaddons?path=README.md&tag=v5.0.0 # points to README.md file at tag v5.0.0<br />
https://commits.kde.org/kdelibs?path=kdecore/tests&branch=KDE/3.5 # points to kdecore/tests directory in branch KDE/3.5<br />
</pre><br />
<br />
There currently is no service to generate commit.kde.org URLs from URLs for the actual system. This has to be done manually.</div>Pontaoshttps://community.kde.org/index.php?title=GSoD/2020/Ideas&diff=88094GSoD/2020/Ideas2020-04-22T19:15:10Z<p>Pontaos: /* Kirigami */</p>
<hr />
<div>== Guidelines ==<br />
<br />
=== Information for Technical Writers ===<br />
<br />
These ideas were contributed by our developers and users. They are sometimes vague or incomplete. If you wish to submit a proposal based on these ideas, you are urged to contact the developers and find out more about the particular suggestion you're looking at.<br />
<br />
<!-- Becoming accepted as a Google Summer of Documentation student is quite competitive. Accepted students typically have thoroughly researched the technologies of their proposed project and have been in frequent contact with potential mentors. '''Simply copying and pasting an idea here will not work.''' On the other hand, creating a completely new idea without first consulting potential mentors rarely works. --><br />
<br />
When writing your proposal or asking for help from the general KDE community don't assume people are familiar with the ideas here. KDE is really big!<br />
<br />
If there is no specific contact given you can ask questions on the general KDE development list kde-devel@kde.org and the KDE documentation list kde-doc-english@kde.org. See [https://kde.org/mailinglists/ the KDE mailing lists page] for information on available mailing lists and how to subscribe.<br />
<br />
{{Note|'''These are all proposals! We are open to new ideas you might have!!''' Do you have an awesome idea you want to work on with KDE but that is not among the ideas below? That's cool. We love that! But please do us a favor: Get in touch with a mentor early on and make sure your project is realistic and within the scope of KDE.}}<br />
<br />
__TOC__<br />
<br />
=== Adding a Proposal ===<br />
<br />
{{Note|Follow the template of other proposals!}}<br />
<br />
==== Project: ====<br />
<br />
'''If appropriate, screenshot or another image '''<br />
<br />
'''Brief explanation:'''<br />
<br />
'''Expected results:'''<br />
<br />
'''Knowledge Prerequisite:'''<br />
<br />
'''Mentor:'''<br />
<br />
When adding an idea to this section, please try to include the following data:<br />
<br />
:*if the application is not widely known, a description of what it does and where its code lives<br />
:*a brief explanation<br />
:*the expected results<br />
:*pre-requisites for working on your project<br />
:*if applicable, links to more information or discussions<br />
:*mailing list or IRC channel for your application/library/module<br />
:*your name and email address for contact (if you're willing to be a mentor) <br />
<br />
'''Ideas with no mentors listed and their contact info will be removed'''<br />
<br />
{{Note|The GSoD documtation has a section about [https://developers.google.com/season-of-docs/docs/project-ideas Project ideas].}}<br />
<br />
==Ideas==<br />
<br />
=== Kirigami ===<br />
<br />
Improving the accuracy, English, and examples of the Kirigami documentation will be useful for all developers seeking to use Kirigami in their applications.<br />
<br />
Prerequisite knowledge expected: Basic proficiency of English and basic understanding of C++, QML, and their interactions.<br />
<br />
Mentors: <br />
- Carson Black [ uhhadd AT gmail DOT com ]<br />
- Marco Martin [ notmart AT gmail DOT com ]</div>Pontaoshttps://community.kde.org/index.php?title=GSoD/2020/Ideas&diff=88093GSoD/2020/Ideas2020-04-22T19:12:06Z<p>Pontaos: </p>
<hr />
<div>== Guidelines ==<br />
<br />
=== Information for Technical Writers ===<br />
<br />
These ideas were contributed by our developers and users. They are sometimes vague or incomplete. If you wish to submit a proposal based on these ideas, you are urged to contact the developers and find out more about the particular suggestion you're looking at.<br />
<br />
<!-- Becoming accepted as a Google Summer of Documentation student is quite competitive. Accepted students typically have thoroughly researched the technologies of their proposed project and have been in frequent contact with potential mentors. '''Simply copying and pasting an idea here will not work.''' On the other hand, creating a completely new idea without first consulting potential mentors rarely works. --><br />
<br />
When writing your proposal or asking for help from the general KDE community don't assume people are familiar with the ideas here. KDE is really big!<br />
<br />
If there is no specific contact given you can ask questions on the general KDE development list kde-devel@kde.org and the KDE documentation list kde-doc-english@kde.org. See [https://kde.org/mailinglists/ the KDE mailing lists page] for information on available mailing lists and how to subscribe.<br />
<br />
{{Note|'''These are all proposals! We are open to new ideas you might have!!''' Do you have an awesome idea you want to work on with KDE but that is not among the ideas below? That's cool. We love that! But please do us a favor: Get in touch with a mentor early on and make sure your project is realistic and within the scope of KDE.}}<br />
<br />
__TOC__<br />
<br />
=== Adding a Proposal ===<br />
<br />
{{Note|Follow the template of other proposals!}}<br />
<br />
==== Project: ====<br />
<br />
'''If appropriate, screenshot or another image '''<br />
<br />
'''Brief explanation:'''<br />
<br />
'''Expected results:'''<br />
<br />
'''Knowledge Prerequisite:'''<br />
<br />
'''Mentor:'''<br />
<br />
When adding an idea to this section, please try to include the following data:<br />
<br />
:*if the application is not widely known, a description of what it does and where its code lives<br />
:*a brief explanation<br />
:*the expected results<br />
:*pre-requisites for working on your project<br />
:*if applicable, links to more information or discussions<br />
:*mailing list or IRC channel for your application/library/module<br />
:*your name and email address for contact (if you're willing to be a mentor) <br />
<br />
'''Ideas with no mentors listed and their contact info will be removed'''<br />
<br />
{{Note|The GSoD documtation has a section about [https://developers.google.com/season-of-docs/docs/project-ideas Project ideas].}}<br />
<br />
==Ideas==<br />
<br />
=== Kirigami ===<br />
<br />
Improving the accuracy, English, and examples of the Kirigami documentation will be useful for all developers seeking to use Kirigami in their applications.<br />
<br />
Prerequisite knowledge expected: Basic proficiency of English and basic understanding of C++, QML, and their interactions.<br />
<br />
Mentor: Carson Black [ uhhadd AT gmail DOT com ]</div>Pontaoshttps://community.kde.org/index.php?title=Guidelines_and_HOWTOs/Icon_Workflow_Tips&diff=87485Guidelines and HOWTOs/Icon Workflow Tips2020-02-08T16:55:34Z<p>Pontaos: Add how to use Ikona for icon workflow</p>
<hr />
<div>== Making icons ==<br />
<br />
Make sure you have read https://hig.kde.org/style/icons/index.html<br />
<br />
=== Applications ===<br />
<br />
Don't use proprietary software like Adobe Illustrator, Gravit Designer or Figma. All of our icons are made with Inkscape, but as long as your SVG editor is free, open source, compatible with Inkscape and compatible with the Qt SVG renderer, it should be OK to use.<br />
<br />
=== Canvas ===<br />
<br />
Make sure you always use a canvas that matches the size you're using for the icon (e.g., 48x48 px instead of 210x297 mm). In Inkscape, you can change the canvas size by going to <menuchoice>File -> Document Properties...</menuchoice> or <keycap>Ctrl + Shift + D</keycap><br />
<br />
=== Grid ===<br />
<br />
A grid can be extremely useful for making icons that appear sharp instead of blurry or faded. When making icons, a grid with 1 px of space between each line is generally ideal. In Inkscape, you can modify the grid settings by going to <menuchoice>File -> Document Properties... -> Grids</menuchoice>. You can toggle the grid on and off with <keycap>Shift + 3</keycap> (US Keyboard layout) or <keycap>#</keycap>.<br />
<br />
If you are making strokes with the Line tool in Inkscape (<keycap>Shift + F6</keycap>), it is useful to use a spacing of 0.5 px and a major grid line every 2 lines. Strokes are centered on the points where you create them, so they would appear between pixels if you used a 1px grid spacing.<br />
<br />
=== Drawing Techniques ===<br />
<br />
==== General Tips ====<br />
<br />
* Always convert strokes to paths. Strokes don't always show up correctly in various SVG renderers, including the Qt SVG renderer. In Inkscape, the shortcut to convert a stroke to a path is <keycap>Ctrl + Alt + C</keycap>.<br />
<br />
==== Diagonal lines ====<br />
<br />
The best way to get a 1px thick pixel perfect diagonal line is use strokes, line up the end points with the grid diagonally, place end points in the center of pixels, and enable end caps. Avoid snapping the sides of the line to the grid, although it is acceptable with some difficult to make shapes.<br />
<br />
See the pictures below: <br />
[[File:Diagonal 1px line style.png|center|frame|Left: wrong, Right: correct]]<br />
The image above at 1x size:<br />
[[File:Diagonal 1px line style 100%.png|left|none|The image above at 1x size]]<br />
<br />
* Notice that the incorrect style looks thicker and fuzzier than the vertical and horizontal lines while the correct style is more crisp and similar in thickness to the vertical and horizontal lines.<br />
<br />
== SVG optimization ==<br />
<br />
In general, SVGs should be optimized and automatically formatted. This makes them compact, easier to read and easier to manually edit (when necessary). There are multiple methods that can be used to optimize an SVG.<br />
<br />
=== Inkscape: Optimized SVG format ===<br />
<br />
This option does not strip embedded stylesheets, but saving in Inkscape always adds hardcoded colors to modified parts of the SVG. Remember to fix the hardcoded colors.<br />
<br />
<menuchoice>File -> Save As...</menuchoice> or <keycap>Ctrl + Shift + S</keycap><br />
<br />
Set the file type to <menuchoice>Optimized SVG (*.svg)</menuchoice><br />
<br />
Use these settings:<br />
<gallery><br />
Inkscape Optimized SVG dialog - Options page.png|Options<br />
Inkscape Optimized SVG dialog - SVG Output page.png|SVG Output<br />
Inkscape Optimized SVG dialog - IDs page.png|IDs<br />
</gallery><br />
<br />
=== Scour ===<br />
<br />
* https://github.com/scour-project/scour<br />
<br />
<code>scour</code> is available in many Linux distribution repositories. The package name is usually <code>scour</code> or <code>python-scour</code>.<br />
<br />
Put this somewhere that will be loaded by your shell:<br />
<br />
{{Input|<syntaxhighlight lang="Bash"><br />
# For optimizing SVGs in the Breeze icon theme<br />
function scour-icon {<br />
# Use this for icons from breeze-icons<br />
scour --set-precision=8 --enable-viewboxing --enable-comment-stripping --remove-descriptive-elements --create-groups --strip-xml-space --strip-xml-prolog --nindent=4 $1 output.svg<br />
mv output.svg $1<br />
}<br />
<br />
# For optimizing SVGs in the the Plasma theme<br />
function scour-theme {<br />
scour --set-precision=8 --enable-viewboxing --enable-comment-stripping --remove-descriptive-elements --strip-xml-space --strip-xml-prolog --nindent=4 $1 output.svg<br />
mv output.svg $1<br />
}<br />
</syntaxhighlight>}}<br />
<br />
Usage:<br />
<br />
{{Input|1=<nowiki><br />
cd [path to directory containing icon]<br />
scour-icon [icon name]<br />
</nowiki>}}<br />
<br />
=== SVG Cleaner ===<br />
<br />
* https://github.com/RazrFalcon/SVGCleaner<br />
* https://github.com/RazrFalcon/svgcleaner-gui<br />
<br />
Available in fewer distros, but it has a GUI if you prefer that. The package name is usually <code>svgcleaner</code> (for the CLI tool) or <code>svgcleaner-gui</code> (for the GUI). Always double check the positions of your gradients in Inkscape if you use this program. It will always strip embedded stylesheets, so if your SVG is supposed to have stylesheets, add those last. Do not use for desktop themes.<br />
<br />
Usage:<br />
<br />
{{Input|1=<nowiki><br />
svgcleaner icon-name.svg icon-name.svg --indent=4 --allow-bigger-file<br />
</nowiki>}}<br />
<br />
=== SVGO ===<br />
<br />
* https://github.com/svg/svgo<br />
<br />
Currently available in no distro repositories, but you can install it from Node Package Manager (<code>npm</code>) with this:<br />
<br />
{{Input|1=<nowiki><br />
sudo npm install -g svgo<br />
</nowiki>}}<br />
<br />
SVGO can be set to preserve stylesheets, but it will still strip <code>type="text/css"</code>, which is wrong. This command will strip stylesheets, so add those last. Do not use for desktop themes.<br />
<br />
Usage:<br />
<br />
{{Input|1=<nowiki><br />
svgo --pretty icon-name.svg<br />
</nowiki>}}<br />
<br />
=== Misc comments about SVG optimizers ===<br />
<br />
If you combine them, you can get a more thorough cleaning. I usually use SVG Cleaner and then SVGO for icons. Scour doesn't do as good of a job for color icons, which often require more cleaning to get the size down. However, it's nice when you're editing existing monochrome icons because it doesn't strip the stylesheets.<br />
<br />
== Embedding stylesheets in SVGs ==<br />
<br />
Put this somewhere that will be loaded by your shell:<br />
<br />
{{Input|<syntaxhighlight lang="Bash"><br />
#These will replace hardcoded colors with the appropriate class and currentColor fill for stylesheet compatibility<br />
# Made for people who do Breeze 1st and Breeze Dark 2nd<br />
# You still need to add stylesheets<br />
alias sed-Text="sed --follow-symlinks -i 's/fill=\"#232629\"/class=\"ColorScheme-Text\" fill=\"currentColor\"/'"<br />
alias sed-Background="sed --follow-symlinks -i 's/fill=\"#eff0f1\"/class=\"ColorScheme-Background\" fill=\"currentColor\"/'"<br />
alias sed-ViewBackground="sed --follow-symlinks -i 's/fill=\"#fcfcfc\"/class=\"ColorScheme-ViewBackground\" fill=\"currentColor\"/'"<br />
alias sed-ButtonFocus="sed --follow-symlinks -i 's/fill=\"#3daee9\"/class=\"ColorScheme-ButtonFocus\" fill=\"currentColor\"/'"<br />
alias sed-PositiveText="sed --follow-symlinks -i 's/fill=\"#27ae60\"/class=\"ColorScheme-PositiveText\" fill=\"currentColor\"/'"<br />
alias sed-NeutralText="sed --follow-symlinks -i 's/fill=\"#f67400\"/class=\"ColorScheme-NeutralText\" fill=\"currentColor\"/'"<br />
alias sed-NegativeText="sed --follow-symlinks -i 's/fill=\"#da4453\"/class=\"ColorScheme-NegativeText\" fill=\"currentColor\"/'"<br />
<br />
# Convert Breeze icon with stylesheet to Breeze Dark. ColorScheme-Text only<br />
alias sed-breeze-dark="sed --follow-symlinks -i 's/color:#232629/color:#eff0f1/'"<br />
# Convert Breeze Dark icon with stylesheet to Breeze. ColorScheme-Text only<br />
alias sed-breeze="sed --follow-symlinks -i 's/color:#eff0f1/color:#232629/'"<br />
</syntaxhighlight>}}<br />
<br />
Usage:<br />
<br />
{{Input|1=<nowiki><br />
sed-Text an-icon.svg<br />
sed-Text *wild*cards*work*<br />
</nowiki>}}<br />
<br />
=== Stylesheets ===<br />
<br />
Only include the color classes you will actually use.<br />
<br />
Most monochrome icons will only need this much:<br />
<br />
{{Input|<syntaxhighlight lang="XML"><br />
<style type="text/css" id="current-color-scheme"><br />
.ColorScheme-Text {<br />
color:#232629;<br />
}<br />
</style><br />
</syntaxhighlight>}}<br />
<br />
==== Breeze ====<br />
<br />
{{Input|<syntaxhighlight lang="XML"><br />
<style type="text/css" id="current-color-scheme"><br />
.ColorScheme-Text {<br />
color:#232629;<br />
}<br />
.ColorScheme-Background {<br />
color:#eff0f1;<br />
}<br />
.ColorScheme-ViewBackground {<br />
color:#fcfcfc;<br />
}<br />
.ColorScheme-ButtonFocus {<br />
color:#3daee9;<br />
}<br />
.ColorScheme-PositiveText {<br />
color:#27ae60;<br />
}<br />
.ColorScheme-NeutralText {<br />
color:#f67400;<br />
}<br />
.ColorScheme-NegativeText {<br />
color:#da4453;<br />
}<br />
</style><br />
</syntaxhighlight>}}<br />
<br />
==== Breeze Dark ====<br />
<br />
{{Input|<syntaxhighlight lang="XML"><br />
<style type="text/css" id="current-color-scheme"><br />
.ColorScheme-Text {<br />
color:#eff0f1;<br />
}<br />
.ColorScheme-Background {<br />
color:#31363b;<br />
}<br />
.ColorScheme-ViewBackground {<br />
color:#232629;<br />
}<br />
.ColorScheme-ButtonFocus {<br />
color:#3daee9;<br />
}<br />
.ColorScheme-PositiveText {<br />
color:#27ae60;<br />
}<br />
.ColorScheme-NeutralText {<br />
color:#f67400;<br />
}<br />
.ColorScheme-NegativeText {<br />
color:#da4453;<br />
}<br />
</style><br />
</syntaxhighlight>}}<br />
<br />
The only differences are Text, Background and ViewBackground.<br />
<br />
For background information, see http://notmart.org/blog/2016/05/icon-colors/<br />
<br />
== Using Ikona for optimization and stylesheet injection ==<br />
<br />
[https://invent.kde.org/kde/ikona Ikona] offers a command line utility called <code>ikona-cli</code> that can optimize and inject stylesheets into your icon.<br />
<br />
Usage for injecting stylesheets (note that commands can change based on locale):<br />
<br />
Injects the Breeze (Normal) stylesheet and replaces colors:<br />
{{Input|1=<nowiki><br />
ikona-cli class --mode light input.svg output.svg<br />
</nowiki>}}<br />
<br />
Injects the Breeze Dark stylesheet and replaces colors:<br />
{{Input|1=<nowiki><br />
ikona-cli class --mode dark input.svg output.svg<br />
</nowiki>}}<br />
<br />
Optimize your icon:<br />
{{Input|1=<nowiki><br />
ikona-cli optimize input.svg output.svg<br />
</nowiki>}}<br />
<br />
== Icon compilation images ==<br />
<br />
<code>montage</code> can be used to make compilations of all your icons quickly. The package name is usually <code>ImageMagick</code> or <code>imagemagick</code>.<br />
<br />
Put this somewhere that will be loaded by your shell:<br />
<br />
{{Input|<syntaxhighlight lang="Bash"><br />
alias montage-breeze="montage -density 96x96 -fill '#232629' -label '%t' -background '#eff0f1'" # Background color<br />
alias montage-breeze2="montage -density 96x96 -fill '#232629' -label '%t' -background '#fcfcfc'" # ViewBackground color<br />
alias montage-breeze-dark="montage -density 96x96 -fill '#eff0f1' -label '%t' -background '#31363b'" # Background color<br />
alias montage-breeze-dark2="montage -density 96x96 -fill '#eff0f1' -label '%t' -background '#232629'" # ViewBackground color<br />
</syntaxhighlight>}}<br />
<br />
Usage:<br />
<br />
{{Input|1=<nowiki><br />
montage-breeze an-icon-here.svg ../an-icon-up-there.svg ../*/*wild*cards*work* montage-breeze-Background.png # The PNG at the end is the image that the command will create<br />
</nowiki>}}</div>Pontaoshttps://community.kde.org/index.php?title=SoK/Ideas/2020&diff=87100SoK/Ideas/20202020-01-02T04:44:03Z<p>Pontaos: </p>
<hr />
<div>[[File:Mascot konqi-app-presentation.png|thumbnail|right|[[Konqi]] is giving a lesson!]]<br />
==Ideas==<br />
<br />
=== Information for students ===<br />
<br />
These ideas were contributed by our developers and users. They are sometimes vague or incomplete. If you wish to submit a proposal based on these ideas, contact the developers and find out more about the particular suggestion you're interested in.<br />
<br />
When writing your proposal or asking for help from the general KDE community don't assume people are familiar with the ideas here. KDE is really big!<br />
<br />
If there is no specific contact given in the idea, you can ask questions on the general KDE development list kde-devel@kde.org. See [http://www.kde.org/mailinglists/ the KDE mailing lists page] for information on available mailing lists and how to subscribe.<br />
<br />
=== Sample project ===<br />
<br />
'''Project type:''' Coding / Web Development / Promo / Translation<br />
<br />
'''Brief explanation:'''<br />
<br />
'''Expected results:'''<br />
<br />
'''Knowledge Prerequisite:'''<br />
<br />
'''Mentor:'''<br />
<br />
When adding an idea to this section, please try to include the following data:<br />
<br />
:*if the application is not widely known, a description of what it does and where its code lives<br />
:*a brief explanation<br />
:*the expected results<br />
:*pre-requisites for working on your project<br />
:*if applicable, links to more information or discussions<br />
:*mailing list or IRC channel for your application/library/module<br />
:*your name and email address for contact (if you're willing to be a mentor)<br />
<br />
If you are not a developer but have a good idea for a proposal, get in contact with relevant developers first.<br />
<br />
===Your Own Idea ===<br />
<br />
==== Something that you're totally excited about ====<br />
<br />
'''Project type:''' Coding / Web Development / Promo / Translation<br />
<br />
'''Brief explanation:''' Do you have an awesome idea you want to work on with KDE but that is not among the ideas below? That's cool. We love that! But please do us a favor: Get in touch with a mentor early on and make sure your project is realistic and within the scope of KDE. That will spare you and us a lot of frustration.<br />
<br />
'''Expected results:''' Something you and KDE loves<br />
<br />
'''Knowledge Prerequisite:''' Probably C++ and Qt but depends on your project<br />
<br />
'''Mentor:''' Try to see who in KDE is interested in what you want to work on and approach them. If you are unsure you can always ask in #kde-soc on Freenode IRC.<br />
<br />
=== Atelier ===<br />
<br />
'''Project type:''' Coding<br />
<br />
'''Brief explanation:'''<br />
Atelier is the 3DPrinting software built by the KDE Community to help you to control your 3Dprinters from your PC, and hopeful from any device.<br />
<br />
'''Expected results:'''<br />
<br />
What we would like to have:<br />
<br />
* Build a web layer on [https://invent.kde.org/kde/atcore/ AtCore](That is the library behind Atelier)<br />
* Build an interface with QML for mobile/embedded devices.<br />
<br />
'''Knowledge Prerequisite:'''<br />
C++ and Qt. <br />
<br />
'''Mentor:'''<br />
Lays Rodrigues<br />
Tomaz Canabrava<br />
Chris Rizzitello<br />
<br />
=== Calligra ===<br />
<br />
'''Project type:''' Web Development<br />
<br />
'''Brief explanation:'''<br />
Calligra is an office program developed by KDE for 22 years. Currently, the webpage of Calligra looks very dated and is using old screenshots from the KDE4 era. The task consists of rewriting the website to look similar to kontact.kde.org. Since the code can be reused the task will consist mostly in writing content and taking screenshots.<br />
<br />
'''Expected results:'''<br />
</br><br />
A beautiful webpage for the promotion of Calligra.<br />
<br />
'''Knowledge Prerequisite:'''<br />
Markdown and some very basic programming. Familiarity with git. Good English knowledge is recommended.<br />
<br />
'''Mentor:'''<br />
Carl Schwan, ping me in https://t.me/KDEWeb or #kde-www in Freenode/Matrix<br />
<br />
=== GCompris ===<br />
<br />
'''Project type:''' Coding<br />
<br />
'''Brief explanation''': <br />
[https://gcompris.net/ GCompris] is a high quality educational software suite, including a large number of activities for children aged 2 to 10. We recently introduced a multiple level selection. This allows user to choose more closely the competences they want to work on. For example when working on numeration, user can now choose if he wants to learn numbers from 0 to 3 or 0 to 4 or 0 to 5 etc... <br />
[mailto:gcompris-devel@kde.org Contact] the GCompris team.<br />
<br />
'''Expected results''':<br />
The aim of this year is to complete the number of activities including this features.<br />
Targeted activities are listed under the following address:<br />
<br />
https://phabricator.kde.org/T12428<br />
<br />
Activities already including the selection level can be found in our git repository under multiple_dataset branch. Activities are smallnumber, smallnumbers2, gletters, reversecount, gletters. <br />
<br />
'''Knowledge Prerequisite''':<br />
<br />
Be interested in children’s education<br />
<br />
Be familiar with GCompris concept and content<br />
<br />
Basic knowledge in a programming language (a 1 year school course is enough)<br />
<br />
Be able to build the Qt Quick version of GCompris<br />
<br />
'''Application guide''':<br />
Provide a timeline in your application. If you haven't contributed yet please read http://gcompris.net/wiki/GSOC_newcomers, http://gcompris.net/wiki/An_exercise_for_new_contributors and http://gcompris.net/wiki/Reviewing_an_activity<br />
<br />
There are several info in the wiki: http://gcompris.net/wiki/Developer%27s_corner.<br />
<br />
''Feel free to contact us either on irc or by mail (gcompris-devel@kde.org)''<br />
<br />
'''Mentors''': Emmanuel Charruau (IRC: allon), Johnny Jazeix (IRC: JohnnyJ), Timothée Giet (IRC: Animtim), Rajdeep Kaur (IRC: )<br />
<br />
=== Kdenlive ===<br />
<br />
'''Project type:''' Coding<br />
<br />
'''Brief explanation:'''<br />
Improve the [https://invent.kde.org/kde/kdenlive/issues/445 timeline clips color palette]. <br />
<br />
'''Expected results:'''<br />
To have a better UI/UX by designing a concept on how clips should look in the timeline. Also improve the way audio waves are displayed.<br />
<br />
'''Knowledge Prerequisite:'''<br />
Qt and QML<br />
<br />
=== KDE Connect ===<br />
<br />
'''Project type:''' Web Development<br />
<br />
'''Brief explanation:'''<br />
Create a website for KDE Connect for better outreach and visibility.<br />
<br />
The current discussion for this project is available [https://phabricator.kde.org/T10615 here].<br />
<br />
'''Expected results:'''<br />
* To have a static website for KDE Connect that allows any user or developer to understand the purpose and features of KDE Connect <br />
* To provide static link(s) for the various master builds of KDE Connect applications, namely the android application and its desktop counterpart(s).<br />
<br />
<br />
'''Knowledge Prerequisite:'''<br />
* Basic knowledge of HTML, CSS, JavaScript. <br />
* Previous static website projects are a nice-to-have.<br />
* Please do elaborate about how you plan to explain the inner working of KDE Connect in your proposal.<br />
<br />
'''Mentors:'''<br />
* Carl Schwan, ping me in https://t.me/KDEWeb or #kde-www in Freenode/Matrix<br />
* Piyush Aggarwal<br />
<br />
=== KDE Web ===<br />
<br />
'''Project type:''' Web Development / Promo<br />
<br />
'''Brief explanation:''' We need to update the version of dot.kde.org, blog.kde.org and akademy.kde.org from drupal 7 to drupal 8. We should use this opportunity to create a new theme for those drupal websites.<br />
<br />
'''Expected results:'''<br />
<br /><br />
A more modern webpage for the promotion of KDE and KDE events.<br />
<br />
'''Knowledge Prerequisite:'''<br />
Drupal 8 or good php knownledge. The theme is already provided so you don't need to be a designer ;)<br />
<br />
'''Mentor:'''<br />
Carl Schwan, ping me in https://t.me/KDEWeb or #kde-www in Freenode/Matrix<br />
<br />
=== Krita ===<br />
<br />
'''Project type:''' Coding / Documentation / Tutorials / Usability<br />
<br />
'''Brief explanation:'''<br />
Krita is a wide-used digital painting application, written in C++ and Qt. Plugins can also be written in Python. If you want to participate in Season of KDE 2020 for Krita, please contact the Krita developers on #krita on irc.freenode.org (there is also a matrix mirror on webchat.kde.org). We prefer students bring their own ideas. Examples of coding projects you can work on are image filters, pixel generators or brush engines. Non-coding project proposals are welcome as well. These could take the form of papercuts inventories, usability surveys or creating tutorials for underdocumented aspects of Krita.<br />
<br />
'''Mentor:'''<br />
Boudewijn Rempt<br />
<br />
=== KDE Developer Portal ===<br />
<br />
'''Project type:''' Documentation / Web Development / Marketing<br />
<br />
'''Brief explanation:'''<br />
KDE as a project is lacking a "start here" portal for both internal and external purposes. A developer portal gives a launchpad to both contributors looking to contribute to a project directly as well as third-party developers looking to take advantage of a project's offerings for their own applications.<br />
<br />
'''Mentor:'''<br />
Carson Black (Matrix @appadeia:matrix.org, Telegram @pontaoski)<br />
<br />
=== marK ===<br />
<br />
'''Project type:''' Coding<br />
<br />
'''Brief explanation:'''<br />
marK is a machine learning dataset annotation tool which allows users to annotate multiple types of data to help during the training for supervised classification problems. It is currently under development and we are planning to release its beta version soon. We now have a version of marK that was developed with Qt Widgets, but we are planning to port it to QML, as it will provide an easier way to manipulate different types of data and a possible release for mobile devices in the future. More information can be seen in this post: https://caiojcarvalho.wordpress.com/2019/01/29/mark-a-general-purpose-tool-for-data-annotation/<br />
<br />
'''Expected results:'''<br />
Finish porting marK to QML.<br />
<br />
'''Knowledge Prerequisite:'''<br />
Qt and QML<br />
<br />
'''Mentor:'''<br />
Caio Jordão Carvalho<br />
<br />
=== ROCS ===<br />
<br />
'''Project type:''' Coding<br />
<br />
'''Brief explanation:'''<br />
Rocs is a Graph Theory IDE for designing and analyzing graph algorithms. It provides a easy to use visual editor for creating graphs, a scripting engine to execute the<br />
algorithms and other tools for experimentation on graphs. The scripting<br />
language is Javascript. The UI for Rocs is built with a mix of QWidgets and QML.<br />
<br />
'''Tasks'''<br />
There are multiple tasks; it is not expected that a single student would deal with all of them.<br />
* Fixing the '''graph editor view''' that have some problems related to the placement of the graphs in the view and mouse clicks not working correctly.<br />
* Improving workflow for graph generation. Generating a (for instance, random) graph is rather tedious, and that workflow can be improved.<br />
* The UI is not aligned "nicely" and has a lot of internal borders and whitespace that no longer match up with the UI guidelines for KDE projects. It would be nice to simplify and "tighten up" the UI.<br />
<br />
'''Expected results:'''<br />
* A graph editor view working correctly.<br />
* Easier to generate graphs.<br />
* Looks better and follows the HIG better.<br />
<br />
'''Knowledge Prerequisite:'''<br />
Basic programming in C++ and QML. Familiarity with git. Good English knowledge is recommended.<br />
<br />
'''Mentor:'''<br />
Caio Tonetti, Tomaz Canabrava, Adriaan de Groot<br />
<br />
'''See Also:'''<br />
https://community.kde.org/KDEEdu/Rocs/Todo<br />
<br />
=== Plasma Phonebook Contact Groups ===<br />
'''Project type:''' Coding<br />
<br />
'''Brief explanation:'''<br />
plasma-phonebook is a contacts application for Plasma Mobile and other mobile OS. Goal of this task is to add group management to the app. Contacts can be assigned one or multiple groups and groups can be browsed<br />
<br />
'''Expected results:'''<br />
A basic group management inside the application.<br />
<br />
'''Knowledge Prerequisite:'''<br />
Basic programming in C++.<br />
<br />
'''Mentor:'''<br />
Nicolas Fella<br />
<br />
'''Contact:'''<br />
https://www.plasma-mobile.org/join/<br />
<br />
=== Plasma Mobile Clock application ===<br />
'''Project type:''' Coding<br />
<br />
'''Brief explanation:'''<br />
Plasma Mobile needs a suitable clock application that provides alarms, stopwatch and similar functionality. There is a work in progress that needs expansion (https://phabricator.kde.org/T8904)<br />
<br />
'''Expected results:'''<br />
Basic functionality works<br />
<br />
'''Knowledge Prerequisite:'''<br />
Basic programming in C++.<br />
<br />
'''Mentor:'''<br />
Nicolas Fella<br />
<br />
'''Contact:'''<br />
https://www.plasma-mobile.org/join/<br />
<br />
=== Plasma Mobile: Nextcloud contacts integration ===<br />
'''Project type:''' Coding<br />
<br />
'''Brief explanation:'''<br />
Plasma Mobile is KDE's software stack for mobile devices that includes Plasma phone components, Kirigami and a set of mobile-friendly applications. Plasma Mobile offers the Nextcloud account integration. <br />
<br />
Goal of this task is addition of '''Edit Contact''' functionality to enable users to edit contacts synced from Nextcloud account using Plasma-Phonebook app.<br />
<br />
'''Expected results:'''<br />
User is able to edit contacts that are synced from Nextcloud account using Plasma-Phonebook app.<br />
<br />
'''Knowledge Prerequisite:'''<br />
Basic knowledge of C++, Qt. <br />
Knowledge of [https://kube-sink.readthedocs.io Sink] is nice to have.<br />
<br />
Example code to use sink API for contact synchronization: [https://invent.kde.org/rpatwal/sink-use-examples/tree/master/sink-caldav-example sink-caldav-example]<br />
<br />
'''Mentor:'''<br />
Rituka Patwal<br />
<br />
'''Contact:'''<br />
https://www.plasma-mobile.org/join/</div>Pontaoshttps://community.kde.org/index.php?title=SoK/Ideas/2020&diff=87052SoK/Ideas/20202019-12-25T21:29:43Z<p>Pontaos: Add new idea</p>
<hr />
<div>[[File:Mascot konqi-app-presentation.png|thumbnail|right|[[Konqi]] is giving a lesson!]]<br />
==Ideas==<br />
<br />
=== Information for students ===<br />
<br />
These ideas were contributed by our developers and users. They are sometimes vague or incomplete. If you wish to submit a proposal based on these ideas, contact the developers and find out more about the particular suggestion you're interested in.<br />
<br />
When writing your proposal or asking for help from the general KDE community don't assume people are familiar with the ideas here. KDE is really big!<br />
<br />
If there is no specific contact given in the idea, you can ask questions on the general KDE development list kde-devel@kde.org. See [http://www.kde.org/mailinglists/ the KDE mailing lists page] for information on available mailing lists and how to subscribe.<br />
<br />
=== Sample project ===<br />
<br />
'''Project type:''' Coding / Web Development / Promo / Translation<br />
<br />
'''Brief explanation:'''<br />
<br />
'''Expected results:'''<br />
<br />
'''Knowledge Prerequisite:'''<br />
<br />
'''Mentor:'''<br />
<br />
When adding an idea to this section, please try to include the following data:<br />
<br />
:*if the application is not widely known, a description of what it does and where its code lives<br />
:*a brief explanation<br />
:*the expected results<br />
:*pre-requisites for working on your project<br />
:*if applicable, links to more information or discussions<br />
:*mailing list or IRC channel for your application/library/module<br />
:*your name and email address for contact (if you're willing to be a mentor)<br />
<br />
If you are not a developer but have a good idea for a proposal, get in contact with relevant developers first.<br />
<br />
===Your Own Idea ===<br />
<br />
==== Something that you're totally excited about ====<br />
<br />
'''Project type:''' Coding / Web Development / Promo / Translation<br />
<br />
'''Brief explanation:''' Do you have an awesome idea you want to work on with KDE but that is not among the ideas below? That's cool. We love that! But please do us a favor: Get in touch with a mentor early on and make sure your project is realistic and within the scope of KDE. That will spare you and us a lot of frustration.<br />
<br />
'''Expected results:''' Something you and KDE loves<br />
<br />
'''Knowledge Prerequisite:''' Probably C++ and Qt but depends on your project<br />
<br />
'''Mentor:''' Try to see who in KDE is interested in what you want to work on and approach them. If you are unsure you can always ask in #kde-soc on Freenode IRC.<br />
<br />
=== Atelier ===<br />
<br />
'''Project type:''' Coding<br />
<br />
'''Brief explanation:'''<br />
Atelier is the 3DPrinting software built by the KDE Community to help you to control your 3Dprinters from your PC, and hopeful from any device.<br />
<br />
'''Expected results:'''<br />
<br />
What we would like to have:<br />
<br />
* Build a web layer on [https://invent.kde.org/kde/atcore/ AtCore](That is the library behind Atelier)<br />
* Build an interface with QML for mobile/embedded devices.<br />
<br />
'''Knowledge Prerequisite:'''<br />
C++ and Qt. <br />
<br />
'''Mentor:'''<br />
Lays Rodrigues<br />
Tomaz Canabrava<br />
Chris Rizzitello<br />
<br />
=== Calligra ===<br />
<br />
'''Project type:''' Web Development<br />
<br />
'''Brief explanation:'''<br />
Calligra is an office program developed by KDE for 22 years. Currently, the webpage of Calligra looks very dated and is using old screenshots from the KDE4 era. The task consists of rewriting the website to look similar to kontact.kde.org. Since the code can be reused the task will consist mostly in writing content and taking screenshots.<br />
<br />
'''Expected results:'''<br />
</br><br />
A beautiful webpage for the promotion of Calligra.<br />
<br />
'''Knowledge Prerequisite:'''<br />
Markdown and some very basic programming. Familiarity with git. Good English knowledge is recommended.<br />
<br />
'''Mentor:'''<br />
Carl Schwan, ping me in https://t.me/KDEWeb or #kde-www in Freenode/Matrix<br />
<br />
=== GCompris ===<br />
<br />
'''Project type:''' Coding<br />
<br />
'''Brief explanation''': <br />
[https://gcompris.net/ GCompris] is a high quality educational software suite, including a large number of activities for children aged 2 to 10. We recently introduced a multiple level selection. This allows user to choose more closely the competences they want to work on. For example when working on numeration, user can now choose if he wants to learn numbers from 0 to 3 or 0 to 4 or 0 to 5 etc... <br />
[mailto:gcompris-devel@kde.org Contact] the GCompris team.<br />
<br />
'''Expected results''':<br />
The aim of this year is to complete the number of activities including this features.<br />
Targeted activities are:<br />
<br />
- Enumeration memory game<br />
<br />
- Find the date<br />
<br />
- Count the items<br />
<br />
- Balance the scales properly<br />
<br />
But also to improve the level selection for the following activities :<br />
<br />
- Analog watch<br />
<br />
- Small Numbers<br />
<br />
Activities already including the selection level can be found in our git repository under multiple_dataset branch. Activities are smallnumber, smallnumbers2, gletters, reversecount, gletters. <br />
<br />
'''Knowledge Prerequisite''':<br />
<br />
Be interested in children’s education<br />
<br />
Be familiar with GCompris concept and content<br />
<br />
Basic knowledge in a programming language (a 1 year school course is enough)<br />
<br />
Be able to build the Qt Quick version of GCompris<br />
<br />
'''Application guide''':<br />
Provide a timeline in your application. If you haven't contributed yet please read http://gcompris.net/wiki/GSOC_newcomers, http://gcompris.net/wiki/An_exercise_for_new_contributors and http://gcompris.net/wiki/Reviewing_an_activity<br />
<br />
There are several info in the wiki: http://gcompris.net/wiki/Developer%27s_corner.<br />
<br />
''Feel free to contact us either on irc or by mail (gcompris-devel@kde.org)''<br />
<br />
'''Mentors''': Emmanuel Charruau (IRC: allon), Johnny Jazeix (IRC: JohnnyJ), Timothée Giet (IRC: Animtim), Rajdeep Kaur (IRC: )<br />
<br />
=== Kdenlive ===<br />
<br />
'''Project type:''' Coding<br />
<br />
'''Brief explanation:'''<br />
Improve the [https://invent.kde.org/kde/kdenlive/issues/445 timeline clips color palette]. <br />
<br />
'''Expected results:'''<br />
To have a better UI/UX by designing a concept on how clips should look in the timeline. Also improve the way audio waves are displayed.<br />
<br />
'''Knowledge Prerequisite:'''<br />
Qt and QML<br />
<br />
=== KDE Connect ===<br />
<br />
'''Project type:''' Web Development<br />
<br />
'''Brief explanation:'''<br />
Create a website for KDE Connect for better outreach and visibility.<br />
<br />
The current discussion for this project is available [https://phabricator.kde.org/T10615 here].<br />
<br />
'''Expected results:'''<br />
* To have a static website for KDE Connect that allows any user or developer to understand the purpose and features of KDE Connect <br />
* To provide static link(s) for the various master builds of KDE Connect applications, namely the android application and its desktop counterpart(s).<br />
<br />
<br />
'''Knowledge Prerequisite:'''<br />
* Basic knowledge of HTML, CSS, JavaScript. <br />
* Previous static website projects are a nice-to-have.<br />
* Please do elaborate about how you plan to explain the inner working of KDE Connect in your proposal.<br />
<br />
'''Mentors:'''<br />
* Carl Schwan, ping me in https://t.me/KDEWeb or #kde-www in Freenode/Matrix<br />
* Piyush Aggarwal<br />
<br />
=== KDE Web ===<br />
<br />
'''Project type:''' Web Development / Promo<br />
<br />
'''Brief explanation:''' We need to update the version of dot.kde.org, blog.kde.org and akademy.kde.org from drupal 7 to drupal 8. We should use this opportunity to create a new theme for those drupal websites.<br />
<br />
'''Expected results:'''<br />
<br /><br />
A more modern webpage for the promotion of KDE and KDE events.<br />
<br />
'''Knowledge Prerequisite:'''<br />
Drupal 8 or good php knownledge. The theme is already provided so you don't need to be a designer ;)<br />
<br />
'''Mentor:'''<br />
Carl Schwan, ping me in https://t.me/KDEWeb or #kde-www in Freenode/Matrix<br />
<br />
=== Krita ===<br />
<br />
'''Project type:''' Coding / Documentation / Tutorials / Usability<br />
<br />
'''Brief explanation:'''<br />
Krita is a wide-used digital painting application, written in C++ and Qt. Plugins can also be written in Python. If you want to participate in Season of KDE 2020 for Krita, please contact the Krita developers on #krita on irc.freenode.org (there is also a matrix mirror on webchat.kde.org). We prefer students bring their own ideas. Examples of coding projects you can work on are image filters, pixel generators or brush engines. Non-coding project proposals are welcome as well. These could take the form of papercuts inventories, usability surveys or creating tutorials for underdocumented aspects of Krita.<br />
<br />
'''Mentor:'''<br />
Boudewijn Rempt<br />
<br />
=== KDE Developer Portal ===<br />
<br />
'''Project type:''' Documentation / Web Development / Marketing<br />
<br />
'''Brief explanation:'''<br />
KDE as a project is lacking a "start here" portal for both internal and external purposes. A developer portal gives a launchpad to both contributors looking to contribute to a project directly as well as third-party developers looking to take advantage of a project's offerings for their own applications.<br />
<br />
'''Mentor:'''<br />
Carson Black<br />
<br />
=== marK ===<br />
<br />
'''Project type:''' Coding<br />
<br />
'''Brief explanation:'''<br />
marK is a machine learning dataset annotation tool which allows users to annotate multiple types of data to help during the training for supervised classification problems. It is currently under development and we are planning to release its beta version soon. We now have a version of marK that was developed with Qt Widgets, but we are planning to port it to QML, as it will provide an easier way to manipulate different types of data and a possible release for mobile devices in the future. More information can be seen in this post: https://caiojcarvalho.wordpress.com/2019/01/29/mark-a-general-purpose-tool-for-data-annotation/<br />
<br />
'''Expected results:'''<br />
Finish porting marK to QML.<br />
<br />
'''Knowledge Prerequisite:'''<br />
Qt and QML<br />
<br />
'''Mentor:'''<br />
Caio Jordão Carvalho<br />
<br />
=== ROCS ===<br />
<br />
'''Project type:''' Coding<br />
<br />
'''Brief explanation:'''<br />
Rocs is a Graph Theory IDE for designing and analyzing graph algorithms. It provides a easy to use visual editor for creating graphs, a scripting engine to execute the<br />
algorithms and other tools for experimentation on graphs. The scripting<br />
language is Javascript. The UI for Rocs is built with a mix of QWidgets and QML.<br />
<br />
'''Tasks'''<br />
There are multiple tasks; it is not expected that a single student would deal with all of them.<br />
* Fixing the '''graph editor view''' that have some problems related to the placement of the graphs in the view and mouse clicks not working correctly.<br />
* Improving workflow for graph generation. Generating a (for instance, random) graph is rather tedious, and that workflow can be improved.<br />
* The UI is not aligned "nicely" and has a lot of internal borders and whitespace that no longer match up with the UI guidelines for KDE projects. It would be nice to simplify and "tighten up" the UI.<br />
<br />
'''Expected results:'''<br />
* A graph editor view working correctly.<br />
* Easier to generate graphs.<br />
* Looks better and follows the HIG better.<br />
<br />
'''Knowledge Prerequisite:'''<br />
Basic programming in C++ and QML. Familiarity with git. Good English knowledge is recommended.<br />
<br />
'''Mentor:'''<br />
Caio Tonetti, Tomaz Canabrava, Adriaan de Groot<br />
<br />
'''See Also:'''<br />
https://community.kde.org/KDEEdu/Rocs/Todo<br />
<br />
=== Plasma Phonebook Contact Groups ===<br />
'''Project type:''' Coding<br />
<br />
'''Brief explanation:'''<br />
plasma-phonebook is a contacts application for Plasma Mobile and other mobile OS. Goal of this task is to add group management to the app. Contacts can be assigned one or multiple groups and groups can be browsed<br />
<br />
'''Expected results:'''<br />
A basic group management inside the application.<br />
<br />
'''Knowledge Prerequisite:'''<br />
Basic programming in C++.<br />
<br />
'''Mentor:'''<br />
Nicolas Fella<br />
<br />
'''Contact:'''<br />
https://www.plasma-mobile.org/join/<br />
<br />
=== Plasma Mobile Clock application ===<br />
'''Project type:''' Coding<br />
<br />
'''Brief explanation:'''<br />
Plasma Mobile needs a suitable clock application that provides alarms, stopwatch and similar functionality. There is a work in progress that needs expansion (https://phabricator.kde.org/T8904)<br />
<br />
'''Expected results:'''<br />
Basic functionality works<br />
<br />
'''Knowledge Prerequisite:'''<br />
Basic programming in C++.<br />
<br />
'''Mentor:'''<br />
Nicolas Fella<br />
<br />
'''Contact:'''<br />
https://www.plasma-mobile.org/join/<br />
<br />
=== Plasma Mobile: Nextcloud contacts integration ===<br />
'''Project type:''' Coding<br />
<br />
'''Brief explanation:'''<br />
Plasma Mobile is KDE's software stack for mobile devices that includes Plasma phone components, Kirigami and a set of mobile-friendly applications. Plasma Mobile offers the Nextcloud account integration. <br />
<br />
Goal of this task is addition of '''Edit Contact''' functionality to enable users to edit contacts synced from Nextcloud account using Plasma-Phonebook app.<br />
<br />
'''Expected results:'''<br />
User is able to edit contacts that are synced from Nextcloud account using Plasma-Phonebook app.<br />
<br />
'''Knowledge Prerequisite:'''<br />
Basic knowledge of C++, Qt. <br />
Knowledge of [https://kube-sink.readthedocs.io Sink] is nice to have.<br />
<br />
Example code to use sink API for contact synchronization: [https://invent.kde.org/rpatwal/sink-use-examples/tree/master/sink-caldav-example sink-caldav-example]<br />
<br />
'''Mentor:'''<br />
Rituka Patwal<br />
<br />
'''Contact:'''<br />
https://www.plasma-mobile.org/join/</div>Pontaoshttps://community.kde.org/index.php?title=KDE_Visual_Design_Group/Plasma_5.18_Wallpaper_Competition&diff=87030KDE Visual Design Group/Plasma 5.18 Wallpaper Competition2019-12-22T21:22:46Z<p>Pontaos: Adjust English style</p>
<hr />
<div>Submit your designs to [https://forum.kde.org/viewforum.php?f=313 the subforum we have set up for the competition]. We also have a [https://community.kde.org/Promo/Plasma_5.18_Video_Competition video competition] ongoing. <br />
<br />
Read everything on this page very carefully before entering your submission.<br />
<br />
== Rules ==<br />
<br />
# The deadline for submissions is January 15th, 2020, at midnight UTC time. The winning wallpaper will be announced on January 22nd, 2020.<br />
# Your wallpaper must be your original and created specifically for the contest.<br />
# Your wallpaper must be released to KDE under the CC-BY-SA-4.0 license.<br />
# You are allowed a max of 3 submissions.<br />
# Images must be in PNG format. <br />
# If asked, you should be able to provide the source files used to create the wallpaper in a non-proprietary format, like an Inkscape-compatible SVG, .blend, .kra, .xcf, etc.<br />
# The minimum required size for wallpapers is 4K measurements (3840x2160), although 5K (5120x2880) is preferred.<br />
# A companion phone-sized (1080x2280) wallpaper for Plasma Mobile can also be submitted.<br />
# Image files must be hosted on an external (non-KDE) site without compression. Two sites that host images without compression for free are [https://imgbox.com/ imgbox.com] and [https://postimages.org/ postimages.org]. You can also upload the image to your preferred cloud storage provider, such as Google Drive, Dropbox, or OneDrive.<br />
# Any submissions containing racist, sexist, demeaning, or inappropriate content in any way will be disqualified immediately.<br />
# Any submissions of copyrighted material from third parties with little or no modifications will be disqualified and erased.<br />
# Disqualified entries and deletions are final and cannot be appealed.<br />
<br />
== Design Guidance & Suggestions ==<br />
<br />
# Images should iterate and capture the graphical elements of the previous wallpaper selection and should feel like a new version of graphical elements seen in the "Ice Cold" wallpaper.<br />
# Do not add the Plasma version number (5.18) into your wallpaper or any other text elements.<br />
# Any text or logos should integrate into the wallpaper design and not be used for quick identification. Text and logos should not drive attention away from the main design of your original piece.<br />
<br />
<br/><br />
<br />
The six following wallpapers, made by Ken Vermette and Santiago César, are used in previous versions of Plasma. You can find [https://store.kde.org/member/103267/ Ken Vermette's work on this page].<br />
<br />
<gallery mode="packed-hover"><br />
Image:5.16.jpg|''[https://community.kde.org/images.community/f/f4/5.16_large.png Ice Cold] (Plasma 5.16 & 5.17)''<br />
Image:5.14.jpg|''[https://cn.opendesktop.org/img/9/6/8/9/16a60e21b0ccc01a55a1b81b1f392ed2c474.jpg Cluster] (Plasma 5.14 & 5.15)<br />
Image:5.13.png|''[https://cn.opendesktop.org/img/f/f/4/f/bad5a585bed490feedea7325fe545b3d1691.png Kokkini] (Plasma 5.13)''<br />
Image:5.11.png|''[https://cn.opendesktop.org/img/a/4/b/6/5aae7f9d7ec198d3913da5544e4b0b4358eb.png Opal] (Plasma 5.11 & 5.12)''<br />
Image:5.10.png|''[https://cn.opendesktop.org/img/3/7/1/6/0d1b53eee747122bcb65744248ff4afc8920.png Cascade] (Plasma 5.10)''<br />
Image:5.9.png|''[https://cn.opendesktop.org/img/c/d/0/7/a389cad31cf53621ebc377c3a2f84be52899.png Canopée] (Plasma 5.9)''<br />
</gallery><br />
<br />
== Selection Process ==<br />
<br />
Judges for the competition are part of the KDE's Visual Design Group and other esteemed community members. At the end of the submission period, six finalists will be selected for a second round. Users that make it to this stage get a small prize from TUXEDO Computers. The second round will last one week. <br />
<br />
The selection team recognizes the need for selecting a quality image that will be used as a default wallpaper in Plasma 5.18 release. Images selected during the competition may need additional changes to attain this status. During the second round, participants may be asked for edits to their submissions to make stronger pieces. After the second round ends, the winning wallpaper will be selected. <br />
<br />
While there will only be one winning selection, other finalists may be included as optional wallpapers in Plasma 5.18, or used in future releases. The judges' decision is final.<br />
<br />
== Finalists Prizes ==<br />
<br />
[https://www.tuxedocomputers.com TUXEDO Computers] is sponsoring prizes for all the finalists who make it to the second round. The packages will vary, but they will all include:<br />
<br />
<br/><br />
<br />
# A KDE-branded baseball cap<br />
# A plush Tux<br />
# KDE stickers<br />
# A frozen glass coffee mug <br />
<br />
<br/><br />
<br />
== Grand Prize == <br />
The grand prize is an [https://www.tuxedocomputers.com/ibp14 InfinityBook Pro 14] sponsored by our friends at TUXEDO Computers.<br />
<br />
<b/><br />
It has: <br />
<br />
* Powerful Intel Core i7, 16GB of RAM and 500GB SSD<br />
* All-day battery capacity of 12 hours<br />
* Weight of just 1.4kg (3lbs) and thinness of 19mm (0.7in)<br />
<br />
<br/><br />
<br />
Naturally, it will come decked-out with the upcoming KDE Plasma 5.18 desktop, the winning wallpaper, and a bunch of great KDE software.<br />
<br />
<br/><br />
<br />
[[File:Txedo InfinityBookPro14 logo.png|800px|center]]<br />
<!--[[File:Tuxedo_computers.png|300px|center]]--><br />
<br />
== Help and Feedback ==<br />
<br />
You can ask the [[Get_Involved/design | VDG]] for help and feedback any time during the competition!<br />
Just join the [https://webchat.kde.org/#/room/#kde-vdg:kde.org #kde-vdg] channel on [[Matrix]] or the freenode [[Internet Relay Chat | IRC channel]] (which is bridged to the [https://telegram.me/vdgmainroom VDG] Telegram room, if you prefer [[Telegram]]).<br />
<br />
Also check out the discussion in the [https://forum.kde.org/viewforum.php?f=313 competition's subforum] to get tips and feedback.<br />
<br />
<br />
<br />
== Current Entries ==<br />
<br />
Start here!</div>Pontaoshttps://community.kde.org/index.php?title=KDE_Visual_Design_Group/Plasma_5.18_Wallpaper_Competition&diff=86978KDE Visual Design Group/Plasma 5.18 Wallpaper Competition2019-12-18T01:30:10Z<p>Pontaos: </p>
<hr />
<div>__NOTOC__<br />
<!--<br />
'''Submit your designs to [https://forum.kde.org/viewforum.php?f=xxx the subforum we have set up for the competition].'''<br />
--><br />
<br />
== Rules ==<br />
<br />
# The deadline for submissions is January 15th 2020, at midnight UTC time. The winning wallpaper will be selected on January 22nd 2020.<br />
# Your wallpaper must be original and created specifically for the contest.<br />
# Your wallpaper must be released to KDE under the CC-BY-SA-4.0 license.<br />
# You can submit up to 3 wallpapers.<br />
# Images must be in PNG format. <br />
# The source files used to create the wallpaper should be shared in a non-proprietary format, like an Inkscape-compatible SVG, .blend, .kra, .xfc, etc.<br />
# The minimum required size for wallpapers is 4K (3840x2160), although 5K (5120x2880) is preferred.<br />
# A phone-sized (1080x2280) wallpaper for Plasma Mobile can also be submitted.<br />
# Image files must be hosted on an external (non-KDE) site without compression. Two sites that host images without compression for free are [https://imgbox.com/ imgbox.com] and [https://postimages.org/ postimages.org]. You can also upload it to your preferred cloud storage provider, such as Google Drive, Dropbox, or OneDrive.<br />
# Any users that submit wallpapers that are racist, sexist, demeaning, or inappropriate in any way will be disqualified. Disqualifications and deletions are final and cannot be appealed.<br />
<br />
== Design Guidance & Suggestions ==<br />
<br />
# Consider making a wallpaper that provides a sense of continuity with the current "Ice Cold" wallpaper. Your wallpaper should feel like images on a timeline with Ice Cold.<br />
# Do not add the Plasma version number (5.18) into your wallpaper.<br />
# Any words or logos should not be simply overlaid on the wallpaper. If you add words or logos, integrate them into the design of the wallpaper.<br />
<br />
<br/><br />
<br />
The six following wallpapers, made by Ken Vermette and Santiago César, are used in previous versions of Plasma. You can find [https://store.kde.org/member/103267/ Ken Vermette's work on this page].<br />
<br />
<gallery mode="packed-hover"><br />
Image:5.16.jpg|''[https://community.kde.org/images.community/f/f4/5.16_large.png Ice Cold] (Plasma 5.16 & 5.17)''<br />
Image:5.14.jpg|''[https://cn.opendesktop.org/img/9/6/8/9/16a60e21b0ccc01a55a1b81b1f392ed2c474.jpg Cluster] (Plasma 5.14 & 5.15)<br />
Image:5.13.png|''[https://cn.opendesktop.org/img/f/f/4/f/bad5a585bed490feedea7325fe545b3d1691.png Kokkini] (Plasma 5.13)''<br />
Image:5.11.png|''[https://cn.opendesktop.org/img/a/4/b/6/5aae7f9d7ec198d3913da5544e4b0b4358eb.png Opal] (Plasma 5.11 & 5.12)''<br />
Image:5.10.png|''[https://cn.opendesktop.org/img/3/7/1/6/0d1b53eee747122bcb65744248ff4afc8920.png Cascade] (Plasma 5.10)''<br />
Image:5.9.png|''[https://cn.opendesktop.org/img/c/d/0/7/a389cad31cf53621ebc377c3a2f84be52899.png Canopée] (Plasma 5.9)''<br />
</gallery><br />
<br />
<br />
== Selection Process ==<br />
<br />
A jury of members in KDE's Visual Design Group and other KDE community members will judge submitted wallpapers. After the end of the given time for submissions, six finalists will be selected for a second round. Users that make it to this stage get a prize from Tuxedo Computers. The second round will last one week. In the second round, the judges may ask for tweaks to the wallpapers to make them even better. After the second round ends, the winning wallpaper will be selected. There will only be one winning wallpaper, but other wallpapers may be included as optional wallpapers in Plasma 5.18, or used in future releases. The jury's decision is final.<br />
<br />
== Prize ==<br />
<br />
For the finalists who make it to the second round, Tuxedo Computers has offered a prize. The packages will vary, but they will all include:<br />
# A KDE baseball cap<br />
# A plush Tux<br />
# KDE stickers<br />
# A frozen glass coffee mug <br />
<br />
The grand prize, also sponsored by our friends at Tuxedo Computers, is an InfinityBook Pro 14, featuring a powerful Intel Core i7, 16GB of RAM and 500GB SSD. It also features an all-day battery life of 12 hours. It weighs just 1.4kg (3lbs) and is 19mm (0.7in) thin. Naturally, it will come decked out with the upcoming KDE Plasma 5.18 desktop, the winning wallpaper, and a bunch of great software made by KDE. Check it out [https://www.tuxedocomputers.com/ibp14 here].<br />
[[File:38203_3.jpg|400px|center]]<br />
<br />
<br />
<br />
[[File:Tuxedo_computers.png|300px|center]]<br />
<br />
== Help and Feedback ==<br />
<br />
You can ask the [[Get_Involved/design | VDG]] for help and feedback any time during the competition!<br />
Just join the [https://webchat.kde.org/#/room/#kde-vdg:kde.org #kde-vdg] channel on [[Matrix]] or the freenode [[Internet Relay Chat | IRC channel]] (which is bridged to the [https://telegram.me/vdgmainroom VDG] Telegram room, if you prefer [[Telegram]]).<br />
<br />
Also check out the discussion in the [https://forum.kde.org/viewforum.php?f=312 competition's subforum] to get tips and feedback.<br />
<br />
<br />
<br />
== Current Entries ==<br />
<br />
Start here!</div>Pontaoshttps://community.kde.org/index.php?title=KDE_Visual_Design_Group/Plasma_5.18_Wallpaper_Competition&diff=86977KDE Visual Design Group/Plasma 5.18 Wallpaper Competition2019-12-18T01:29:30Z<p>Pontaos: </p>
<hr />
<div>__NOTOC__<br />
<!--<br />
'''Submit your designs to [https://forum.kde.org/viewforum.php?f=xxx the subforum we have set up for the competition].'''<br />
--><br />
<br />
== Rules ==<br />
<br />
# The deadline for submissions is January 15th 2020, at midnight UTC time. The winning wallpaper will be selected on January 22nd 2020.<br />
# Your wallpaper must be original and created specifically for the contest.<br />
# Your wallpaper must be released to KDE under the CC-BY-SA-4.0 license.<br />
# You can submit up to 3 wallpapers.<br />
# Images must be in PNG format. <br />
# The source files used to create the wallpaper should be shared in a non-proprietary format, like an Inkscape-compatible SVG, .blend, .kra, .xfc, etc.<br />
# The minimum required size for wallpapers is 4K (3840x2160), although 5K (5120x2880) is preferred.<br />
# A phone-sized (1080x2280) wallpaper for Plasma Mobile can also be submitted.<br />
# Image files must be hosted on an external (non-KDE) site without compression. Sites that host images without compression for free are [https://imgbox.com/ imgbox], [https://postimages.org/ postimages]. You can also upload it to your preferred cloud storage, such as Google Drive, Dropbox, or OneDrive.<br />
# Any users that submit wallpapers that are racist, sexist, demeaning, or inappropriate in any way will be disqualified. Disqualifications and deletions are final and cannot be appealed.<br />
<br />
== Design Guidance & Suggestions ==<br />
<br />
# Consider making a wallpaper that provides a sense of continuity with the current "Ice Cold" wallpaper. Your wallpaper should feel like images on a timeline with Ice Cold.<br />
# Do not add the Plasma version number (5.18) into your wallpaper.<br />
# Any words or logos should not be simply overlaid on the wallpaper. If you add words or logos, integrate them into the design of the wallpaper.<br />
<br />
<br/><br />
<br />
The six following wallpapers, made by Ken Vermette and Santiago César, are used in previous versions of Plasma. You can find [https://store.kde.org/member/103267/ Ken Vermette's work on this page].<br />
<br />
<gallery mode="packed-hover"><br />
Image:5.16.jpg|''[https://community.kde.org/images.community/f/f4/5.16_large.png Ice Cold] (Plasma 5.16 & 5.17)''<br />
Image:5.14.jpg|''[https://cn.opendesktop.org/img/9/6/8/9/16a60e21b0ccc01a55a1b81b1f392ed2c474.jpg Cluster] (Plasma 5.14 & 5.15)<br />
Image:5.13.png|''[https://cn.opendesktop.org/img/f/f/4/f/bad5a585bed490feedea7325fe545b3d1691.png Kokkini] (Plasma 5.13)''<br />
Image:5.11.png|''[https://cn.opendesktop.org/img/a/4/b/6/5aae7f9d7ec198d3913da5544e4b0b4358eb.png Opal] (Plasma 5.11 & 5.12)''<br />
Image:5.10.png|''[https://cn.opendesktop.org/img/3/7/1/6/0d1b53eee747122bcb65744248ff4afc8920.png Cascade] (Plasma 5.10)''<br />
Image:5.9.png|''[https://cn.opendesktop.org/img/c/d/0/7/a389cad31cf53621ebc377c3a2f84be52899.png Canopée] (Plasma 5.9)''<br />
</gallery><br />
<br />
<br />
== Selection Process ==<br />
<br />
A jury of members in KDE's Visual Design Group and other KDE community members will judge submitted wallpapers. After the end of the given time for submissions, six finalists will be selected for a second round. Users that make it to this stage get a prize from Tuxedo Computers. The second round will last one week. In the second round, the judges may ask for tweaks to the wallpapers to make them even better. After the second round ends, the winning wallpaper will be selected. There will only be one winning wallpaper, but other wallpapers may be included as optional wallpapers in Plasma 5.18, or used in future releases. The jury's decision is final.<br />
<br />
== Prize ==<br />
<br />
For the finalists who make it to the second round, Tuxedo Computers has offered a prize. The packages will vary, but they will all include:<br />
# A KDE baseball cap<br />
# A plush Tux<br />
# KDE stickers<br />
# A frozen glass coffee mug <br />
<br />
The grand prize, also sponsored by our friends at Tuxedo Computers, is an InfinityBook Pro 14, featuring a powerful Intel Core i7, 16GB of RAM and 500GB SSD. It also features an all-day battery life of 12 hours. It weighs just 1.4kg (3lbs) and is 19mm (0.7in) thin. Naturally, it will come decked out with the upcoming KDE Plasma 5.18 desktop, the winning wallpaper, and a bunch of great software made by KDE. Check it out [https://www.tuxedocomputers.com/ibp14 here].<br />
[[File:38203_3.jpg|400px|center]]<br />
<br />
<br />
<br />
[[File:Tuxedo_computers.png|300px|center]]<br />
<br />
== Help and Feedback ==<br />
<br />
You can ask the [[Get_Involved/design | VDG]] for help and feedback any time during the competition!<br />
Just join the [https://webchat.kde.org/#/room/#kde-vdg:kde.org #kde-vdg] channel on [[Matrix]] or the freenode [[Internet Relay Chat | IRC channel]] (which is bridged to the [https://telegram.me/vdgmainroom VDG] Telegram room, if you prefer [[Telegram]]).<br />
<br />
Also check out the discussion in the [https://forum.kde.org/viewforum.php?f=312 competition's subforum] to get tips and feedback.<br />
<br />
<br />
<br />
== Current Entries ==<br />
<br />
Start here!</div>Pontaoshttps://community.kde.org/index.php?title=KDE_Visual_Design_Group/Plasma_5.18_Wallpaper_Competition&diff=86976KDE Visual Design Group/Plasma 5.18 Wallpaper Competition2019-12-18T01:29:02Z<p>Pontaos: </p>
<hr />
<div>__NOTOC__<br />
<!--<br />
'''Submit your designs to [https://forum.kde.org/viewforum.php?f=xxx the subforum we have set up for the competition].'''<br />
--><br />
<br />
== Rules ==<br />
<br />
# The deadline for submissions is January 15th 2020, at midnight UTC time. The winning wallpaper will be selected on January 22nd 2020.<br />
# Your wallpaper must be original and created specifically for the contest.<br />
# Your wallpaper must be released to KDE under the CC-BY-SA-4.0 license.<br />
# You can submit up to 3 wallpapers.<br />
# Images must be in PNG format. <br />
# The source files used to create the wallpaper should be shared in a non-proprietary format, like an Inkscape-compatible SVG, .blend, .kra, .xfc, etc.<br />
# The minimum required size for wallpapers is 4K (3840x2160), although 5K (5120x2880) is preferred.<br />
# A phone-sized (1080x2280) wallpaper for Plasma Mobile can also be submitted.<br />
# Image files must be hosted on an external (non-KDE) site without compression. Sites that host images without compression for free are [https://imgbox.com/ imgbox], [https://postimages.org/ postimages]. You can also upload it to your preferred cloud storage, such as Google Drive, Dropbox, or OneDrive.<br />
# Any users that submit wallpapers that are racist, sexist, demeaning, or inappropriate in any way will be disqualified. Disqualifications and deletions are final and cannot be appealed.<br />
<br />
== Design Guidance & Suggestions ==<br />
<br />
# Consider making a wallpaper that provides a sense of continuity with the current "Ice Cold" wallpaper. Your wallpaper should feel like images on a timeline with Ice Cold.<br />
# Do not add the Plasma version number (5.18) into your wallpaper.<br />
# Any words or logos should not be simply overlayed on the wallpaper. If you add words or logos, integrate them into the design of the wallpaper.<br />
<br />
<br/><br />
<br />
The six following wallpapers, made by Ken Vermette and Santiago César, are used in previous versions of Plasma. You can find [https://store.kde.org/member/103267/ Ken Vermette's work on this page].<br />
<br />
<gallery mode="packed-hover"><br />
Image:5.16.jpg|''[https://community.kde.org/images.community/f/f4/5.16_large.png Ice Cold] (Plasma 5.16 & 5.17)''<br />
Image:5.14.jpg|''[https://cn.opendesktop.org/img/9/6/8/9/16a60e21b0ccc01a55a1b81b1f392ed2c474.jpg Cluster] (Plasma 5.14 & 5.15)<br />
Image:5.13.png|''[https://cn.opendesktop.org/img/f/f/4/f/bad5a585bed490feedea7325fe545b3d1691.png Kokkini] (Plasma 5.13)''<br />
Image:5.11.png|''[https://cn.opendesktop.org/img/a/4/b/6/5aae7f9d7ec198d3913da5544e4b0b4358eb.png Opal] (Plasma 5.11 & 5.12)''<br />
Image:5.10.png|''[https://cn.opendesktop.org/img/3/7/1/6/0d1b53eee747122bcb65744248ff4afc8920.png Cascade] (Plasma 5.10)''<br />
Image:5.9.png|''[https://cn.opendesktop.org/img/c/d/0/7/a389cad31cf53621ebc377c3a2f84be52899.png Canopée] (Plasma 5.9)''<br />
</gallery><br />
<br />
<br />
== Selection Process ==<br />
<br />
A jury of members in KDE's Visual Design Group and other KDE community members will judge submitted wallpapers. After the end of the given time for submissions, six finalists will be selected for a second round. Users that make it to this stage get a prize from Tuxedo Computers. The second round will last one week. In the second round, the judges may ask for tweaks to the wallpapers to make them even better. After the second round ends, the winning wallpaper will be selected. There will only be one winning wallpaper, but other wallpapers may be included as optional wallpapers in Plasma 5.18, or used in future releases. The jury's decision is final.<br />
<br />
== Prize ==<br />
<br />
For the finalists who make it to the second round, Tuxedo Computers has offered a prize. The packages will vary, but they will all include:<br />
# A KDE baseball cap<br />
# A plush Tux<br />
# KDE stickers<br />
# A frozen glass coffee mug <br />
<br />
The grand prize, also sponsored by our friends at Tuxedo Computers, is an InfinityBook Pro 14, featuring a powerful Intel Core i7, 16GB of RAM and 500GB SSD. It also features an all-day battery life of 12 hours. It weighs just 1.4kg (3lbs) and is 19mm (0.7in) thin. Naturally, it will come decked out with the upcoming KDE Plasma 5.18 desktop, the winning wallpaper, and a bunch of great software made by KDE. Check it out [https://www.tuxedocomputers.com/ibp14 here].<br />
[[File:38203_3.jpg|400px|center]]<br />
<br />
<br />
<br />
[[File:Tuxedo_computers.png|300px|center]]<br />
<br />
== Help and Feedback ==<br />
<br />
You can ask the [[Get_Involved/design | VDG]] for help and feedback any time during the competition!<br />
Just join the [https://webchat.kde.org/#/room/#kde-vdg:kde.org #kde-vdg] channel on [[Matrix]] or the freenode [[Internet Relay Chat | IRC channel]] (which is bridged to the [https://telegram.me/vdgmainroom VDG] Telegram room, if you prefer [[Telegram]]).<br />
<br />
Also check out the discussion in the [https://forum.kde.org/viewforum.php?f=312 competition's subforum] to get tips and feedback.<br />
<br />
<br />
<br />
== Current Entries ==<br />
<br />
Start here!</div>Pontaoshttps://community.kde.org/index.php?title=Incubator/Projects/Ikona&diff=85791Incubator/Projects/Ikona2019-08-23T14:55:46Z<p>Pontaos: /* Incubating */</p>
<hr />
<div>= Ikona =<br />
<br />
'''Sponsor:''' Albert Astals Cid<br />
<br />
Ikona is a an application designed to be a companion to designers when designing icons. It shows icons in about every way a designer could want, as well as giving them some extra tools to help with icons.<br />
<br />
== Team ==<br />
<br />
List the people committed to the project and actively working on it.<br />
<br />
- Carson Black [pontaos/appadeia]<br />
<br />
== Manifesto Compliance Plan ==<br />
<br />
List the actions planned to get in compliance with the manifesto. <br />
<br />
=== Values ===<br />
<br />
==== Open Governance ====<br />
- Find a chatroom appropriate for discussion about Ikona<br />
<br />
==== Free Software ====<br />
- Ikona is already licensed under GPLv2 with a "or later" clause. <br />
<br />
- It will migrate to KDE's GitLab.<br />
<br />
==== Inclusivity ====<br />
- Anyone is free to contribute, and anyone can use it.<br />
<br />
==== Innovation ====<br />
- Ikona offers extra features on top of just a plain icon viewer. These are curated specifically to assist designers, such as offering an integrated Breeze color palette.<br />
<br />
==== Common Ownership ====<br />
- Anyone can help out, anyone can fork it and make their own Ikona.<br />
<br />
==== End-User Focus ====<br />
- Ikona is tailored to help designers, the target userbase, without getting in their way.<br />
<br />
== Sponsor Checklists ==<br />
<br />
=== Candidate ready ===<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Status<br />
! Description<br />
! width=250 | Notes<br />
|-<br />
{{FeatureDone|Project description| see above}}<br />
{{FeatureDone|Project team| see above}}<br />
{{FeatureDone|Manifesto compliance plan|see above}}<br />
|}<br />
<br />
=== Incubating ===<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Status<br />
! Description<br />
! width=250 | Notes<br />
|-<br />
{{FeatureDone|Repository and code available (in playground)|https://invent.kde.org/kde/ikona}}<br />
{{FeatureTodo|Mailing list available (if applicable)|...}}<br />
{{FeatureTodo|Website available (if applicable)| ...}}<br />
{{FeatureTodo|Active community| ...}}<br />
{{FeatureTodo|Manifesto compliance| ...}}<br />
|}</div>Pontaoshttps://community.kde.org/index.php?title=Incubator/Projects/Ikona&diff=85790Incubator/Projects/Ikona2019-08-23T14:54:03Z<p>Pontaos: /* Incubating */</p>
<hr />
<div>= Ikona =<br />
<br />
'''Sponsor:''' Albert Astals Cid<br />
<br />
Ikona is a an application designed to be a companion to designers when designing icons. It shows icons in about every way a designer could want, as well as giving them some extra tools to help with icons.<br />
<br />
== Team ==<br />
<br />
List the people committed to the project and actively working on it.<br />
<br />
- Carson Black [pontaos/appadeia]<br />
<br />
== Manifesto Compliance Plan ==<br />
<br />
List the actions planned to get in compliance with the manifesto. <br />
<br />
=== Values ===<br />
<br />
==== Open Governance ====<br />
- Find a chatroom appropriate for discussion about Ikona<br />
<br />
==== Free Software ====<br />
- Ikona is already licensed under GPLv2 with a "or later" clause. <br />
<br />
- It will migrate to KDE's GitLab.<br />
<br />
==== Inclusivity ====<br />
- Anyone is free to contribute, and anyone can use it.<br />
<br />
==== Innovation ====<br />
- Ikona offers extra features on top of just a plain icon viewer. These are curated specifically to assist designers, such as offering an integrated Breeze color palette.<br />
<br />
==== Common Ownership ====<br />
- Anyone can help out, anyone can fork it and make their own Ikona.<br />
<br />
==== End-User Focus ====<br />
- Ikona is tailored to help designers, the target userbase, without getting in their way.<br />
<br />
== Sponsor Checklists ==<br />
<br />
=== Candidate ready ===<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Status<br />
! Description<br />
! width=250 | Notes<br />
|-<br />
{{FeatureDone|Project description| see above}}<br />
{{FeatureDone|Project team| see above}}<br />
{{FeatureDone|Manifesto compliance plan|see above}}<br />
|}<br />
<br />
=== Incubating ===<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Status<br />
! Description<br />
! width=250 | Notes<br />
|-<br />
{{FeatureDone|Repository and code available (in playground)|...}}<br />
{{FeatureTodo|Mailing list available (if applicable)|...}}<br />
{{FeatureTodo|Website available (if applicable)| ...}}<br />
{{FeatureTodo|Active community| ...}}<br />
{{FeatureTodo|Manifesto compliance| ...}}<br />
|}</div>Pontaoshttps://community.kde.org/index.php?title=Incubator/Projects/Ikona&diff=85720Incubator/Projects/Ikona2019-08-21T20:53:48Z<p>Pontaos: /* Candidate ready */</p>
<hr />
<div>= Ikona =<br />
<br />
'''Sponsor:''' Albert Astals Cid<br />
<br />
Ikona is a an application designed to be a companion to designers when designing icons. It shows icons in about every way a designer could want, as well as giving them some extra tools to help with icons.<br />
<br />
== Team ==<br />
<br />
List the people committed to the project and actively working on it.<br />
<br />
- Carson Black [pontaos/appadeia]<br />
<br />
== Manifesto Compliance Plan ==<br />
<br />
List the actions planned to get in compliance with the manifesto. <br />
<br />
=== Values ===<br />
<br />
==== Open Governance ====<br />
- Find a chatroom appropriate for discussion about Ikona<br />
<br />
==== Free Software ====<br />
- Ikona is already licensed under GPLv2 with a "or later" clause. <br />
<br />
- It will migrate to KDE's GitLab.<br />
<br />
==== Inclusivity ====<br />
- Anyone is free to contribute, and anyone can use it.<br />
<br />
==== Innovation ====<br />
- Ikona offers extra features on top of just a plain icon viewer. These are curated specifically to assist designers, such as offering an integrated Breeze color palette.<br />
<br />
==== Common Ownership ====<br />
- Anyone can help out, anyone can fork it and make their own Ikona.<br />
<br />
==== End-User Focus ====<br />
- Ikona is tailored to help designers, the target userbase, without getting in their way.<br />
<br />
== Sponsor Checklists ==<br />
<br />
=== Candidate ready ===<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Status<br />
! Description<br />
! width=250 | Notes<br />
|-<br />
{{FeatureDone|Project description| see above}}<br />
{{FeatureDone|Project team| see above}}<br />
{{FeatureDone|Manifesto compliance plan|see above}}<br />
|}<br />
<br />
=== Incubating ===<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Status<br />
! Description<br />
! width=250 | Notes<br />
|-<br />
{{FeatureTodo|Repository and code available (in playground)|...}}<br />
{{FeatureTodo|Mailing list available (if applicable)|...}}<br />
{{FeatureTodo|Website available (if applicable)| ...}}<br />
{{FeatureTodo|Active community| ...}}<br />
{{FeatureTodo|Manifesto compliance| ...}}<br />
|}</div>Pontaoshttps://community.kde.org/index.php?title=Incubator/Projects/Ikona&diff=85535Incubator/Projects/Ikona2019-08-14T12:47:35Z<p>Pontaos: /* Open Governance */</p>
<hr />
<div>= Ikona =<br />
<br />
'''Sponsor:''' Albert Astals Cid<br />
<br />
Ikona is a an application designed to be a companion to designers when designing icons. It shows icons in about every way a designer could want, as well as giving them some extra tools to help with icons.<br />
<br />
== Team ==<br />
<br />
List the people committed to the project and actively working on it.<br />
<br />
- Carson Black [pontaos/appadeia]<br />
<br />
== Manifesto Compliance Plan ==<br />
<br />
List the actions planned to get in compliance with the manifesto. <br />
<br />
=== Values ===<br />
<br />
==== Open Governance ====<br />
- Find a chatroom appropriate for discussion about Ikona<br />
<br />
==== Free Software ====<br />
- Ikona is already licensed under GPLv2 with a "or later" clause. <br />
<br />
- It will migrate to KDE's GitLab.<br />
<br />
==== Inclusivity ====<br />
- Anyone is free to contribute, and anyone can use it.<br />
<br />
==== Innovation ====<br />
- Ikona offers extra features on top of just a plain icon viewer. These are curated specifically to assist designers, such as offering an integrated Breeze color palette.<br />
<br />
==== Common Ownership ====<br />
- Anyone can help out, anyone can fork it and make their own Ikona.<br />
<br />
==== End-User Focus ====<br />
- Ikona is tailored to help designers, the target userbase, without getting in their way.<br />
<br />
== Sponsor Checklists ==<br />
<br />
=== Candidate ready ===<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Status<br />
! Description<br />
! width=250 | Notes<br />
|-<br />
{{FeatureDone|Project description| see above}}<br />
{{FeatureDone|Project team| see above}}<br />
{{FeatureTodo|Manifesto compliance plan|see above}}<br />
|}<br />
<br />
=== Incubating ===<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Status<br />
! Description<br />
! width=250 | Notes<br />
|-<br />
{{FeatureTodo|Repository and code available (in playground)|...}}<br />
{{FeatureTodo|Mailing list available (if applicable)|...}}<br />
{{FeatureTodo|Website available (if applicable)| ...}}<br />
{{FeatureTodo|Active community| ...}}<br />
{{FeatureTodo|Manifesto compliance| ...}}<br />
|}</div>Pontaoshttps://community.kde.org/index.php?title=Incubator/Projects/Ikona&diff=85467Incubator/Projects/Ikona2019-08-08T22:38:17Z<p>Pontaos: /* Values */</p>
<hr />
<div>= Ikona =<br />
<br />
'''Sponsor:''' Albert Astals Cid<br />
<br />
Ikona is a an application designed to be a companion to designers when designing icons. It shows icons in about every way a designer could want, as well as giving them some extra tools to help with icons.<br />
<br />
== Team ==<br />
<br />
List the people committed to the project and actively working on it.<br />
<br />
- Carson Black [pontaos/appadeia]<br />
<br />
== Manifesto Compliance Plan ==<br />
<br />
List the actions planned to get in compliance with the manifesto. <br />
<br />
=== Values ===<br />
<br />
==== Open Governance ====<br />
- Obtain chatrooms specifically for Ikona (currently openSUSE Artwork is where most discussion takes place)<br />
<br />
==== Free Software ====<br />
- Ikona is already licensed under GPLv2 with a "or later" clause. <br />
<br />
- It will migrate to KDE's GitLab.<br />
<br />
==== Inclusivity ====<br />
- Anyone is free to contribute, and anyone can use it.<br />
<br />
==== Innovation ====<br />
- Ikona offers extra features on top of just a plain icon viewer. These are curated specifically to assist designers, such as offering an integrated Breeze color palette.<br />
<br />
==== Common Ownership ====<br />
- Anyone can help out, anyone can fork it and make their own Ikona.<br />
<br />
==== End-User Focus ====<br />
- Ikona is tailored to help designers, the target userbase, without getting in their way.<br />
<br />
== Sponsor Checklists ==<br />
<br />
=== Candidate ready ===<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Status<br />
! Description<br />
! width=250 | Notes<br />
|-<br />
{{FeatureDone|Project description| see above}}<br />
{{FeatureTodo|Project team| see above}}<br />
{{FeatureTodo|Manifesto compliance plan|see above}}<br />
|}<br />
<br />
=== Incubating ===<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Status<br />
! Description<br />
! width=250 | Notes<br />
|-<br />
{{FeatureTodo|Repository and code available (in playground)|...}}<br />
{{FeatureTodo|Mailing list available (if applicable)|...}}<br />
{{FeatureTodo|Website available (if applicable)| ...}}<br />
{{FeatureTodo|Active community| ...}}<br />
{{FeatureTodo|Manifesto compliance| ...}}<br />
|}</div>Pontaoshttps://community.kde.org/index.php?title=Incubator/Projects/Ikona&diff=85466Incubator/Projects/Ikona2019-08-08T22:28:14Z<p>Pontaos: /* Free Software */</p>
<hr />
<div>= Ikona =<br />
<br />
'''Sponsor:''' Albert Astals Cid<br />
<br />
Ikona is a an application designed to be a companion to designers when designing icons. It shows icons in about every way a designer could want, as well as giving them some extra tools to help with icons.<br />
<br />
== Team ==<br />
<br />
List the people committed to the project and actively working on it.<br />
<br />
- Carson Black [pontaos/appadeia]<br />
<br />
== Manifesto Compliance Plan ==<br />
<br />
List the actions planned to get in compliance with the manifesto. <br />
<br />
=== Values ===<br />
<br />
==== Open Governance ====<br />
- Obtain chatrooms specifically for Ikona (currently openSUSE Artwork is where most discussion takes place)<br />
<br />
==== Free Software ====<br />
- Ikona is already licensed under GPLv2 with a "or later" clause. <br />
<br />
- It should probably migrate to an OSS platform (platform undecided, most likely Gitlab)<br />
<br />
==== Inclusivity ====<br />
- Anyone is free to contribute, and anyone can use it.<br />
<br />
==== Innovation ====<br />
- Ikona offers extra features on top of just a plain icon viewer. These are curated specifically to assist designers, such as offering an integrated Breeze color palette.<br />
<br />
==== Common Ownership ====<br />
- Anyone can help out, anyone can fork it and make their own Ikona.<br />
<br />
==== End-User Focus ====<br />
- Ikona is tailored to help designers, the target userbase, without getting in their way.<br />
<br />
TODO<br />
<br />
== Sponsor Checklists ==<br />
<br />
=== Candidate ready ===<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Status<br />
! Description<br />
! width=250 | Notes<br />
|-<br />
{{FeatureDone|Project description| see above}}<br />
{{FeatureTodo|Project team| see above}}<br />
{{FeatureTodo|Manifesto compliance plan|see above}}<br />
|}<br />
<br />
=== Incubating ===<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Status<br />
! Description<br />
! width=250 | Notes<br />
|-<br />
{{FeatureTodo|Repository and code available (in playground)|...}}<br />
{{FeatureTodo|Mailing list available (if applicable)|...}}<br />
{{FeatureTodo|Website available (if applicable)| ...}}<br />
{{FeatureTodo|Active community| ...}}<br />
{{FeatureTodo|Manifesto compliance| ...}}<br />
|}</div>Pontaoshttps://community.kde.org/index.php?title=Incubator/Projects/Ikona&diff=85465Incubator/Projects/Ikona2019-08-08T22:26:51Z<p>Pontaos: /* Team */</p>
<hr />
<div>= Ikona =<br />
<br />
'''Sponsor:''' Albert Astals Cid<br />
<br />
Ikona is a an application designed to be a companion to designers when designing icons. It shows icons in about every way a designer could want, as well as giving them some extra tools to help with icons.<br />
<br />
== Team ==<br />
<br />
List the people committed to the project and actively working on it.<br />
<br />
- Carson Black [pontaos/appadeia]<br />
<br />
== Manifesto Compliance Plan ==<br />
<br />
List the actions planned to get in compliance with the manifesto. <br />
<br />
=== Values ===<br />
<br />
==== Open Governance ====<br />
- Obtain chatrooms specifically for Ikona (currently openSUSE Artwork is where most discussion takes place)<br />
<br />
==== Free Software ====<br />
- Ikona is already licensed under GPLv2 with a "or later" clause.<br />
- It should probably migrate to an OSS platform (platform undecided, most likely Gitlab)<br />
<br />
==== Inclusivity ====<br />
- Anyone is free to contribute, and anyone can use it.<br />
<br />
==== Innovation ====<br />
- Ikona offers extra features on top of just a plain icon viewer. These are curated specifically to assist designers, such as offering an integrated Breeze color palette.<br />
<br />
==== Common Ownership ====<br />
- Anyone can help out, anyone can fork it and make their own Ikona.<br />
<br />
==== End-User Focus ====<br />
- Ikona is tailored to help designers, the target userbase, without getting in their way.<br />
<br />
TODO<br />
<br />
== Sponsor Checklists ==<br />
<br />
=== Candidate ready ===<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Status<br />
! Description<br />
! width=250 | Notes<br />
|-<br />
{{FeatureDone|Project description| see above}}<br />
{{FeatureTodo|Project team| see above}}<br />
{{FeatureTodo|Manifesto compliance plan|see above}}<br />
|}<br />
<br />
=== Incubating ===<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Status<br />
! Description<br />
! width=250 | Notes<br />
|-<br />
{{FeatureTodo|Repository and code available (in playground)|...}}<br />
{{FeatureTodo|Mailing list available (if applicable)|...}}<br />
{{FeatureTodo|Website available (if applicable)| ...}}<br />
{{FeatureTodo|Active community| ...}}<br />
{{FeatureTodo|Manifesto compliance| ...}}<br />
|}</div>Pontaoshttps://community.kde.org/index.php?title=Incubator/Projects/Ikona&diff=85464Incubator/Projects/Ikona2019-08-08T22:26:21Z<p>Pontaos: /* Manifesto Compliance Plan */</p>
<hr />
<div>= Ikona =<br />
<br />
'''Sponsor:''' Albert Astals Cid<br />
<br />
Ikona is a an application designed to be a companion to designers when designing icons. It shows icons in about every way a designer could want, as well as giving them some extra tools to help with icons.<br />
<br />
== Team ==<br />
<br />
List the people committed to the project and actively working on it.<br />
<br />
TODO<br />
<br />
== Manifesto Compliance Plan ==<br />
<br />
List the actions planned to get in compliance with the manifesto. <br />
<br />
=== Values ===<br />
<br />
==== Open Governance ====<br />
- Obtain chatrooms specifically for Ikona (currently openSUSE Artwork is where most discussion takes place)<br />
<br />
==== Free Software ====<br />
- Ikona is already licensed under GPLv2 with a "or later" clause.<br />
- It should probably migrate to an OSS platform (platform undecided, most likely Gitlab)<br />
<br />
==== Inclusivity ====<br />
- Anyone is free to contribute, and anyone can use it.<br />
<br />
==== Innovation ====<br />
- Ikona offers extra features on top of just a plain icon viewer. These are curated specifically to assist designers, such as offering an integrated Breeze color palette.<br />
<br />
==== Common Ownership ====<br />
- Anyone can help out, anyone can fork it and make their own Ikona.<br />
<br />
==== End-User Focus ====<br />
- Ikona is tailored to help designers, the target userbase, without getting in their way.<br />
<br />
TODO<br />
<br />
== Sponsor Checklists ==<br />
<br />
=== Candidate ready ===<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Status<br />
! Description<br />
! width=250 | Notes<br />
|-<br />
{{FeatureDone|Project description| see above}}<br />
{{FeatureTodo|Project team| see above}}<br />
{{FeatureTodo|Manifesto compliance plan|see above}}<br />
|}<br />
<br />
=== Incubating ===<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Status<br />
! Description<br />
! width=250 | Notes<br />
|-<br />
{{FeatureTodo|Repository and code available (in playground)|...}}<br />
{{FeatureTodo|Mailing list available (if applicable)|...}}<br />
{{FeatureTodo|Website available (if applicable)| ...}}<br />
{{FeatureTodo|Active community| ...}}<br />
{{FeatureTodo|Manifesto compliance| ...}}<br />
|}</div>Pontaoshttps://community.kde.org/index.php?title=Incubator/Projects/Ikona&diff=85462Incubator/Projects/Ikona2019-08-08T22:05:30Z<p>Pontaos: /* Ikona */</p>
<hr />
<div>= Ikona =<br />
<br />
'''Sponsor:''' Albert Astals Cid<br />
<br />
Ikona is a an application designed to be a companion to designers when designing icons. It shows icons in about every way a designer could want, as well as giving them some extra tools to help with icons.<br />
<br />
== Team ==<br />
<br />
List the people committed to the project and actively working on it.<br />
<br />
TODO<br />
<br />
== Manifesto Compliance Plan ==<br />
<br />
List the actions planned to get in compliance with the manifesto. <br />
<br />
=== Values ===<br />
<br />
==== Open Governance ====<br />
TODO<br />
<br />
==== Free Software ====<br />
TODO<br />
<br />
==== Inclusivity ====<br />
TODO<br />
<br />
==== Innovation ====<br />
TODO<br />
<br />
==== Common Ownership ====<br />
TODO<br />
<br />
==== End-User Focus ====<br />
TODO<br />
<br />
== Sponsor Checklists ==<br />
<br />
=== Candidate ready ===<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Status<br />
! Description<br />
! width=250 | Notes<br />
|-<br />
{{FeatureTodo|Project description| see above}}<br />
{{FeatureTodo|Project team| see above}}<br />
{{FeatureTodo|Manifesto compliance plan|see above}}<br />
|}<br />
<br />
=== Incubating ===<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Status<br />
! Description<br />
! width=250 | Notes<br />
|-<br />
{{FeatureTodo|Repository and code available (in playground)|...}}<br />
{{FeatureTodo|Mailing list available (if applicable)|...}}<br />
{{FeatureTodo|Website available (if applicable)| ...}}<br />
{{FeatureTodo|Active community| ...}}<br />
{{FeatureTodo|Manifesto compliance| ...}}<br />
|}</div>Pontaos