< GSoC | 2013 Revision as of 20:48, 11 February 2013 (view source)D ed (talk | contribs) (Created page with "See also: GSoc Instructions == Guidelines == === Information for Students === These ideas were contributed by our developers and users. They are sometimes vague...") Revision as of 20:49, 11 February 2013 (view source) D ed (talk | contribs) (→Project:)Newer edit → Line 38: Line 38: 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. + + +==Ideas== Revision as of 20:49, 11 February 2013 See also: GSoc Instructions Contents 1 Guidelines 1.1 Information for Students 1.2 Adding a Proposal 1.2.1 Project: 2 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 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 Note Follow the template of other proposals! 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 Retrieved from "https://community.kde.org/index.php?title=GSoC/2013/Ideas&oldid=29986" Content is available under Creative Commons License SA 4.0 unless otherwise noted.