GoogleCodeIn/2010/Ideas: Difference between revisions

Revision as of 08:05, 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
Mailing List: amarok at kde org
Mentor: Lydia Pintscher (lydia at kde org)

@@ Line 3: / Line 3: @@
 === 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.
+This page is for collecting ideas for Google Code-in tasks. The tasks will be moved into Melange for you to claim when appropriate.
-Being accepted as a Google Code-in 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 [http://www.kde.org/mailinglists/ the KDE mailing lists page] for information on available mailing lists and how to subscribe.
 === Adding a Proposal ===
@@ Line 15: / Line 9: @@
 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
+:*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<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>
+'''IRC:''' #amarok<br>
+'''Mailing List:''' amarok at kde org<br>
+'''Mentor:''' Lydia Pintscher (lydia at kde org)