Jump to content

GSoC/2023/Ideas: Difference between revisions

From KDE Community Wiki
Jjazeix (talk | contribs)
Created page with "<br> See the page with the original ideas: GSoC 2023 Ideas And the preliminary status reports from students: GSoC 2023 Status Reports Categor..."
 
Jjazeix (talk | contribs)
No edit summary
Line 1: Line 1:
<br>
[[File:Mascot konqi-app-presentation.png|thumbnail|right|[[Konqi]] is giving a lesson!]]
See the page with the original ideas: [[/Ideas|GSoC 2023 Ideas]]
See also: [[../../|GSoC Instructions]], [[../../2022/Ideas|Last year ideas]]


And the preliminary status reports from students: [[/StatusReports|GSoC 2023 Status Reports]]
== Guidelines  ==


[[Category:Mentoring]]
=== 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 [http://www.kde.org/mailinglists/ the KDE mailing lists page] for information on available mailing lists and how to subscribe.
 
{{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.}}
 
__TOC__
 
=== Adding a Proposal ===
 
{{Note|Follow the template of other proposals!}}
 
==== Project: ====
 
'''If appropriate, screenshot or another image '''
 
'''Brief explanation:'''
 
'''Expected results:'''
 
'''Knowledge Prerequisite:'''
 
'''Duration:''' ~175 hr or ~350 hour (use only one)
 
'''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
:*expected effort to finish the project (either ~175 or ~350 hrs)
:*your name and email address for contact (if you're willing to be a mentor)
 
'''**Ideas with no mentors listed and their contact info will be removed**'''
 
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 ===
 
==== 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 ~175 or ~350 hours of effort necessary to finish the project. Use only one of these two 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 [https://matrix.to/#/#kde-soc:kde.org #kde-soc:kde.org] on matrix.

Revision as of 18:41, 11 December 2022

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 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

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.


Adding a Proposal

Note

Follow the template of other proposals!


Project:

If appropriate, screenshot or another image

Brief explanation:

Expected results:

Knowledge Prerequisite:

Duration: ~175 hr or ~350 hour (use only one)

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
  • expected effort to finish the project (either ~175 or ~350 hrs)
  • your name and email address for contact (if you're willing to be a mentor)

**Ideas with no mentors listed and their contact info will be removed**

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

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 ~175 or ~350 hours of effort necessary to finish the project. Use only one of these two 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.