View source for GoogleCodeIn/2010/Ideas

= 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  =

== Promotion and Marketing ==

=== Video ad for KDE ===
'''Area:''' Outreach<br>
'''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.<br>
'''Outcome:''' A short film (less that 2 minutes) promoting KDE<br>
'''Difficulty:''' medium<br>
'''Time:''' 1 week<br>
'''IRC:''' #kdenlive on freenode<br>
'''Mailing List:''' kdenlive-devel at lists dot sourceforge dot net<br>
'''Mentor:''' Jorge Salgueiro (jorge.salgueiro@gmail.com)

=== Overhaul the Promo wiki ===
'''Area:''' Documentation<br>
'''Description:''' Go through the KDE Promo wiki pages, remove obsolete content, update pages and provide a good navigation structure<br>
'''Outcome:''' A more useful wiki<br>
'''Difficulty:''' easy<br>
'''Time:''' 2 weeks<br>
'''IRC:''' #kde-promo on freenode<br>
'''Mailing List:''' kde-promo at kde dot org<br>
'''Mentor:''' [[User:Stuart Jarvis|Stuart Jarvis]] (stuart.jarvis@gmail.com)

=== KDE Slide Show ===
'''Area:''' Outreach<br>
'''Description:''' Create a slide show introducing KDE and its software, through a mixture of images and text<br>
'''Outcome:''' Cool stuff to have in the background at booths<br>
'''Difficulty:''' medium<br>
'''Time:''' 1 week<br>
'''IRC:''' #kde-promo on freenode<br>
'''Mailing List:''' kde-promo at kde dot org<br>
'''Mentor:''' [[User:Stuart Jarvis|Stuart Jarvis]] (stuart.jarvis@gmail.com)

=== Workspace Screencasts ===
'''Area:''' Outreach<br>
'''Description:''' Create a screencast aimed at getting Windows and Mac users started with Plasma Desktop and/or Plasma Netbook<br>
'''Outcome:''' Simple 'getting started' guide for placing on KDE website, potential future distribution with KDE software<br>
'''Difficulty:''' medium<br>
'''Time:''' 2 weesk<br>
'''IRC:''' #kde-promo on freenode<br>
'''Mailing List:''' kde-promo at kde dot org<br>
'''Mentor:''' [[User:Stuart Jarvis|Stuart Jarvis]] (stuart.jarvis@gmail.com - I can advise on content, but not on how to make a screencast)

=== KDE Live CD ===
'''Area:''' Outreach<br>
'''Description:''' KDe is not affiliated to and does not endorse any particular Linux distribution, however, by necessity we often use a distro Live CD to demo our software, even though it may be different to what we release. Based on an existing distribution, create a Live CD that contains only KDE branding and vanilla KDE software<br>
'''Outcome:''' Pure KDE Live CD to demo KDE software at conferences and shows<br>
'''Difficulty:''' medium<br>
'''Time:''' 4 weesk<br>
'''IRC:''' #kde-promo on freenode<br>
'''Mailing List:''' kde-promo at kde dot org<br>
'''Mentor:''' Sandro Andrade (sandroandrade@kde.org)

== Oxygen ==
=== Icon junior Job ===
'''Area:'''User Interface<br>
'''Description:''' Oxygen needs many many icons, some need to be updated to the new look and feel, some need to be created from scratch. Create or update three icons.<br>
'''Outcome:''' A more complete/modern oxygen icon set.<br>
'''Difficulty:''' medium<br>
'''Time:''' 1 week<br>
'''IRC:''' #Oxygen on freenode<br>
'''Mailing List:''' all at oxygen-icons org<br>
'''Mentor:''' Nuno Pinheiro (nuno@oxygen-icons.org)

== Amarok ==
=== Conference poster ===
'''Area:''' Outreach<br>
'''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.<br>
'''Outcome:''' ready to print PDF of a shiny poster that will tell conference visitors more about Amarok.<br>
'''Difficulty:''' medium<br>
'''Time:''' 1 week<br>
'''IRC:''' #amarok on freenode<br>
'''Mailing List:''' amarok at kde org<br>
'''Mentor:''' Lydia Pintscher (lydia at kde org)

=== Bugs and wishes cleanup ===
'''Area:'''Qualit Assurance<br>
'''Description:''' Amarok has quite a big list of bugs and wishes. Unfortunately there are also quite a few duplicates, and bugs or wishes that my have slipped from attention. Besides marking duplicates as such, the reports for older versions than the current stable one need to be cleaned up as well. To check the validity, this needs testing in the latest stable version, <br>
The task consists of both testing and cleanup, available for two students who will do 20 testing items and 50 cleanups. <br>
'''Outcome:''' a) Having a better picture of the importance of ticket handling. b) Being able to give a hand in bug triaging c) Capable of using the search features of bugzilla as well as capable of testing stable software releases. d) Capable of writing a testing plan for further use. <br>
'''Prerequisites:''' logic thinking, methodic work. <br>
'''Difficulty:''' easy to medium <br>
'''Time:''' 1-2 weeks <br>
'''IRC:''' #amarok on irc.freenode.net<br>
'''Mailing List:''' amarok at kde org <br>
'''Mentor:''' Myriam Schweingruber (myriam at kde org)

== KAlgebra ==
=== Mobile applet ===
'''Area:''' Code<br>
'''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.<br>
'''Outcome:''' New and useful little tools ready to use on your device.<br>
'''Difficulty:''' hard<br>
'''Time:''' 1 week<br>
'''IRC:''' #kde-edu on freenode<br>
'''Mailing List:''' kde-edu at kde org<br>
'''Mentor:''' Aleix Pol (aleixpol@kde.org)

=== Physics Library ===
'''Area:''' Code<br>
'''Description:''' Think of one area that you like from your physics book and translate the formulae from your book into KAlgebra language.<br>
'''Outcome:''' New library that will be available for everyone to use.<br>
'''Difficulty:''' medium<br>
'''Time:''' 1 week<br>
'''IRC:''' #kde-edu on freenode<br>
'''Mailing List:''' kde-edu at kde org<br>
'''Mentor:''' Aleix Pol (aleixpol@kde.org)

=== Homework ===
'''Area:''' Documentation<br>
'''Description:''' Try to solve different mathematics problems from class using KAlgebra. Explain how you did it, what turned out good and bad.<br>
'''Outcome:''' For us, a good example on how KAlgebra is being used, for the rest an example of how to properly use KAlgebra.<br>
'''Difficulty:''' medium<br>
'''Time:''' 1 week<br>
'''IRC:''' #kde-edu on freenode<br>
'''Mailing List:''' kde-edu at kde org<br>
'''Mentor:''' Aleix Pol (aleixpol@kde.org)

== KStars ==
KStars is an application that aims to be the all-in-one astronomy portal. It draws a map of the sky, does some cool calculations, helps manage your observations amongst other things! Help us take it even further!

=== Document the Observation Planner ===
'''Area:''' Documentation<br>
'''Description:''' Write clear documentation on all currently implemented functionalities of the Observation Planner in KStars. The help is essentially outdated, and this task aims to update it. This will involve learning a really simple schema called Docbook, which you can learn by looking at other help files. The next thing you would do is to explain how to use the Observation Planner tool and explain what each feature does, with appropriate screenshots. Will be a good task to pick if you are an amateur astronomer.<br>
'''Outcome:''' A nice help / user guide for the Observation Planner.<br>
'''Difficulty:''' easy<br>
'''Time:''' 1 week ~ 1.5 weeks<br>
'''IRC:''' #kde-edu on freenode<br>
'''Mailing List:''' kstars-devel@kde.org<br>
'''Mentor:''' Akarsh Simha <akarsh.simha@kdemail.net>; IRC: kstar

=== Documentation on Types of Telescopes ===
'''Area:''' Documentation<br>
'''Description:''' As a part of KStars, there was a project called AstroInfo that was started several years ago. The aim of the project is to provide an encyclopedia of information accessible from within KStars, with stuff that you can try from within KStars to enhance your understanding! This content is not supposed to be as in-depth as a full-fledged encyclopedia like Wikipedia, but at a much more accessible level. The aim of this project is to write a few articles about Telescopes. It should include these topics: Types of telescopes, Parameters used to describe telescopes (aperture, focal length) etc, Image quality and Aberrations, Calculation of magnification / Field-of-view. There should also be examples of how to use KStars to calculate the FOV of a telescope. A great task to pick if you are planning to do something physics / astronomy related in future.<br>
Also note that you should write all text on your own and not just copy-paste from other sources. Copy-pasting from other sources without appropriate attribution, called plagiarism, is a crime. Copy-pasting might not be allowed (even with attribution) by some sources, depending on their licensing terms. So you should write things on your own.<br>
'''Outcome:''' Information about telescopes as part of the AstroInfo project.<br>
'''Difficulty:''' easy<br>
'''Time:''' 1 week ~ 1.5 weeks<br>
'''IRC:''' #kde-edu on freenode<br>
'''Mailing List:''' kstars-devel@kde.org<br>
'''Mentor:''' Akarsh Simha <akarsh.simha@kdemail.net>; IRC: kstar

=== Links that explain terms within menus ===
'''Area:''' Code<br>
'''Description:''' Astronomy can have a lot of technical terms, and these can make astronomy in general, and KStars, inaccessible to a beginner. The aim of this project is to connect up to the documentation in the AstroInfo project (read about AstroInfo in the previous task description) from various menus in KStars. Wherever there is a technical term in KStars (eg: RA / Dec / Airmass etc in the Details Dialog, Catalog numbers / magnitude / constellation name in the context menu when clicking on an object), there should be a clickable link that takes the user to the corresponding page from the Astroinfo project.<br>
To do this project, you should know basic C++ and should be able to learn to use a couple of Qt-specific things pretty fast.<br>
<b>TODO:</b> Add more detail.<br>
'''Outcome:''' Links to information near technical terms in KStars<br>
'''Difficulty:''' medium<br>
'''Time:''' 2 weeks<br>
'''IRC:''' #kde-edu on freenode<br>
'''Mailing List:''' kstars-devel@kde.org<br>
'''Mentor:''' Akarsh Simha <akarsh.simha@kdemail.net>; IRC: kstar

=== Did you know? facts ===
'''Area:''' Documentation<br>
'''Description:''' The "Tip of the Day" in KStars is used to educate users both about the capabilities of KStars and about astronomy. Include at least 20 more interesting tips about astronomy and KStars. Students interested in astronomy / physics might be more interested, and more capable of doing this task.<br>
'''Outcome:''' More facts / tips in KStars.<br>
'''Difficulty:''' easy<br>
'''Time:''' 1 week<br>
'''IRC:''' #kde-edu on freenode<br>
'''Mailing List:''' kstars-devel@kde.org<br>
'''Mentor:''' Akarsh Simha <akarsh.simha@kdemail.net>; IRC: kstar

=== New screenshots! ===
'''Area:''' Documentation<br>
'''Description:''' The screenshots used in the KStars manual and the AstroInfo project are really old. The aim of this task is to replace all the old pictures with new ones.<br>
'''Outcome:''' Updated help files, which reflect the current look and feel of KStars.<br>
'''Difficulty:''' easy<br>
'''Time:''' 1 week<br>
'''IRC:''' #kde-edu on freenode<br>
'''Mailing List:''' kstars-devel@kde.org<br>
'''Mentor:''' Akarsh Simha <akarsh.simha@kdemail.net>; IRC: kstar

=== Remove code duplication in Observing List ===
'''Area:''' Code<br>
'''Description:''' The observing list code (observinglist.cpp) currently has a lot of duplicate code that can be removed. The aim of this is to remove all possible code duplication in observinglist.cpp.<br>
This will require basic knowledge of C++ and ability to adapt to an unfamiliar API (if you're not familiar with Qt).<br>
'''Outcome:''' Cleaner code in observinglist.cpp<br>
'''Difficulty:''' medium<br>
'''Time:''' 3 weeks<br>
'''IRC:''' #kde-edu on freenode<br>
'''Mailing List:''' kstars-devel@kde.org<br>
'''Mentor:''' Akarsh Simha <akarsh.simha@kdemail.net>; IRC: kstar

== 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 (gladhorn@kde.org)<br>

===Spell-checking improvements===
'''Area:''' Code<br>
'''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.<br>
'''Outcome:''' Spell-checking per language is possible, better language selection.<br>
'''Difficulty:''' hard, at least basic C++ knowledge required<br>
'''Time:''' 2 weeks (1 week to get Parley compiled, 1 week to change the code)<br>
'''IRC:''' #kde-edu on freenode, talk to fregl<br>
'''Mailing List:''' kde-edu at kde org<br>
'''Mentor:''' Frederik Gladhorn (gladhorn@kde.org)<br>

== Plasma ==
=== DataEngine documentation ===
'''Area:''' Documentation<br>
'''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<br>
'''Outcome:''' Techbase wiki pages of documentation of the tructure of the dataengines and pages of tutorials<br>
'''Difficulty:''' easy<br>
'''Time:''' 1-2 weeks<br>
'''IRC:''' #plasma on freenode<br>
'''Mailing list:''' plasma-devel at kde dot org<br>
'''Mentor:''' Marco Martin (mart at kde dot org)<br>

=== QML plasmoid ===
'''Area:''' Code<br>
'''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<br>
'''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<br>
'''Difficulty:''' easy<br>
'''Time:''' 1 week<br>
'''IRC:'''  #plasma on freenode<br>
'''Mailing list:''' plasma-devel at kde dot org<br>
'''Mentor:''' Marco Martin (mart at kde dot org)<br>

=== How to Screencast ===
'''Area:''' Promo/documentation<br>
'''Decription:''' Make screencasts on some Plasma features like "how to create an activity?" "how change wallpaper"? "how download new plasmoids?" and so on<br>
'''Outcome:''' A series of screencast videos with voice ove that explains how to use important features in the KDE Plasma Workspace<br>
'''Difficulty:''' medium<br>
'''Time:''' 1 week<br>
'''IRC:'''  #plasma on freenode<br>
'''Mailing list:''' plasma-devel at kde dot org<br>
'''Mentor:''' Marco Martin (mart at kde dot org)<br>

===Bookmarks plasmoid===
'''Area:''' Bugfix <br>
'''Decription:''' Fix and polish the behaviour of the Bookmarks plasmoid<br>
'''Outcome:''' The bookmarks plasmoid should behave better on bookmarks change, plasmoid resizing and be aware of activity change (last part facultative)<br>
'''Difficulty:''' easy<br>
'''Time:''' up to 1 week<br>
'''IRC:'''  #plasma on freenode<br>
'''Mailing list:''' plasma-devel at kde dot org<br>
'''Mentor:''' Marco Martin (mart at kde dot org)<br>

===Fix Dashboard behaviour===
'''Area:''' Bugfix <br>
'''Decription:''' Make the dashboard go away when some actions are performed, like alt+tab, current active window changed, desktop grid effect trigger<br>
'''Outcome:''' the dashboard should behave in a more natural and expected way hiding itself on the proper situations<br>
'''Difficulty:''' medium<br>
'''Time:''' up to 1 week<br>
'''IRC:'''  #plasma on freenode<br>
'''Mailing list:''' plasma-devel at kde dot org<br>
'''Mentor:''' Chani Armitage<br>

===Text for welcome plasmoid===
'''Area:''' Documentation <br>
'''Decription:''' Since early 4.0 days Plasma needs a plasmoid that displays a simple welcome message with some simple "did you know" or how to do a given thing.<br>
'''Outcome:''' This task would expect some of such text of be produced, and (optional, construct a very simple mockup grade ml plasmoid to display those text snippets)<br>
'''Difficulty:''' easy/medium <br>
'''Time:''' 1/2 weeks <br>
'''IRC:'''  #plasma on freenode<br>
'''Mailing list:''' plasma-devel at kde dot org<br>
'''Mentor:''' Chani Armitage<br>

=== Plasma Media Center Views ===
'''Area:''' Development<br>
'''Description:''' A couple of views for PMC written using QML: one for the TV form factor and the other one for the mobile device form factor<br>
'''Outcome:''' A couple of QML views that will hopefully be integrated with the software<br>
'''Difficulty:''' easy<br>
'''Time:''' 1-2 weeks<br>
'''IRC:''' #plasma on freenode<br>
'''Mailing list:''' plasma-devel at kde dot org<br>
'''Mentor:''' Marco Martin (mart at kde dot org), Alessandro Diaferia (alediaferia at kde dot org)<br>

== KDE and the Masters of the Universe ==

=== News Anchor ===
'''Area:''' Outreach<br>
'''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).<br>
'''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.<br>
'''Difficulty:''' Medium<br>
'''Time:''' 4 week<br>
'''IRC:''' #klluminati on freenode<br>
'''Mentor:''' Guillermo Amaral (gamaral at kde dot org)<br>

== KDE Base ==

=== KWallet UI ===
'''Area:''' Code<br>
'''Description:''' KWallet user interface still uses k3support classes<br>
'''Outcome:''' Rewrite the code that uses k3support to remove the dependencyy from the legacy module <br>
'''Difficulty:''' Medium<br>
'''Time:''' 1 week<br>
'''IRC:''' ???<br>
'''Mentor:''' ???<br>

== KDEPim ==

=== KMail reply to self in mailinglists ===
'''Area:''' Bugfixing<br>
'''Description:''' Replayig on a mail in a mailinglist sent by ourselves makes kmail reply to our own address rather than the mailinglist one.<br>
'''Outcome:''' Make KMil reply to the mailing list address <br>
'''Difficulty:''' Medium<br>
'''Time:''' 1 week<br>
'''IRC:''' ???<br>
'''Mentor:''' ???<br>

== KOffice ==

=== KSpread ===

==== Implement byte-position text functions as aliases for the normal text functions ====
'''Area:''' Code<br>
'''Description:''' The OpenDocument specification, which specifies formulas that should be supported by spreadsheet applications, defines a number of so-called byte-position text functions. These functions are currently not supported in kspread, and adding support for them is rather easy as they can just be aliases for the character-position text functions (these functions are FINDB, LEFTB, LENB, MIDB, REPLACEB, RIGHTB and SEARCHB).<br>
'''Outcome:''' Support for the byte-position text functions, by adding them as alias to the character-position text functions.<br>
'''Difficulty:''' easy<br>
'''Time:''' 1-2 days<br>
'''IRC:''' #koffice on freenode<br>
'''Mailing List:''' koffice-devel at kde org<br>
'''Mentor:''' Marijn Kruisselbrink (m.kruisselbrink@student.tue.nl)

==== Add support for the PERMUTATIONA function to kspread ====
'''Area:''' Code<br>
'''Description:''' Among the spreadsheet functions that are currently not supported by KSpread but are defined in the OpenDocument specification (which kspread aims to fully implement at some point), is the PERMUTATIONA function. PERMUTATIONA is very similar to the currently supported POWER function, it mostly puts some extra constraints on the input values (that should result in an error as output value), so for the implementation the current POWER implementation should be helpfull.<br>
'''Outcome:''' Support for the PERMUTATIONA function in kspread<br>
'''Difficulty:''' medium<br>
'''Time:''' 1 week<br>
'''IRC:''' #koffice on freenode<br>
'''Mailing List:''' koffice-devel at kde org<br>
'''Mentor:''' Marijn Kruisselbrink (m.kruisselbrink@student.tue.nl)

=== Krita ===

==== Implement GIMP's VBR Brush support ====
'''Area:''' Code<br>
'''Description:''' VBR Brush file format is used by GIMP for storing parametric brushes. They are used by digital artists. It is simple text file. Your task is to implement loading of this brush format as preset for the brush engine Pixel Brush, which is equivalent to the brush engine in GIMP.<br>
'''Outcome:''' Happy artists, better interoperability with GIMP<br>
'''Difficulty:''' medium<br>
'''Time:''' few days<br>
'''IRC:''' #krita on freenode<br>
'''Mailing List:''' kimageshop at kde org<br>
'''Mentor:''' Lukáš Tvrdý (lukast.dev at gmail com)

==== History docker ====
'''Area:''' Code<br>
'''Description:''' Implement a docker that show a list with the last undo steps, using a QUndoView. It should even be possible to make it working for all KOffice applications.<br>
'''Outcome:''' Happy artists, better visibility of the undo actions.<br>
'''Difficulty:''' easy<br>
'''Time:''' few days<br>
'''IRC:''' #krita on freenode<br>
'''Mailing List:''' kimageshop at kde org<br>
'''Mentor:''' Dmitry Kazakov (dimula73 at gmail com)

==== Krita YouTube videos ====
'''Area:''' Outreach<br>
'''Description:''' Record Krita in action. Compile Krita 2.3 trunk and record some cool new 2.3 features in action like brush engines, mirroring and rotation of the canvas. Full list of new features can be found here http://wiki.koffice.org/index.php?title=Schedules/KOffice/2.3/Feature_Plan#Krita<br>
'''Outcome:''' Happy developers, better visibility of Krita in the digital world<br>
'''Difficulty:''' easy<br>
'''Time:''' 5 days<br>
'''IRC:''' #krita on freenode<br>
'''Mailing List:''' kimageshop at kde org<br>
'''Mentor:''' Lukáš Tvrdý (lukast.dev at gmail com)

==== Krita UML diagram ====
'''Area:''' Documentation<br />
'''Description:''' Create a Unified Modeling Language (UML) diagram representing the overall structure of Krita. The purpose of this diagram would be to quickly introduce new coders (and the general public) to Krita's broad structure, and to serve as a foundation for a more complex diagram to complement the current Doxygen documentation of Krita.<br />
'''Outcome:''' A cool diagram useful to show the world how Krita works and as graphical documentation.<br />
'''Difficulty:''' medium/hard<br />
'''Time:''' one or two weeks.<br />
'''Mailing List:''' kimageshop at kde org<br />
'''Mentor:''' José L. Vergara (pentalis at gmail.com)<br />

==== Krita Mascot ====
'''Area:''' Outreach<br />
'''Description:''' Gather different design proposals for a Krita mascot and a logo, research their impact on people without previous awareness and with awareness of the project. Questions to consider include whether they think the logo evokes the program's function and whether the mascot is cool enough (think Firefox, Wilber, Puffy... ;) )<br />
'''Outcome:''' A cool mascot and logo or a list of candidates!<br />
'''Difficulty:''' medium<br />
'''Time:''' one or two weeks.<br />
'''Mailing List:''' kimageshop at kde org<br />
'''Mentor:''' José L. Vergara (pentalis at gmail.com)<br />

==== Simple Mixing Brush ====
'''Area:''' Code<br />
'''Description:''' Create a new brush engine for Krita. A brush that can paint with a color equal to the average of the colors underneath the brush outline (this is the simplest algorithm for a mixing brush).<br />
'''Outcome:''' Happy artists with a brush engine that allows for simple color mixing, which at the moment is missing in Krita.<br />
'''Difficulty:''' hard.<br />
'''Time:''' one to three weeks<br />
'''Mailing List:''' kimageshop at kde org<br />
'''Mentor:''' José L. Vergara (pentalis at gmail.com). For this one you can count on me to be your teacher, not just a mentor.<br />

== kdegraphics ==

=== Okular ===

==== Move KPDF bugs/wishes to Okular ====
'''Area:''' Bug triaging<br>
'''Description:''' Okular is the KPDF (KDE 3 PDF viewer) successor for KDE 4, the KDE bugzilla has lots of reports against KPDF that have to be verified against Okular and closed if they are already fixed and moved to the Okular product if they still make sene.<br>
'''Outcome:''' Happy users, Happy developers<br>
'''Difficulty:''' medium<br>
'''Time:''' few days<br>
'''IRC:''' #okular on freenode<br>
'''Mailing List:''' okular-devel@kde.org<br>
'''Mentor:''' Albert Astals Cid (aacid@kde.org)

== KDE Community Forums ==
'''Area:''' Code<br>
'''Description:''' Just like any other forum, KDE Forums being a popular resource is often a target for spammers (both human and bots). Of course, we cannot do much about the human spammers, but identifying spam bots is quite doable given that we identify the patterns. This project involves interaction with the forum staff and getting to know how the most common spam-bot profiles look. The aim is to develop a PHP script for the forum engine phpBB that would hook itself with user profile updates, track any change and pass them through regexes (say for example, for links in their signature, etc.) and move the user to a special usergroup if found suspicious.<br>
'''Outcome:''' Spam-bots get auto moved to a special usergroup that has posting restrictions.<br>
'''Difficulty:''' medium<br>
'''Time:''' 1 week<br>
'''IRC:''' #kde-forum on freenode<br>
'''EMail:''' forum-admin at kde org<br>
'''Mentor:''' KDE Forum Admins (forum-admin at kde org)

== Translation ==

==== Polish (pl) documentation screenshots ====
'''Area:''' Translation<br>
'''Description:''' Browse Polish KDE documentation and check if the current screenshots are up-to-date. Create new ones when needed. Check if the description in the documentation matches the screenshots (menu names etc).<br>
'''Outcome:''' Better quality Polish KDE<br>
'''Difficulty:''' easy<br>
'''Time:''' few days<br>
'''IRC:''' ???<br>
'''Mailing List:''' kdei18n-pl-devel@lists.sourceforge.net<br>
'''Mentor:''' Marta Rybczynska (kde-i18n at rybczynska.net)

==== Polish (pl) GUI verification ====
'''Area:''' Translation<br>
'''Description:''' Browse Polish KDE. Check the translation for correctness and style. Check if it matches Polish KDE guidelines.<br>
'''Outcome:''' Better quality Polish KDE<br>
'''Difficulty:''' easy<br>
'''Time:''' few days to a week<br>
'''IRC:''' ???<br>
'''Mailing List:''' kdei18n-pl-devel@lists.sourceforge.net<br>
'''Mentor:''' Marta Rybczynska (kde-i18n at rybczynska.net)

==== Translation of UserBase pages ====
'''Area:''' Documentation/Translation<br />
'''Description:''' Translation of sets of UserBase pages into a language of your choice.  The pages should be those most needed by newcomers either to KDE Software or new to contributing to documentation.  They are defined on the following pages: http://userbase.kde.org/Category:Getting_Started (with a sub-category Configuration) and http://userbase.kde.org/Category:Contributing.  There are 44 pages in all.  It is anticipated that on-line translation will be used, at least at first, with the student progressing to off-line translation using gettext and Lokalization should time allow.<br />
'''Outcome:''' Useful "own-language" documentation is created and the student learns to be comfortable with translation software.<br />
'''Difficulty:''' Easy to Medium<br />
'''Time:''' 2 weeks<br />
'''IRC:''' #kde-www on freenode<br />
'''Mailing List:''' kde-www@kde.org<br />
'''Mentor:''' Web team led for this purpose by Anne Wilson (annew at kde org)