GSoC/2023/Ideas: Difference between revisions
| Line 183: | Line 183: | ||
Provide new options to copy digiKam properties or metadata entries between items. Write unit-tests, and documentation. | Provide new options to copy digiKam properties or metadata entries between items. Write unit-tests, and documentation. | ||
'''Bugzilla Entries''': | |||
* [https://bugs.kde.org/show_bug.cgi?id=412343 Allow to apply the previously assigned tag to a new image] | |||
* [https://bugs.kde.org/show_bug.cgi?id=155384 Easily copy properties from one image to another one] | |||
'''Duration''': | '''Duration''': | ||
| Line 191: | Line 196: | ||
'''Mentors''': Thanh Trung Dinh ([email protected]), Maik Qualmann ([email protected]), and Gilles Caulier ([email protected]) | '''Mentors''': Thanh Trung Dinh ([email protected]), Maik Qualmann ([email protected]), and Gilles Caulier ([email protected]) | ||
===Your Own Idea === | ===Your Own Idea === | ||
Revision as of 02:18, 3 February 2023
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 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
Kalendar
Project: Calendar Invitation
Brief explanation: The goal is to make it possible to send calendar invitation from Kalendar and also handle incoming invitations. This includes showing the free busy information from the attendees. Part of this features are already implemented in the C++ core but needs to be hooked up in the UI and others will require more work.
Expected results: Being able to manage all your meetings with Kalendar and make sure this is unit tested :)
Duration: ~350 hours
Knowledge Prerequisite: C++ is highly recommended, this is a complex code base
Mentor: Carl Schwan and Claudio Cambra (contact us in #kalendar:kde.org on Matrix)
Project: Improved multiplatform support
Brief explanation: Kalendar works great on Linux, but due to our dependency tree it is tricky to get it to build on Windows, and we do not have any current builds for macOS. For this project you will work on improving our support for either or both of these platforms and helping them become first class citizens for Kalendar. This will likely involve working on related projects like Akonadi.
Expected results: Working daily builds of Kalendar on Windows and/or macOS, depending on chosen project duration.
Duration: ~175 hours for one platform or ~350 hours for both platforms
Knowledge Prerequisite: C++ and CMake will be used extensively
Mentor: Claudio Cambra and Carl Schwan (contact us in #kalendar:kde.org on Matrix)
Project: Mail integration
Brief explanation: The goal is to make Kalendar not just a great calendaring application, but also a great mail application. We have basic email lists and a basic viewer working, but there is a huge amount of work still to do here: threading, editing, sending, and a lot more. A lot of this will not have to be done from scratch thanks to Akonadi (i.e. email retrieval and sending), but a lot of it will (i.e. threading).
Expected results: Kalendar should be a nice mail app :)
Duration: ~350 hours
Knowledge Prerequisite: C++ is required, QML will be needed but can be learned on the go if one has some JS experience
Mentor: Carl Schwan and Claudio Cambra (contact us in #kalendar:kde.org on Matrix)
Project: Implement calendar availability
Brief explanation: The short version is that you will need to implement RFC 7953 in Kalendar. The long version is that this availability extension definde by this RFC allows to define available and unavailable time periods. This is then helpful when trying to schedule a meeting with someone (see above tasks) as you will then be able to see then and avoid scheduling a meeting at that time. Implementation you will first need to add support for this in KCalendarCore for it and then expose this to the user interface so that user can modify their availability.
Expected results: Being able to configure my availability in Kalendar
Duration: ~175 hours
Knowledge Prerequisite: C++ and QML is recommended
Mentor: Carl Schwan and Claudio Cambra (contact us in #kalendar:kde.org on Matrix)
Project: Accessibility improvements
Brief explanation: It is a general KDE goal to make our applications accessible to everyone, including those who may require using their computers with keyboard navigation and screen readers. Kalendar needs a lot of work in this regard, particularly regarding navigation within the calendar views and around the application.
Expected results: Keyboard navigation throughout the entirety of Kalendar is expected, as well as use with screen readers. Further ideas for accessibility-related improvements are a big plus.
Duration: ~175 hours
Knowledge Prerequisite: QML will be required for this task, and you will likely need to use some C++ too.
Mentor: Claudio Cambra (contact me in #kalendar:kde.org on Matrix)
Okular
Okular is a universal document viewer developed by KDE. Okular works on multiple platforms, including but not limited to Linux, Windows, Mac OS X, *BSD. Contact the Okular developers.
Project: Okular user interface for e-ink tables (PineNote)
Brief explanation: e-ink tables are special given their "low" refresh rate.
We would need to create a new Okular user interface (based either in the mobile or the dekstop one) to accommodate for the unique features of those kind of displays.
We will probably arrange to get a device loaned if someone gets selected for this project.
Expected results: A new Okular user interface that works well with e-ink tablets.
Knowledge prerequisite: C++, probably QML.
Duration: 350 hours.
Mentor: Albert Astals Cid [email protected]
Project: Improve Okular for Android
Brief explanation: Okular has an Android version it needs some improvements.
Poppler, the library that Okular uses for PDF rendering is missing a "find me a font given a font name" backend for Android. We should use new new Font API introduced in Android API 29 to do that.
The Icons in Okular-Android are not being rendered, there is something in KDE Frameworks interfering.
You should have an Android device with Android >= 10 for testing
Expected results: New Font API in poppler and icon rendering fixed.
Knowledge prerequisite: C++
Duration: 175 hours.
Mentor: Albert Astals Cid [email protected]
Sustainability
Project: Measuring Energy Usage Remotely with Online Portal
Brief explanation: The goal of this project is to create an online portal that allows developers to remotely access and control the energy measurement lab at KDAB Berlin, enabling them to upload Standard Usage Scenario scripts and obtain data from the power meter.
The related issue to this project : https://invent.kde.org/teams/eco/sustainable-software-goal/-/issues/3
Expected results: Developers can upload Standard Usage Scenario scripts and obtain data from the power meter remotely.
Knowledge Prerequisite: React/Django(Any web framework), Networking/Knowledge of tunneling, Task scheduling and Energy Measurement process.
Duration: 175 hours
Mentor: Joseph P. De Veaugh-Geiss (@joseph:kde.org ), Volker Krause(@vkrause:kde.org)
digiKam
digiKam is an advanced open-source digital photo management application that runs on Linux, Windows, and MacOS. The application provides a comprehensive set of tools for importing, managing, editing, and sharing photos and raw files.
Project: Improve Items Properties Management
Brief Explanation: the goal of this project is to improve the Items properties management. digiKam Properties (as Tags, Color Labels, Rating, Pick Labels, etc.) and Metadata entries (as Exif, Iptc, and Xmp tags) must be copiable between one item to other ones. Drag and drop and clipboard key features must be supported to make these operations. For the copiable Metadata entries, a preferred list of tags must be configurable to simplify workflow users.
Expected Results:
Provide new options to copy digiKam properties or metadata entries between items. Write unit-tests, and documentation.
Bugzilla Entries:
- Allow to apply the previously assigned tag to a new image
- Easily copy properties from one image to another one
Duration: 175 hours
Knowledge Prerequisite:
- C++, Qt API, GUI, CMake, metadata, database
Mentors: Thanh Trung Dinh ([email protected]), Maik Qualmann ([email protected]), and Gilles Caulier ([email protected])
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.