GSoC/2024/Ideas: Difference between revisions
Created page with "thumbnail|right|[[Konqi is giving a lesson!]] See also: GSoC Instructions, Last year ideas == Guidelines == === 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, you are urged to contact the developers and find out more about the particular suggestion you're looki..." |
more info about what to add in the ideas |
||
| Line 34: | Line 34: | ||
'''Mentor:''' | '''Mentor:''' | ||
When adding an idea to this section, please | When adding an idea to this section, please include the following data: | ||
:*if the application is not widely known, a description of what it does and where its code lives | :*if the application is not widely known, a description of what it does and where its code lives | ||
:*a brief explanation | :*a brief explanation (2-5 sentences) | ||
:*the expected size of the project (small-90 hours, medium-175 hours or large-350 hours) | |||
:*the expected results | :*the expected results | ||
:*pre-requisites for working on your project | :*pre-requisites for working on your project (skills required/preferred) | ||
:*if applicable, links to more information or discussions | :*if applicable, links to more information or discussions | ||
:*mailing list or IRC channel for your application/library/module | :*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) | :*your name and email address for contact (if you're willing to be a mentor) | ||
:*if possible, an easy, medium or hard rating of the project | |||
If you are not a developer but have a good idea for a proposal, get in contact with relevant developers first. | If you are not a developer but have a good idea for a proposal, get in contact with relevant developers first. | ||
Revision as of 17:20, 11 January 2024
See also: GSoC Instructions, Last year ideas
Guidelines
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, you are urged to contact the developers and find out more about the particular suggestion you're looking at.
Becoming accepted as a Google Summer of Code 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.
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 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.
Note
Adding a Proposal
Note
Sample project
Project type: Coding / Web Development / Promo / Translation
Brief explanation:
Expected results:
Knowledge Prerequisite:
Mentor:
When adding an idea to this section, please 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 (2-5 sentences)
- the expected size of the project (small-90 hours, medium-175 hours or large-350 hours)
- the expected results
- pre-requisites for working on your project (skills required/preferred)
- 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 possible, an easy, medium or hard rating of the project
If you are not a developer but have a good idea for a proposal, get in contact with relevant developers first.
Ideas
Project: Something that you're totally excited about
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.
Expected results: Something you and KDE loves
Knowledge Prerequisite: Probably C++ and Qt but depends on your project
Duration: Mention one of ~90, ~175 or ~350 hours of effort necessary to finish the project. Use only one of these three project classes and don't come up with other numbers here.
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:kde.org on matrix.