SoK/Ideas/2024: Difference between revisions
(Added KDE Eco Test project) |
m (changed list of Issues to repository Issues) |
||
Line 73: | Line 73: | ||
'''Project type:''' Coding | '''Project type:''' Coding | ||
'''Brief explanation:''' [https://community.kde.org/Goals/Sustainable_Software Sustainability] is one of KDE's goals for the next two years. One aspect of this goal is to measure the energy consumption of KDE software. To do this, it is necessary to use an emulation tool to create usage scenario scripts. [https://invent.kde.org/teams/eco/feep/-/blob/master/tools/KdeEcoTest/ "KDE Eco Test"] is one such tool, but it needs some fixes. A list of to-dos can be found at the repository's [https://invent.kde.org/teams/eco/feep/-/ | '''Brief explanation:''' [https://community.kde.org/Goals/Sustainable_Software Sustainability] is one of KDE's goals for the next two years. One aspect of this goal is to measure the energy consumption of KDE software. To do this, it is necessary to use an emulation tool to create usage scenario scripts. [https://invent.kde.org/teams/eco/feep/-/blob/master/tools/KdeEcoTest/ "KDE Eco Test"] is one such tool, but it needs some fixes. A list of to-dos can be found at the repository's [https://invent.kde.org/teams/eco/feep/-/issues Issues for "KDEEcoTest"]. | ||
'''Expected results:''' At the end of the project several of the to-dos in the above list should be resolved (while new ones may be added). | '''Expected results:''' At the end of the project several of the to-dos in the above list should be resolved (while new ones may be added). |
Revision as of 14:50, 28 November 2023
Ideas
General information
All community members can submit an idea for a Season of KDE project. However, if you are not intending to be a mentor for the project, make sure to contact relevant mentors first and obtain consent to include their contact information here. Do not add SoK ideas with no mentor and no contact info.
Information for mentees
These ideas were contributed by our KDE 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 are interested in.
When writing your proposal or asking for help from the general KDE community do not 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 https://invent.kde.org/teams/season-of-kde/2024 before the deadline. Instructions for how to submit are included there.
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.
Sustainability 1: Improve "KDE Eco Test" emulation tool
Project type: Coding
Brief explanation: Sustainability is one of KDE's goals for the next two years. One aspect of this goal is to measure the energy consumption of KDE software. To do this, it is necessary to use an emulation tool to create usage scenario scripts. "KDE Eco Test" is one such tool, but it needs some fixes. A list of to-dos can be found at the repository's Issues for "KDEEcoTest".
Expected results: At the end of the project several of the to-dos in the above list should be resolved (while new ones may be added).
Knowledge Prerequisite: Coding in Python, basic knowledge of git and automation tools
Mentors: Emmanuel Charruau @allon:kde.org, Joseph P. De Veaugh-Geiss @joseph:kde.org on Matrix