GSoD/2020/Ideas
Guidelines
Information for Technical Writers
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.
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] and the KDE documentation list [email protected]. See the KDE mailing lists page for information on available mailing lists and how to subscribe.
Adding a Proposal
Project:
If appropriate, screenshot or another image
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)
Ideas with no mentors listed and their contact info will be removed
Ideas
Kirigami
Improving the accuracy, English, and examples of the Kirigami documentation will be useful for all developers seeking to use Kirigami in their applications.
Prerequisite knowledge expected: Basic proficiency of English and basic understanding of C++, QML, and their interactions.
Mentors: - Carson Black [ uhhadd AT gmail DOT com ] - Marco Martin [ notmart AT gmail DOT com ]