Jump to content

GoogleCodeIn/2017/Ideas

From KDE Community Wiki


Guidelines

Information for Students

This page is for collecting ideas for Google Code-in tasks. The tasks will be moved into the GCi app for you to claim when appropriate. Add your names under mentor field if you also would like to mentor for that idea.

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. We have a particular need for beginner tasks.

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/Training: Tasks related to creating/editing documents and helping others learn more
  • Outreach/research: Tasks related to community management, outreach/marketing, or studying problems and recommending solutions
  • Quality Assurance: Tasks related to testing and ensuring code is of high quality
  • 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

Beginner: Do your first commit

Clone the project the firstcommit. Add your name to the CONTIBUTOR.md in the format specified. And commit your change to the local repository. Take the screenshot of the commit

mentors
vijay<[email protected]>,

GCompris: replace variant with var where possible

See task https://phabricator.kde.org/T6911

mentors
Timothee<[email protected]>, Johnny<[email protected]>,

Beginner: Start your first project

Create a repo from scratch on KDE infra and submit the link or the screenshot. The repo can store your configuration file or any project that you think can be useful for other people. It can also contain a simple readme with the idea described of type of application you would want to use.

mentors
vijay<[email protected]>,

Kopete: Add tests for Kopete components

You can go through the QtTest documentation and add test cases for the previously written tests or add new tests of your own.

mentors
vijay<[email protected]>,

Kopete: Build Kopete from source and update documentation

Build Kopete from source and create the wiki page with the steps of how you did it.

mentors
vijay<[email protected]>,

Documentation/training

GCompris: Document "ScoreItem.qml"

Look for how this item is used and as some documentation to it.

mentors
Timothee<[email protected]>, Johnny<[email protected]>, Amit<[email protected]>

GCompris: Document "ReadyButton.qml"

Look for how this item is used and as some documentation to it.

mentors
Timothee<[email protected]>, Johnny<[email protected]>, Amit<[email protected]>

GCompris: Document "Numpad.qml"

Look for how this item is used and as some documentation to it.

mentors
Timothee<[email protected]>, Johnny<[email protected]>, Amit<[email protected]>

GCompris: Document "DominoNumber.qml"

Look for how this item is used and as some documentation to it.

mentors
Timothee<[email protected]>, Johnny<[email protected]>, Amit<[email protected]>

GCompris: Document "Domino.qml"

Look for how this item is used and as some documentation to it.

mentors
Timothee<[email protected]>, Johnny<[email protected]>, Amit<[email protected]>

GCompris: Document "Balloon.qml"

Look for how this item is used and as some documentation to it.

mentors
Timothee<[email protected]>, Johnny<[email protected]>, Amit<[email protected]>

GCompris: Document "AnswerButton.qml"

Look for how this item is used and as some documentation to it.

mentors
Timothee<[email protected]>, Johnny<[email protected]>, Amit<[email protected]>

GCompris: Document "menu/ConfigurationItem.qml"

Look for how this item is used and as some documentation to it.

mentors
Timothee<[email protected]>, Johnny<[email protected]>, Amit<[email protected]>,

Outreach/research

Beginner: Connect to the #KDE-soc channel on freenode, introduce yourself, and have a conversation with someone

  • To connect to IRC, either install and use a client, such as KDE's Konversation, mIRC on Windows, or Colloquoy on Mac; OR use webchat: https://webchat.freenode.net/
  • Once you have connected to irc.freenode.net, join the #kde-soc channel (/join #kde-soc) and introduce yourself. Explain that you are doing a beginner GCi task, and that to finish that, you need to talk to someone. You might ask questions that help you in your future tasks, as IRC is how many of us communicate on a daily basis.
  • Submit a screenshot of the beginning or end of the conversation.
mentors
vijay<[email protected]>,

Beginner: Subscribe to the KDE-Soc mail list, and introduce yourself

  • Subscribe to our student mail list, KDE-Soc. This is for all students who want to subscribe, whether or not they are enrolled in Google Code-in, Google Summer of Code, or Season of KDE. https://mail.kde.org/mailman/listinfo/kde-soc for information on how to subscribe.
  • Once you have confirmed your subscription, send a post to the list introducing yourself. This means sending an email to [email protected].
  • Once you have sent your post, find it in the archives at https://mail.kde.org/pipermail/kde-soc/ and submit the link to your email to finish the task.
  • You may unsubscribe after posting if you like, however you are welcome to stay subscribed if you like. This is valuable if you plan to participate in later student programs.
mentors
vijay<[email protected]>,

Beginner: How did you get to know about KDE?

Write a short 5 paragraph essay answering and explaining the above. You should ideally state your experience about "that first time" when you heard/read about KDE. You can also include the information about what you know about KDE till now, points about opensource and free software in general.

mentors
vijay<[email protected]>,

Quality assurance

Beginner: Install and Use any KDE app

Submit a text with the points like what can be improved in it.

mentors
vijay<[email protected]>,

User interface

GCompris: "Click on me" vertical mode

Fix a visual issue of this activity in vertical mode.

  • The sub level score should be given a better position (its hidden below the bar) GLwVYQU.png
mentors
Timothee<[email protected]>, Johnny<[email protected]>, Divyam<[email protected]>,

GCompris: "Control the hose pipe" vertical mode

Fix a visual issue of this activity in vertical mode.

  • The pipe should always end right above the fire, and not go out of the screen GLwWVCB.png
mentors
Timothee<[email protected]>, Johnny<[email protected]>, Divyam<[email protected]>,

GCompris: "Mining for gold" vertical mode

Fix a visual issue of this activity in vertical mode.

  • The score item should be at a better position (its hidden below the bar) GLwXgvMH.png
mentors
Timothee<[email protected]>, Johnny<[email protected]>, Divyam<[email protected]>,

GCompris: "Penalty" vertical mode

Fix a visual issue of this activity in vertical mode.

  • The mouse should be at a better position (its hidden below the bar) GLwXRzG.png
mentors
Timothee<[email protected]>, Johnny<[email protected]>, Divyam<[email protected]>,

GCompris: "Make the ball go to Tux" vertical mode

Fix a few visual issues of this activity in vertical mode.

  • The text in intro is hidden GLwV3ln.png
  • The arrow keys are hidden by hands GLwVg3s.png
  • The title is hidden by cross GLwVpaZ.png
mentors
Timothee<[email protected]>, Johnny<[email protected]>, Divyam<[email protected]>,
Retrieved from "https://community.kde.org/index.php?title=GoogleCodeIn/2017/Ideas&oldid=78718"