< GoogleCodeIn Revision as of 09:07, 17 October 2012 (view source)TeoM (talk | contribs) (→Amarok: Make a "Team" page)← Older edit Revision as of 09:09, 17 October 2012 (view source) TeoM (talk | contribs) (→Outreach)Newer edit → Line 36: Line 36: == Outreach == == Outreach == +=== Amarok === ==== Amarok: Donations landing page on our drupal site ==== ==== Amarok: Donations landing page on our drupal site ==== ==== Amarok: Migrate content from amarok.kde.org/wiki to various KDE wikis ==== ==== Amarok: Migrate content from amarok.kde.org/wiki to various KDE wikis ==== Revision as of 09:09, 17 October 2012 Contents 1 Guidelines 1.1 Information for Students 1.2 Adding a Proposal 2 Ideas 2.1 Code 2.2 Documentation 2.3 Outreach 2.3.1 Amarok 22.214.171.124 Amarok: Donations landing page on our drupal site 126.96.36.199 Amarok: Migrate content from amarok.kde.org/wiki to various KDE wikis 188.8.131.52 Amarok: Make a "Team" page 2.4 Quality Assurance 2.5 Research 2.6 Training 2.7 User Interface 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 User Interface: Tasks related to user experience research or user interface design and interaction 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 Documentation Outreach Amarok Amarok: Donations landing page on our drupal site Amarok: Migrate content from amarok.kde.org/wiki to various KDE wikis The content that is still useful should be moved to: community.kde.org/Amarok, userbase or techbase depending on target audience. Links to be made from a new page on amarok.kde.org linked to from the site's menu. Amarok: Make a "Team" page Based on information from Amarok's "About" dialog, various social networks such as openDesktop.org, and talking to team members, make a "Team" page on Amarok's project website, like  or . We're specifically interested in a nice design and layout, and can fill out the data ourselves later on. Quality Assurance Research Training User Interface Retrieved from "https://community.kde.org/index.php?title=GoogleCodeIn/2012/Ideas&oldid=25582" Content is available under Creative Commons License SA 4.0 unless otherwise noted.