< GoogleCodeInRevision as of 21:31, 25 October 2012 by Mamarok (talk | contribs) (→Amarok: Testing from git: add more information)(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff) Contents 1 Guidelines 1.1 Information for Students 1.2 Adding a Proposal 2 Ideas 2.1 Code 2.1.1 Kexi: add d-pointers to classes 2.1.2 Pairs: add Get Hot New Stuff upload feature to Pairseditor 2.2 Documentation/Training 2.2.1 Amarok: Reorganize wiki in its new location 2.3 Outreach/Research 2.3.1 Amarok: Make a "Team" page 2.4 Quality Assurance 2.4.1 Pairs Editor: testing it 2.4.2 Amarok: Testing from git 2.5 User Interface 2.5.1 Kexi: find UI issues while running under non-KDE desktop 2.5.2 Pairs: create a new icon for Pairseditor 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! Please keep in mind that the tasks are going to be solved by 13 to 17 year olds. 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 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 Kexi: add d-pointers to classes Description Improve internal APIs in Kexi. This can be done easily by introducing d-poitners to classes that lack them. Details on Kexi wiki. Mentor Jstaniek (talk) Pairs: add Get Hot New Stuff upload feature to Pairseditor Create a new action to provide the user to upload hers/his new Pairs Theme to a public server to make it available for the Get Hot New Stuff feature in the game. Mentors Marco Calignano ([email protected]) Aleix Pol ([email protected]) Documentation/Training Amarok: Reorganize wiki in its new location Description Amarok is changing the location of its wiki and also needs to reorganize its wiki structure. Previously everything was in the same wiki, now we are moving to the 3 wiki site of KDE: Techbase, Community and Userbase. The existing pages need to be checked for consistency and moved to their new location after having made a structure plan. Prerequisites The student should be able to grasp large sets of data and be able to organize these in a logical manner. Some basic mediawiki editing knowledge is a plus. Links *Current wiki location *Main target in the community wiki *Techbase main target page *Userbase main target page Mentor Myriam Schweingruber Outreach/Research Amarok: Make a "Team" page Description 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. Mentor Quality Assurance Pairs Editor: testing it Description The Pairs Editor is a new application and needs to be tested by actual users. The student will have to try create a pairs theme using the editor and help us figure out the parts that are not working that well. Mentor Aleix Pol, Marco Calignano Amarok: Testing from git Description While Amarok ships a stable version there also is the current development version. The student should build a development installation from git and test the main functions of Amarok and report back eventual errors, inconsistencies and bugs. Prerequisites The student must be able to follow clear written instructions, have a logical way of thinking. Must be able to test software independently after a short introduction Links *List of Amarok feature tests *Local build instructions Mentor Myriam Schweingruber User Interface Kexi: find UI issues while running under non-KDE desktop Description Review Kexi UI to find glitches while running under non-KDE desktop such as Unity, GNOME or Xfce. Since Kexi is highly portable software, it is desired to have it adaptable to current look and feel of the underlying desktop. Any found issue, suggestion or doubt should be reported. Proposing solutions is welcome too but not necessary. Providing screen shots and details of system (desktop) configuration is expected. No software engineering skills are needed. User-level understanding of Kexi is preferred. Mentor Jstaniek (talk) Pairs: create a new icon for Pairseditor Description Modify the Pairs game icon to create a new icon for the Pairseditor Mentor Marco Calignano ([email protected]) Aleix Pol ([email protected]) Retrieved from "https://community.kde.org/index.php?title=GoogleCodeIn/2012/Ideas&oldid=25851" Content is available under Creative Commons License SA 4.0 unless otherwise noted.