SoK/Ideas/2023

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.

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.

Accessibility: Work on improving the accessibility of {Kalendar, NeoChat, ...} or another QML app

Project type: Coding

Brief explanation: Accessibility is one of the goal for the next two years. A part of this task is to improve one app. Work on keyboard navigation, make sure a scree reader user is able to use the app, ...

Expected results: More accessibility

Knowledge Prerequisite: QML knowledge is recommended and willingness to learn

Mentor: Carl Schwan #kde-accessibility:kde:org on matrix

Accessibility: Work on improving the accessibility of KDE's websites

Project type: Website maintenance

Brief explanation: Many of KDE's website lack even the most basic accessibility features, such as alt descriptions for images or the correct rendering on small screens, like thos found on mobile phones. The candidate will be required to comb KDE's mains sites (to start with) and add accessibility features to bring them up to spec according to the accessibility guidelines laid out in the latest versions of WCAG.

Expected results: Fully accessible websites for our visitors.

Knowledge Prerequisites: HTML, CSS, Hugo, GitLab.

Mentors: Paul Brown, Aniqa Khokhar at the Promo channel on Matrix.