GoogleCodeIn/2016/Ideas

Jump to: navigation, search


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.

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

Documentation/training

Beginner: Write a wiki page for beginners documenting where to find resources for KDE software development

Write a wiki page for beginners documenting where to find resources for KDE software development. You may link to other wiki pages, webpages, mail list posts, IRC channels and anything else you think beginners will find useful.

Beginner: Write a wiki page for beginners documenting where to find resources for writing KDE documentation

Write a wiki page for beginners documenting where to find resources for writing KDE documentation

You may link to other wiki pages, webpages, mail list posts, IRC channels and anything else you think beginners will find useful.

Beginner: Write a wiki page for beginners documenting where to find resources for designing KDE software artwork

Write a wiki page for beginners documenting where to find resources for designing KDE software artwork, visual design, icons and so forth.

You may link to other wiki pages, webpages, mail list posts, IRC channels and anything else you think beginners will find useful.

Beginner: Write a wiki page for beginners documenting where to find resources for working on KDE websites

Write a wiki page for beginners documenting where to find resources for working on KDE websites.

You may link to other wiki pages, webpages, mail list posts, IRC channels and anything else you think beginners will find useful.

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.

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 KDE-Soc@kde.org.
  • 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.

Beginner: Find resources for development online and identify help channels, relevant to KDE projects

  • Many development docs are in the wikis and some in webpages. Find and link to 5 to 10 up-to-date and complete guides or tutorials for Framework or Plasma 5 development.
  • KDE developers work in teams, and those teams communicate most often in IRC and mail lists. Find 5-10 relevant IRC channels and developer MLs and include the links in your document.
  • The links for both step one and step should be in the form of wiki or webpage links, and irc channel links. If you like, you may blog this document, or submit it like a school paper, with appropriate introductory text and explanation of the links you are presenting.

Beginner: What is KDE, what is Free software, what is open source?

What is KDE, what is Free software, what is open source?

Write a short 5 paragraph essay answering and explaining the above. What is important is clearly stating information and any thoughts you might have, not grammar or spelling. You may submit this essay as a blogpost or like a school paper. Be sure to include appropriate introductory text and explanation of any links you present.

Quality assurance

Beginner: Testing beta and git versions of applications

Testing beta and git versions of stuff, provided the project has a testing framework, should be documented. If they have no such testing framework and documentation, a more advanced student could help create one.

User interface


This page was last edited on 24 January 2016, at 09:31. Content is available under Creative Commons License SA 4.0 unless otherwise noted.