Sample Tasks
Stay organized with collections
Save and categorize content based on your preferences.
We ask you to provide around 25 sample tasks during registration to demonstrate
your commitment and ability to produce at least 50 unique tasks for students to
complete once the contest opens.
Google looks for:
- A mix of tasks across multiple categories. (Code, Documentation/Training,
Outreach/Research, Quality Assurance, and Design)
- Tasks of appropriate scope, length, and complexity.
- Fully fleshed out descriptions with enough information to get started on.
- Clear and understandable descriptions and titles.
- Appropriate tags for searchability.
It is possible to link to external resources for more detail, but the core task
description must be on the contest website.
Examples
Below, please find some examples of tasks created by previous participating open
source organizations. One size does not fit all -- every organization's tasks
will be different -- but these examples should help guide you.
You can find more in the archive.
KDE
Write the story of WikiToLearn
WikiToLearn has never had an about page, and the information about what it is
and how it came to exsitence is scattered in all sorts of places. We need to
unify it and make it visible and accessible to the users of the site.
- Tags: content, promotion, wikitolearn
- Categories: Documentation/Training, Research/Outreach
KDE
Build any KDE application from git repository
For various tasks in KDE organization, you will be required to build the various
KDE applications. This task aims to help you understand how to build various
KDE applications on the distribution of your choice.
The three easy steps to build any application are:
- Get source code from the git.
- Install required dependencies.
- Build the application.
Ask on the #kde-soc IRC channel for more information. You are required to build
KDE application of your choice and document steps you took to build it.
- Tags: cmake, qt, c++
- Catgegories: Coding
- Beginner Task
HAIKU
Fix a bug in the editor Pe
There are several bugs reported for the programmer's editor Pe. Fork the Pe
repository, pick an issue and fix it. Submit your fix as pull request (see
the HaikuPorter wiki which works pretty much the same).
- Tags: c++, pe
- Categories: Coding
FOSSASIA
Run WineTest on Linux and submit the results
First you need to build Wine according to
http://wiki.winehq.org/BuildingWine. This
will also build the testsuite and you can find it at
=programs/winetest/winetest.exe.= To run it follow the instructions in Section
"Running WineTest in Wine" at
http://wiki.winehq.org/ConformanceTests
Expected outcome is the result showing up at test.winehq.org.
- Tags: testsuite, linux, wine
- Categories: Quality Assurance
COPYLEFT GAMES
Webchat input history recall with up/down arrows**
Many chat clients allow you to press the up/down arrow to recall what you've
previously typed. This may be useful functionality for our webchat client.
Implementing this will require keeping a FIFO buffer of previous input
entries, storing only a certain number of entries so that long-term webchat
use doesn't continue to grow memory use. The limit may be dozens of messages,
just not unlimited. Starting with a down arrow should recall the oldest
message in the buffer. When done, attach your changed commands.js to this
task.
- Tags: xmpp, javascript
- Categories: Code, Outreach/Research
SUGAR LABS
Update Turtle Blocks Manual
Research and Update this turtle Block Manual with the features of the latest
released version:
http://people.sugarlabs.org/walter/TurtleBlocksAdvancedBlocksManual.pdf
- Tags: turtle blocks, documentation
- Categories: Documentation/Training, Outreach/Research
METABRAINZ FOUNDATION
Create a "how to" for adding a place
We currently have a number of how tos,
but none of them cover adding a
place. Look at the current How To ideas
on how to structure this article and write the article as a subpage for your
wiki user (e.g.,
https://wiki.musicbrainz.org/User).
- Tags: wiki, documentation, places
- Categories: Documentation/Training
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2024-07-23 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2024-07-23 UTC."],[[["\u003cp\u003eDuring registration, organizations must provide ~25 sample tasks and commit to creating at least 50 diverse tasks across categories like coding, documentation, outreach, quality assurance, and design for students.\u003c/p\u003e\n"],["\u003cp\u003eGoogle emphasizes clear, comprehensive task descriptions with appropriate scope, complexity, and tags for searchability, using external resources for supplemental information only.\u003c/p\u003e\n"],["\u003cp\u003eSample tasks from previous contests, showcasing diverse organizations and task types, are available in the archive to guide task creation.\u003c/p\u003e\n"]]],["During registration, provide approximately 25 sample tasks, ensuring you can create at least 50 unique tasks later. Tasks should span multiple categories: Code, Documentation/Training, Outreach/Research, Quality Assurance, and Design. Descriptions should be detailed, clear, and include appropriate tags for searchability. The tasks must have appropriate scope, length and complexity. While you can link to external resources, the core description must be on the contest website. Examples include fixing bugs, building applications, running tests, and updating documentation.\n"],null,["# Sample Tasks\n\nWe ask you to provide around 25 sample tasks during registration to demonstrate\nyour commitment and ability to produce at least 50 unique tasks for students to\ncomplete once the contest opens.\n\nGoogle looks for:\n\n- A mix of tasks across multiple categories. (Code, Documentation/Training, Outreach/Research, Quality Assurance, and Design)\n- Tasks of appropriate scope, length, and complexity.\n- Fully fleshed out descriptions with enough information to get started on.\n- Clear and understandable descriptions and titles.\n- Appropriate tags for searchability.\n\nIt is possible to link to external resources for more detail, but the core task\ndescription must be on the contest website.\n\nExamples\n--------\n\nBelow, please find some examples of tasks created by previous participating open\nsource organizations. One size does not fit all -- every organization's tasks\nwill be different -- but these examples should help guide you.\n\nYou can find more in the [archive](https://codein.withgoogle.com/archive).\n\n**KDE**\n[Write the story of WikiToLearn](https://codein.withgoogle.com/archive/2015/organization/6472979839975424/task/4601598969905152/)\n\u003e WikiToLearn has never had an about page, and the information about what it is\n\u003e and how it came to exsitence is scattered in all sorts of places. We need to\n\u003e unify it and make it visible and accessible to the users of the site.\n\n- Tags: content, promotion, wikitolearn\n- Categories: Documentation/Training, Research/Outreach\n\n**KDE**\n[Build any KDE application from git repository](https://codein.withgoogle.com/archive/2015/organization/6472979839975424/task/4629188766072832/)\n\u003e For various tasks in KDE organization, you will be required to build the various\n\u003e KDE applications. This task aims to help you understand how to build various\n\u003e KDE applications on the distribution of your choice.\n\u003e The three easy steps to build any application are:\n\n1. Get source code from the git.\n2. Install required dependencies.\n3. Build the application.\n\n\u003e Ask on the #kde-soc IRC channel for more information. You are required to build\n\u003e KDE application of your choice and document steps you took to build it.\n\n- Tags: cmake, qt, c++\n- Catgegories: Coding\n- Beginner Task\n\n**HAIKU**\n[Fix a bug in the editor Pe](https://codein.withgoogle.com/archive/2015/organization/4777925899452416/task/4744391868547072/)\n\u003e There are several bugs reported for the programmer's editor Pe. Fork the Pe\n\u003e repository, pick an issue and fix it. Submit your fix as pull request (see\n\u003e the HaikuPorter wiki which works pretty much the same).\n\n- Tags: c++, pe\n- Categories: Coding\n\n**FOSSASIA**\n[Run WineTest on Linux and submit the results](https://codein.withgoogle.com/archive/2015/organization/6744396808585216/task/4554599679655936/)\n\u003e First you need to build Wine according to\n\u003e \u003chttp://wiki.winehq.org/BuildingWine\u003e. This\n\u003e will also build the testsuite and you can find it at\n\u003e =programs/winetest/winetest.exe.= To run it follow the instructions in Section\n\u003e \"Running WineTest in Wine\" at\n\u003e \u003chttp://wiki.winehq.org/ConformanceTests\u003e\n\u003e Expected outcome is the result showing up at test.winehq.org.\n\n- Tags: testsuite, linux, wine\n- Categories: Quality Assurance\n\n**COPYLEFT GAMES**\n[Webchat input history recall with up/down arrows](https://codein.withgoogle.com/archive/2015/organization/4935850504749056/task/4967041899429888/)\\*\\*\n\u003e Many chat clients allow you to press the up/down arrow to recall what you've\n\u003e previously typed. This may be useful functionality for our webchat client.\n\u003e Implementing this will require keeping a FIFO buffer of previous input\n\u003e entries, storing only a certain number of entries so that long-term webchat\n\u003e use doesn't continue to grow memory use. The limit may be dozens of messages,\n\u003e just not unlimited. Starting with a down arrow should recall the oldest\n\u003e message in the buffer. When done, attach your changed commands.js to this\n\u003e task.\n\n- Tags: xmpp, javascript\n- Categories: Code, Outreach/Research\n\n**SUGAR LABS**\n[Update Turtle Blocks Manual](https://codein.withgoogle.com/archive/2015/organization/5117750959669248/task/4591217765515264/)\n\u003e Research and Update this turtle Block Manual with the features of the latest\n\u003e released version:\n\u003e \u003chttp://people.sugarlabs.org/walter/TurtleBlocksAdvancedBlocksManual.pdf\u003e\n\n- Tags: turtle blocks, documentation\n- Categories: Documentation/Training, Outreach/Research\n\n**METABRAINZ FOUNDATION**\n[Create a \"how to\" for adding a place](https://codein.withgoogle.com/archive/2015/organization/5644885180809216/task/4538012515958784/)\n\u003e We currently have a number of [how tos](https://wiki.musicbrainz.org/How_To),\n\u003e but none of them cover adding a\n\u003e [place](https://musicbrainz.org/doc/Place). Look at the current How To ideas\n\u003e on how to structure this article and write the article as a subpage for your\n\u003e wiki user (e.g.,\n\u003e \u003chttps://wiki.musicbrainz.org/User\u003e).\n\n- Tags: wiki, documentation, places\n- Categories: Documentation/Training"]]
