← GoogleCodeIn/2012/Ideas You do not have permission to edit this page, for the following reason: The action you have requested is limited to users in one of the groups: Users, Administrators, trusted, KDEDevelopers. You can view and copy the source of this page. = Guidelines = == Information for Students == This page is for collecting ideas for [http://code.google.com/opensource/gci/2012/index.html 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 == === KDE Telepathy: Allow the user to configure the theme for group chats=== ;Description: Currently a user can configure the theme used for normal 1-1 chats, but group chats are hardcoded to use a different theme. We should have a way to configure which theme is used for group chats as well https://bugs.kde.org/show_bug.cgi?id=282518 ;Prerequisites: C++, Qt ;Mentor: The KDE Telepathy Team (#kde-telepathy on freenode, or email@example.com (be sure to join the mailing list first, otherwise your email may get lost)) === KDE Telepathy: Provide an option on whether to go offline when the contact list closes=== ;Description: Currently when a user goes offline they remain online if the presence applet is visible, otherwise it shows a prompt "Do you wish to go disconnect your accounts y/n". If a user selects the option "Do not show again" this never appears again and the user can never change this. Student should add an option in KDE Telepathy to say what should happen when the contact list closes. https://bugs.kde.org/show_bug.cgi?id=306853 ;Prerequisites: C++, Qt ;Mentor: The KDE Telepathy Team (#kde-telepathy on freenode, or firstname.lastname@example.org (be sure to join the mailing list first, otherwise your email may get lost)) === Amarok: Check Copyright Headers and Collect Contributor Email Addresses === ;Description: Amarok should be GPLv2+ licensed throughout, but not all license headers seem to contain the correct statement. Some files even miss a license header. If there is a incorrect license stated in a header the copyright holders should be contacted before making the fix. It could have been intentional (unlikely). It's useful to know who contributed to various parts of Amarok and during which period for statistical reasons. If we get a complete list and manage to maintain it, any future license changes (ex. to GPLv3) will be easier. ;Mentors: === 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 [http://community.kde.org/Kexi/Junior_Jobs/Add_d-pointers Kexi wiki]. ;Prerequisites: General C++ knowledge, prior knowledge of Qt is a plus. ;Mentor: [[User:Jstaniek|Jstaniek]] ([[User talk:Jstaniek|talk]]) === Pairs: add Get Hot New Stuff upload feature to Pairseditor === ;Description: 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@example.com) and Aleix Pol (firstname.lastname@example.org) === KGet: Code Stlye Check and Cleanup === ;Description: KGet currently consists of several lines of code which do not confirm to the KDE coding conventions. The task is to have KGet's codebase follow the coding conventions. ;Mentors: Aish Raj Dahal [http://www.google.com/recaptcha/mailhide/d?k=01yxUihv4rNalJX5Ut5RHxBQ==&c=0GUHTl8ugkU_MF62Cd2GPw0NPvtw3zQhxwv4v6sYxrk=], Lukas Appelhans [http://www.google.com/recaptcha/mailhide/d?k=01yxUihv4rNalJX5Ut5RHxBQ==&c=4NIC29OGMF0dot8jUMrqb_ZXCyVyg9rf2yTkgFeHgtw=] == Documentation/Training == === KDE Telepathy: Update account creation documentation === ;Description: This task consists of 3 parts all of which must be completed: * Update http://userbase.kde.org/Telepathy#1._How_do_I_add_a_new_IM_accounts to be more detailed with a step by step walkthrough with pictures * Add a guide on how to add a GTalk account if you use Google 2 Factor Authentication (https://bugs.kde.org/show_bug.cgi?id=303351) * Update this page http://kdetalk.net/howtoregister.php to show how you'd do it with KTp details (https://bugs.kde.org/show_bug.cgi?id=303923) ;Prerequisites: Be a user of KDE Telepathy. Good grasp of English. Able to take screenshots ;Mentor: The KDE Telepathy Team (#kde-telepathy on freenode, or email@example.com (be sure to join the mailing list first, otherwise your email may get lost)) === 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: * [http://amarok.community.kde.org Current wiki location] * [http://community.kde.org/Amarok Main target in the community wiki] * [http://techbase.kde.org/Amarok Techbase main target page] * [http://userbase.kde.org/Amarok Userbase main target page] ;Mentor: [mailto:firstname.lastname@example.org Myriam Schweingruber] === Update KSirK documentation === ;Description: [http://docs.kde.org/development/en/kdegames/ksirk/index.html KSirK documentation] is moderate outdated (outdated screenshots, no description of new main menu items). Student should download [https://projects.kde.org/projects/kde/kdegames/ksirk/repository/revisions/master/raw/doc/index.docbook documentation source] and update it using [http://docs.kde.org/development/en/kdegames/ksirk/index.html HTML version] as a reference, new screenshots for the default KDE theme (Oxygen) should be also presented. ;Prerequisites: Moderate level of English, [http://userbase.kde.org/Special:myLanguage/What_is_a_distribution KDE distribution] installed or run from live image. ; Links: * [http://techbase.kde.org/Documentation_Primer/Manual Reference on docbook syntax] * [http://userbase.kde.org/Special:myLanguage/Taking_Screenshots Manual on how to take a screenshot] ;Mentor: [mailto:email@example.com Yuir Chornoivan] == 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 [http://tomahawk-player.org/about.html] or [http://chakra-project.org/team.html]. We're specifically interested in a nice design and layout, and can fill out the data ourselves later on. ;Mentor: === KDE Forums: clean up KDE Brainstorm === ;Description: Currently the KDE Brainstorm (http://brainstorm.forum.kde.org) includes a lot of invalid, duplicate, or already fixed ideas. In order for both users and developers to screen them effectively, they need to be reorganized. The Brainstorm interface already allows to do this: the task involves looking through the open ideas and mark them as fixed, invalid, in progress, or finished. ;Prerequisites: Some general knowledge about the current progress of KDE software, including recent developments. ;Mentor: Luca Beltrame (firstname.lastname@example.org) === Metrics: Check Ohloh organisation page === ;Description: KDE is a showcase in Ohloh's new organisation feature. We need to make sure the information in the project is accurate. Please check if there are any missing projects in the project listing and if they are correctly categorized as being a KDE project. Check for other improvements that can be done and suggest them. ;Mentor: Lydia Pintscher === Metrics: MLStats === ;Description: Investigate MLStats and create some useful statistics for 3 mailing lists. Document your findings and work so it can be extended later. ;Mentor: Lydia Pintscher === Metrics: Git stats === ;Description: Investigate some options to get statistics out of git that let us learn more about the project and the people working on it. Document your findings and their benefits, drawbacks and what the individual options can do. ;Mentor: Lydia Pintscher === Promo: new Twitter and identi.ca backgrounds === ;Description: Create new backgrounds for identi.ca and Twitter similar to the ones at [[Promo/Material/Microblogging]]. ;Mentor: Lydia Pintscher === KDE e.V.: Create board timeline === ;Description: Create a timeline for the board of directors of KDE e.V. similar to http://meta.wikimedia.org/wiki/Wikimedia_Board_of_Trustees#Chart. ;Mentor: Lydia Pintscher === Promo: Create a timeline of important events in KDE's history === ;Description: Create a timeline of important events in KDE's history. ;Mentor: Lydia Pintscher === Promo: Create an overview of KDE === ;Description: Create a mindmap to give an overview of KDE similar to http://de.wikipedia.org/w/index.php?title=Datei:WikimediaMovementMindmap-October2012.svg. ;Mentor: Lydia Pintscher === KStars: Add a custom catalog === ;Description: The Catalog selected is the "Saguaro Astronomy Club catalog". Reformat and clean up the existing catalog to make it compatible for being loading into KStars. ;Mentor: Rishab Arora (ra.rishab [at] gmail.com) === Promo: Propose updates for KDE's events calendar === ;Description: KDE maintains an event calendar at http://events.kde.org/upcoming.php. Research dates of future events we've attended before and make a list of dates, locations and links for them. ;Mentor: Lydia Pintscher === Join the Game: Come up with ideas for a social media campaign === ;Description: KDE e.V. is running an individual supporting membership program called Join the Game to help raise funds and connect to members. Come up with ideas for a social media campaign to raise awareness of the program. Look at what other organisations have done like the Ada Initiative. ;Mentor: Lydia Pintscher == Quality Assurance == ===KDE Telepathy: go through our testing specification=== ;Description: We have a testing specification that we go through before every release. http://community.kde.org/Real-Time_Communication_and_Collaboration/ReleaseTesting. We require a student to go through this test procedure and see if there are any problems with the current code ;Prerequisites: Running the latest KTp from source ;Mentor: The KDE Telepathy Team (#kde-telepathy on freenode, or email@example.com (be sure to join the mailing list first, otherwise your email may get lost)) === 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 and 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: * [http://community.kde.org/Amarok/Development/Testing List of Amarok feature tests] * [http://blogs.fsfe.org/myriam/2009/09/compiling-amarok-from-git-locally-full-summary/ Local build instructions] ;Mentor: [mailto:firstname.lastname@example.org 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. <br>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. ;Prerequisites: Ability of gathering data from users, aggregating it and structuring; UI design/analytic skills are welcome. ;Mentor: [[User:Jstaniek|Jstaniek]] ([[User talk:Jstaniek|talk]]) === Pairs: create a new icon for Pairs Editor === ;Description: Modify the Pairs game icon to create a new icon for the Pairs Editor ;Mentor: Marco Calignano (email@example.com) and Aleix Pol (firstname.lastname@example.org) === KAlgebra Mobile: figure out a touch-friendly keyboard === ;Description: We have had KAlgebra working for more than a year now and it works great. Now the problem is that the input method we're using uses the default keyboard in the device. That's good because it feels integrated, but it would be interesting to have our own keyboard targeting KAlgebra's language. In this task you'll have to design a keyboard either through a mock-up or a QML file (better) that will let the user enter any equation supported by KAlgebra's language. ;Mentor: Aleix Pol Gonzalez <email@example.com> === KStars: propose UI design for mobile version of KStars === ;Description: We are planning to port KStars to mobile devices, tablets in particular. We would like to gather as many UI design concepts as possible. The scope of the design is to be considered, as well as the method of recording it. ;Prerequisites: UI design skills and enthusiasm for work. Preferably amateur astronomer and KStars user. No coding skills needed. ;Mentor: Rafal Kulaga (rl.kulaga [at] gmail.com) === KStars: design an icon for AstroBin.com API feature === ;Description: We are introducing AstroBin.com API support in KStars, so we're looking for a neat icon for its configuration page in Options window. ;Mentor: Rafal Kulaga (rl.kulaga [at] gmail.com) Return to GoogleCodeIn/2012/Ideas. Retrieved from "https://community.kde.org/GoogleCodeIn/2012/Ideas"