GoogleCodeIn/2010/Ideas: Difference between revisions
(→Plasma) |
(→Parley) |
||
Line 100: | Line 100: | ||
=== Parley === | === Parley === | ||
====Vocabulary Test==== | |||
'''Area:''' Documentation<br> | |||
'''Description:''' Prepare for a vocabulary test with Parley. | |||
While doing that, write an introduction with screen-shots how you used and configured the program. | |||
With your tutorial it should be easy to get up and running to use Parley for those knowledge based tests.<br> | |||
'''Outcome:''' A tutorial with screen-shots that explains one use case for Parley.<br> | |||
'''Difficulty:''' easy<br> | |||
'''Time:''' 1 week<br> | |||
'''IRC:''' #kde-edu on freenode<br> | |||
'''Mailing List:''' kde-edu at kde org<br> | |||
'''Mentor:''' Frederik Gladhorn ([email protected])<br> | |||
====Spell-checking improvements==== | ====Spell-checking improvements==== | ||
'''Area:''' Code<br> | '''Area:''' Code<br> | ||
Line 109: | Line 121: | ||
'''Mailing List:''' kde-edu at kde org<br> | '''Mailing List:''' kde-edu at kde org<br> | ||
'''Mentor:''' Frederik Gladhorn ([email protected])<br> | '''Mentor:''' Frederik Gladhorn ([email protected])<br> | ||
=== Plasma === | === Plasma === |
Revision as of 19:23, 26 October 2010
Guidelines
Information for Students
This page is for collecting ideas for Google Code-in tasks. The tasks will be moved into Melange for you to claim when appropriate.
Adding a Proposal
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 any
- 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)
- difficulty of the proposal - must be one of easy, medium, hard
- time to complete the proposal
- the area the proposal is related to. This can be any of the following:
- Code: Tasks related to writing or refactoring code
- Documentation: Tasks related to creating/editing documents
- Outreach: Tasks related to community management and outreach/marketing
- Quality Assurance: Tasks related to testing and ensuring code is of high quality
- Research: Tasks related to studying a problem and recommending solutions
- Training: Tasks related to helping others learn more
- Translation: Tasks related to localization
- User Interface: Tasks related to user experience research or user interface design and interaction
If you are not a developer but have a good idea for a proposal, get in contact with relevant developers first.
Ideas
KDE
Video ad for KDE
Area: Outreach
Description: Use all your creativity to create an innovating short film promoting KDE. We are looking for an advertise with new ideas that communicate the spirit behind KDE.
Outcome: A short film (less that 2 minutes) promoting KDE
Difficulty: medium
Time: 1 week
IRC: #kdenlive on freenode
Mailing List: kdenlive-devel at lists dot sourceforge dot net
Mentor: Jorge Salgueiro ([email protected])
Oxygen
Icon junior Job
Area:User Interface
Description: Oxygen needs many many icons, some need to be updated to the new look and feel, some need to be created from scratch.
Outcome: A more complete/modern oxygen icon set.
Difficulty: medium
Time: 1 month
IRC: #Oxygen on freenode
Mailing List: all at oxygen-icons org
Mentor: Nuno Pinheiro ([email protected])
Amarok
conference poster
Area: Outreach
Description: Amarok needs a poster giving an overview of what Amarok is. It should be big, good-looking, easy to read and informative. http://amarok.kde.org/en/features can be taken as the basis for the poster but needs to be checked for correctness with the Amarok promo team.
Outcome: ready to print PDF of a shiny poster that will tell conference visitors more about Amarok.
Difficulty: medium
Time: 1 week
IRC: #amarok on freenode
Mailing List: amarok at kde org
Mentor: Lydia Pintscher (lydia at kde org)
KAlgebra
Mobile applet
Area: Code
Description: Think of what utilities you would like to have in your calculator and add them to KAlgebra Mobile version, it would be using some JavaScript bindings for KAlgebra so it would be quite simple.
Outcome: New and useful little tools ready to use on your device.
Difficulty: hard
Time: 1 week
IRC: #kde-edu on freenode
Mailing List: kde-edu at kde org
Mentor: Aleix Pol ([email protected])
Physics Library
Area: Code
Description: Think of one area that you like from your physics book and translate the formulae from your book into KAlgebra language.
Outcome: New library that will be available for everyone to use.
Difficulty: medium
Time: 1 week
IRC: #kde-edu on freenode
Mailing List: kde-edu at kde org
Mentor: Aleix Pol ([email protected])
Homework
Area: Documentation
Description: Try to solve different mathematics problems from class using KAlgebra. Explain how you did it, what turned out good and bad.
Outcome: For us, a good example on how KAlgebra is being used, for the rest an example of how to properly use KAlgebra.
Difficulty: medium
Time: 1 week
IRC: #kde-edu on freenode
Mailing List: kde-edu at kde org
Mentor: Aleix Pol ([email protected])
Parley
Vocabulary Test
Area: Documentation
Description: Prepare for a vocabulary test with Parley.
While doing that, write an introduction with screen-shots how you used and configured the program.
With your tutorial it should be easy to get up and running to use Parley for those knowledge based tests.
Outcome: A tutorial with screen-shots that explains one use case for Parley.
Difficulty: easy
Time: 1 week
IRC: #kde-edu on freenode
Mailing List: kde-edu at kde org
Mentor: Frederik Gladhorn ([email protected])
Spell-checking improvements
Area: Code
Description: There is a basic implementation for spell-checking in Parley. It is in a very rough state and prone to crashes. Improving the language selection and making it possible to check the spelling in one language at a time will make this feature much more useful.
Outcome: Spell-checking per language is possible, better language selection.
Difficulty: hard, at least basic C++ knowledge required
Time: 2 weeks (1 week to get Parley compiled, 1 week to change the code)
IRC: #kde-edu on freenode, talk to fregl
Mailing List: kde-edu at kde org
Mentor: Frederik Gladhorn ([email protected])
Plasma
DataEngine documentation
Area: Documentation
Description: Documentation of the sources and data structure of the most important dataengines currently shipped in the Plasma workspace, with extensive tutorials on ho to use them
Outcome: Techbase wiki pages of documentation of the tructure of the dataengines and pages of tutorials
Difficulty: easy
Time: 1-2 weeks
IRC: #plasma on freenode
Mailing list: plasma-devel at kde dot org
Mentor: Marco Martin (mart at kde dot org)
QML plasmoid
Area: Code
Decription: with the KDE Plasma Workspace 4.6 there is the new possibility to write plasmoids in QML and Javascript, let's try to rewrite one of the standard plasmoids in this language
Outcome: a simple plasmoid of the default set reimplemented almost identic in QML (suggested: RSSnow) this will kickstart the migration towards QtComponents and scene graph
Difficulty: easy
Time: 1 week
IRC: #plasma on freenode
Mailing list: plasma-devel at kde dot org
Mentor: Marco Martin (mart at kde dot org)
KDE and the Masters of the Universe
News Anchor
Area: Outreach
Description: Collect, write and record a small news segment for KDEMU; News must relevant to KDE and/or the Free desktop scene. Non-KDE related content must be in some way relevant to the KDE community (like Linux or X.org news).
Outcome: Every week the news segment recording will be played before our usual cast takes center stage. The written version can be published both as the show notes and as a KDE DOT Article.
Difficulty: Medium
Time: 4 week
IRC: #klluminati on freenode
Mentor: Guillermo Amaral (gamaral at kde dot org)