GSoC/2013/Ideas: Difference between revisions
Line 52: | Line 52: | ||
'''Knowledge Prerequisite:''' Qt, C++ library design, unit testing, ideally usage of TelepathyQt already. | '''Knowledge Prerequisite:''' Qt, C++ library design, unit testing, ideally usage of TelepathyQt already. | ||
'''Mentor:''' [[mailto:[email protected], [email protected], [email protected], [email protected] ]] | |||
==== Project: Collaborative text editor powered by Telepathy Tubes==== | ==== Project: Collaborative text editor powered by Telepathy Tubes==== |
Revision as of 21:07, 11 February 2013
See also: GSoc Instructions
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 may wish to contact the developers and find out more about the particular suggestion you're looking at.
Being 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 is unlikely to work out.
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.
Adding a Proposal
Project:
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
KDE Telepathy
Project: Add ConnectionManager bindings to TpQt
Brief explanation: KDE Telepathy, the IM client, uses the backend library TelepathyQt to power everything. We have library bindings for writing instant messaging clients in Qt, but not the backend connection manager to to write protocols in TpQt. This has been started, but a lot of work is needed to make this finished. This will be a project in collaboration with Telepathy upstream at freedesktop.org.
Expected results: At the end of the summer we should have a completely working library for writing connection managers, with full unit tests.
Knowledge Prerequisite: Qt, C++ library design, unit testing, ideally usage of TelepathyQt already.
Mentor: [[email protected], [email protected],[email protected]]
Project: Collaborative text editor powered by Telepathy Tubes
Brief explanation: With Telepathy we can set up P2P DBus session between two contacts without the difficulty of servers and firewalls and low level TCP details. It would be great to use this to create a collaborative text editor that can be used for writing documents, or code.
What I expect to see in your proposal: Knowledge of collaborative text editors, and the main difficulty analysed. I expect to see what libraries you can re-use and a detailed list of what needs to be created.
Expected results: A working telepathy powered collaborative real-time text editor.
Knowledge Prerequisite: Qt, C++, Dbus, Telepathy
Mentor: [email protected]