This wiki was updated to MediaWiki 1.37. If you notice any issues, please report them to admin[at]

openSUSE:GCI 2011

Jump to: navigation, search


After a successful partnership with Google Summer of Code, openSUSE plans to participate in Google Code-in 2011. Google Code-in is a program aimed at pre university students between the age of 13 and 17. openSUSE as a project views it as a great opportunity to introduce to the open source projects and in particular the openSUSE Project.

  • Our Objectives
    • Introduce pre university students to open source projects.
    • To provide small and varied tasks that can be fun, challenging and a healthy educational environment for students.
  • What are the teams tasks?
    • The tasks are divided into 8 various categories as directed by Google which are
  1. Code: Writing or refactoring code
  2. Documentation: Creating and editing documents
  3. Outreach: Community management and outreach, as well as marketing
  4. Quality Assurance: Testing and ensuring code is of high quality
  5. Research: Studying a problem and recommending solutions
  6. Training: Helping others learn more
  7. Translation: Localization (adapting code to your region and language)
  8. User interface: User experience research or user interface design and interaction


The openSUSE projects has a small team of people organizing the Google Summer of Code event.

A few others are also involved, Byunashko Talk - Contributions and Manu Gupta

We are going to divide the tasks in categories as decided by Google. Each category will have its own mentors. Students can simply contact the project mailing list or the mentors with the respective category. Students can either ask for more information related to a particular task or claim a task.


Subscribe and mail to the openSUSE Project mailing list. If direct access to the list fails, please subscribe to the mailing list. Make sure you introduce yourself, give some short bio, what you want to work on or basically what do you like to do. This allows you to get in touch with the community easier.


The contest is open to all students who are at least thirteen (13) years of age and no older than seventeen (17) years of age on November 21, 2011. Students must be enrolled in a pre-university program, e.g. high school, secondary school, or educational institution. All contestants will need to have their parent or guardian's consent to participate where applicable, and we will ask for proof of consent before you can claim any prizes. For full details, see the contest official rules. Remember, by participating in the contest you are agreeing to abide by these rules, so go ahead and take a few minutes now to carefully read through them.


Tasks and Claiming Them

a. Select a Task: In order to submit an Entry to the Contest, Participants must visit the Main Contest Web page at Each of the the relevant Open Source Organizations will add to a list of Tasks on the “List all tasks” page for Participants to attempt to complete. Each Task will identify the problem, explain some general background information, set the time limit for the Task, the degree of difficulty of the task, and define the requirements that an Entry for that Task must meet in order to be designated as a Completed Entry. Each task is assigned a degree of difficulty by the organization posting the task. Tasks deemed “easy” are worth 1 point, tasks deemed “medium” are worth 2 points, and tasks deemed “hard” are worth 4 points.

b. Claim a Task: You claim a Task by selecting “Request to claim the task” from the drop down menu on that Task. You cannot claim a Task that another Participant has claimed UNLESS that Task has been reopened as explained in subsection (d) below. Participants may claim only one Task at a time.

c. Submitting an Entry: Once you finish a Task you have claimed, you submit an Entry by uploading your original work product as an attachment and/or link to the Task. You may then, if you choose, select another Task to work on, claim it in the fashion set forth in subsection (b) above, and submit your Entry to that Task in the manner set forth in this subsection. Entrants will be required to submit varying information, depending on the task. Entrants should review the specific instructions provided for the task to determine what to submit.

d. Reopening a Task: Each Task has a time limit associated with it that is set forth in the Task description. The time period begins to run from when you claim the Task. If you claim a Task but do not submit an Entry for that Task within the allotted time period, you will receive a reminder via email. From the time the reminder is sent, you will have twenty-four (24) hours to either post an Entry or inform the Open Source Organization through a comment to the Task that you will not be posting an Entry. If you fail to post an entry during the 24 hour extension period, the Open Source Organization will reopen the Task for other Participants, any of whom may claim the Task according to the procedure set forth in subsection (b).


A tentative list of tasks can be found at openSUSE:GCI tasks

Information For Mentors

More Information