SoK/Ideas/2022

Konqi is giving a lesson!

Ideas

Information for students

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.

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!

If there is no specific contact given in the idea, you can ask questions on the general KDE development list [email protected]. See the KDE mailing lists page for information on available mailing lists and how to subscribe.

You need to submit your proposal to season.kde.org before the deadline.

Sample project

Project type: Coding / Web Development / Promo / Translation

Brief explanation:

Expected results:

Knowledge Prerequisite:

Mentor:

When adding an idea to this section, please try to include the following data:

• if the application is not widely known, a description of what it does and where its code lives
• a brief explanation
• the expected results
• pre-requisites for working on your project
• if applicable, links to more information or discussions
• mailing list or IRC channel for your application/library/module
• your name and email address for contact (if you're willing to be a mentor)

If you are not a developer but have a good idea for a proposal, get in contact with relevant developers first.

Ideas

Your Own Idea: Something that you're totally excited about

Project type: Coding / Web Development / Promo / Translation

Brief explanation: Do you have an awesome idea you want to work on with KDE but it isn't 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.

Expected results: Something you and KDE love

Knowledge Prerequisite: Probably C++ and Qt, but it depends on your project

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.

Plasma Sound Design

Project type: Sound Design

Brief explanation: The goal of this task is to create a new sound theme that will be used on KDE Plasma for many purposes. For more information, please check this task

Expected results: At the end we expect Plasma to have a sound theme for many desktop actions, including but not limited to notifications, startup/shutdown jingle, alerts, and so on. We need 20 sounds in total, and most of them, with the exclusion of startup/shutdown jingles, should be about 1 second long.

Knowledge Prerequisite: Knowledge in sound design and/or music production. You'll also need to know how to use any FLOSS (Free/Libre and Open Source Software) music production software of your liking.

Mentor: Guilherme Marçal Silva and Noah Davis - You can contact your mentors on this Phabricator task. There you can see more details of what you have to do.

KDE Apps packaging as Flatpak for Flathub

Project type: Coding and Packaging

Brief explanation: We currently have Flatpaks recipes for a lot of KDE Apps (https://invent.kde.org/packaging/flatpak-kde-applications) but only some of them are available on Flathub (https://flathub.org/apps/search/org.kde). You will work on submitting missing KDE Apps to Flathub while fixing the issues that come up during the submission review. Once you've understood the process better, you may start working on tooling to help maintain KDE Apps as Flatpaks in both Flathub and KDE CI/CD infrastructure in GitLab.

Expected results: Submit a couple of KDE Apps to Flathub and develop fixes for the issues found during review.

Knowledge Prerequisite: C++, Qt, CMake, Bash, Python (basic knowledge in at least two of those is recommended)

Mentor: Timothée Ravier. Reach out to https://matrix.to/#/#flatpak:kde.org.

Permission management for Flatpak Apps in Discover

Project type: Coding and design

Brief explanation: We currently have Flatpak support in Discover. Flatpaks can have access to files, sockets, etc. However, those permissions are not currently displayed or manageable from the user interface. We thus want to add support for managing Flatpak application permissions directly in the Discover user interface. This project would look a lot like what's currently possible with Flatseal (See https://github.com/tchx84/flatseal and https://flathub.org/apps/details/com.github.tchx84.Flatseal).

Expected results: Installing a Flatpak application prompts the user for comfirmation for requested permissions and allow them to manage given permissions after installation.

Knowledge Prerequisite: C++, Qt, CMake (basic knowledge in C++ and Qt is recommended)

Mentor: Timothée Ravier, Aleix Pol. Reach out to https://matrix.to/#/#plasma-discover:kde.org.