GoogleCodeIn/2010/Ideas: Difference between revisions
No edit summary |
|||
Line 37: | Line 37: | ||
'''Outcome:''' ready to print PDF of a shiny poster that will tell conference visitors more about Amarok.<br> | '''Outcome:''' ready to print PDF of a shiny poster that will tell conference visitors more about Amarok.<br> | ||
'''Difficulty:''' medium<br> | '''Difficulty:''' medium<br> | ||
'''IRC:''' #amarok<br> | '''IRC:''' #amarok on freenode<br> | ||
'''Mailing List:''' amarok at kde org<br> | '''Mailing List:''' amarok at kde org<br> | ||
'''Mentor:''' Lydia Pintscher (lydia at kde org) | '''Mentor:''' Lydia Pintscher (lydia at kde org) |
Revision as of 08:06, 24 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
- 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
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
IRC: #amarok on freenode
Mailing List: amarok at kde org
Mentor: Lydia Pintscher (lydia at kde org)