GoogleCodeIn/2011/Ideas: Difference between revisions
→easy: added new Idea |
→easy: added bug triaging task |
||
| Line 174: | Line 174: | ||
=== easy === | === easy === | ||
==== | ==== Bug triaging: searching for duplicates ==== | ||
Description: Many KDE bug reports need to be triaged (checked) before they can be forwarded to the developers. The task consists in selecting individual KDE projects and check the database for duplicate entries. | |||
Expected results: have a better triaged bug database to facilitate the developer's work. | |||
Prerequisites: Having good analytical skills, having read and understood the triaging Guide: http://techbase.kde.org/Contribute/Bugsquad/Guide_To_BugTriaging | |||
Time to complete:48 hours. | |||
Mentor: [email protected], kde-bugsquad, coordination in #kde-bugs | |||
=== medium === | === medium === | ||
Revision as of 11:51, 18 October 2011
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
Please only add proposals you are willing to mentor!
When adding an idea to this section, please try to include the following data:
- a brief explanation
- the expected results
- prerequisites for working on your project if any
- if applicable, links to more information or discussions
- your name and email address for contact
- time to complete the proposal
The proposals should be ordered by area:
- 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
Inside these areas they should be ordered by difficulty of the proposal (must be one of easy, medium, hard)
If you have a good idea for a proposal but are not going to mentor it, get in contact with relevant team/contributor first.
Ideas
Code
easy
Adding a twitter functionality (probably invalid because too big and missing a mentor)
Description: I wish to have a twitter functionality into the Plasma App "Microblogging".
Expected results: Full implemented twitter
Prerequisites: Knowledge of QML and JS
Time to complete: ?
Mentor:
medium
example task
Description:
Expected results:
Prerequisites:
Time to complete:
Mentor:
hard
example task
Description:
Expected results:
Prerequisites:
Time to complete:
Mentor:
Documentation
easy
Rewrite part of KPresenter documentation
Description: Rewriting of KPresenter's "Step by Step Tutorial" in order to be up to date with the new interface
Expected results: understandeable chapter on KPresenter handbook that explain how to create a basic project and how to use some basic features. Must have screenshoots.
Prerequisites: English language, some basic HTML knoweledge.
Time to complete: 48hrs.
Mentor: [email protected]
Update the Amarok Manual to the latest version
Description: The current Amarok Manual refers to version 2.4.0 which is already rather old. The task is to check for each entry if the text and screen shots still apply to the current stable version of Amarok and adapt if necessary.
Expected results: have an up-to-date Manual in Userbase.
Prertequisites: English language,some basic HTML knowledge and basic Mediawiki knowledge.
Time to complete: 48 hours.
Mentors: [email protected], [email protected]
medium
example task
Description:
Expected results:
Prerequisites:
Time to complete:
Mentor:
hard
example task
Description:
Expected results:
Prerequisites:
Time to complete:
Mentor:
Outreach
easy
example task
Description:
Expected results:
Prerequisites:
Time to complete:
Mentor:
medium
example task
Description:
Expected results:
Prerequisites:
Time to complete:
Mentor:
hard
example task
Description:
Expected results:
Prerequisites:
Time to complete:
Mentor:
Quality Assurance
easy
Bug triaging: searching for duplicates
Description: Many KDE bug reports need to be triaged (checked) before they can be forwarded to the developers. The task consists in selecting individual KDE projects and check the database for duplicate entries.
Expected results: have a better triaged bug database to facilitate the developer's work.
Prerequisites: Having good analytical skills, having read and understood the triaging Guide: http://techbase.kde.org/Contribute/Bugsquad/Guide_To_BugTriaging
Time to complete:48 hours.
Mentor: [email protected], kde-bugsquad, coordination in #kde-bugs
medium
example task
Description:
Expected results:
Prerequisites:
Time to complete:
Mentor:
hard
example task
Description:
Expected results:
Prerequisites:
Time to complete:
Mentor:
Research
easy
example task
Description:
Expected results:
Prerequisites:
Time to complete:
Mentor:
medium
example task
Description:
Expected results:
Prerequisites:
Time to complete:
Mentor:
hard
example task
Description:
Expected results:
Prerequisites:
Time to complete:
Mentor:
Training
easy
example task
Description:
Expected results:
Prerequisites:
Time to complete:
Mentor:
medium
example task
Description:
Expected results:
Prerequisites:
Time to complete:
Mentor:
hard
example task
Description:
Expected results:
Prerequisites:
Time to complete:
Mentor:
Translation
easy
example task
Description:
Expected results:
Prerequisites:
Time to complete:
Mentor:
medium
example task
Description:
Expected results:
Prerequisites:
Time to complete:
Mentor:
hard
example task
Description:
Expected results:
Prerequisites:
Time to complete:
Mentor:
User Interface
easy
example task
Description:
Expected results:
Prerequisites:
Time to complete:
Mentor:
medium
example task
Description:
Expected results:
Prerequisites:
Time to complete:
Mentor:
hard
example task
Description:
Expected results:
Prerequisites:
Time to complete:
Mentor: