Difference between revisions of "Google Code-in"

From GeeklogWiki
Jump to: navigation, search
m (that's a documentation task, even though it involves some "research")
(started list of patches to review)
Line 54: Line 54:
 
<br>Difficulty: medium
 
<br>Difficulty: medium
 
<br>Time: about 4-6 hours each
 
<br>Time: about 4-6 hours each
<br>Possible Mentors: preferrably people speaking the language ...
+
<br>Possible Mentors: preferably people speaking the language ...
  
 
== Update a Geeklog (Core) translation ==
 
== Update a Geeklog (Core) translation ==
Line 62: Line 62:
 
<br>Difficulty: medium
 
<br>Difficulty: medium
 
<br>Time: about 4-6 hours each
 
<br>Time: about 4-6 hours each
<br>Possible Mentors: preferrably people speaking the language ...
+
<br>Possible Mentors: preferably people speaking the language ...
  
 
== Create a "Invitation to contribute" page ==
 
== Create a "Invitation to contribute" page ==
Line 87: Line 87:
 
<br>Time: about 1-2 days
 
<br>Time: about 1-2 days
 
<br>Possible Mentor: ???
 
<br>Possible Mentor: ???
 +
 +
== Review Patches ==
 +
 +
Description: We have quite a few patches for issues (bugs and feature requests) in our [http://project.geeklog.net/tracking/ bugtracker]. Your tasks would be to review such a patch, i.e. check that it can be applied to the current Geeklog version; fix it if it can't be applied as-is; check that it does resolve the issue; leave feedback and, if necessary, an updated patch on the issue in the bugtracker.
 +
<br>Category: QA
 +
<br>Difficulty: medium
 +
<br>Time: between 4 hours and 2 days, depending on the patch
 +
<br>Possible Mentors: ??? (preferably more than one)
 +
 +
List of Patches (one task per patch):
 +
 +
* [http://project.geeklog.net/tracking/view.php?id=157 Add FCK editor to "mail users" utility]
  
 
= TBD =
 
= TBD =

Revision as of 12:57, 29 October 2010

Information for students

This is a collection of possible tasks for the Google Code-in. Please note that you can not claim these tasks from here. Should Geeklog be accepted as a mentoring organization, you will be able to claim tasks from the Code-in homepage, once the contest starts.

For more information, please see the Google Code-in FAQ.


Tasks

Move the FAQ to the wiki

Description: The Geeklog FAQ is hard to maintain in its current state (due to technical issues with the FAQ plugin and the fact that contributions can't be included easily). So the idea is to move all the current FAQ topics to the Geeklog Wiki. Hints: One wiki page per FAQ article. Add a FAQ category. Make sure the formatting, e.g. of sample code, is carried over.
Category: Documentation
Difficulty: easy
Time: a few hours
Possible Mentor: Dirk Haun

FAQ: Fix occurences of config.php

Description: There are a lot of places in the Geeklog FAQ that still refer to the config.php that was used for configuration in earlier Geeklog versions. Find and rewrite those sections to refer to the Configuration Admin panel instead. Note: Some occurences may still be valid (e.g. when referring to upgrading from an old version) or may need to refer to the siteconfig.php or db-config.php file now instead.
Category: Documentation
Difficulty: easy
Time: 1-2 hours
Possible Mentor: Dirk Haun

Review the installation instructions

Description: Try to install Geeklog following the installation instructions. Make notes of the problems you have understanding these instructions. Suggest a list of improvements.
Category: Documentation
Difficulty: easy
Time: 1-2 hours
Possible Mentor: Dirk Haun

Review the installation instructions

Description: Try to install Geeklog following the installation instructions. Make notes of the problems you run into following these instructions. Check that the troubleshooting section covers these problems. If not, suggest additions.
Category: Documentation
Difficulty: easy
Time: 1-2 hours
Possible Mentor: Dirk Haun

Find a replacement for kses

Description: Geeklog uses kses as its HTML filter. Since kses is no longer supported, we are looking for a replacement. Research other existing HTML filters and evaluate them. Check features such as filtering abilities (HTML tags + attributes, JavaScript, CSS), ability to close unbalanced HTML tags. Also consider dependency on any frameworks / libraries, ongoing support, and a GPLv2-compatible license.
Category: Research
Difficulty: medium
Time: about 8 hours
Possible Mentor: Dirk Haun

Provide a translation for a plugin

Description: Geeklog (i.e. the Geeklog Core) has been translated into more than 20 languages. However, not all of the plugins we ship with Geeklog have been translated to all those languages yet. If you speak one of those languages, provide a missing translation. (To do: make a full list of the missing translations; this should easily account for 20+ tasks)
Category: Translation
Difficulty: medium
Time: about 4-6 hours each
Possible Mentors: preferably people speaking the language ...

Update a Geeklog (Core) translation

Description: Geeklog (i.e. the Geeklog Core) has been translated into more than 20 languages. However, not all of the Core language files are actively maintained, so some of them are only partially translated. If you speak one of those languages, update one of those translations. (To do: make a full list of the affected translations; this should account for another 10+ tasks)
Category: Translation
Difficulty: medium
Time: about 4-6 hours each
Possible Mentors: preferably people speaking the language ...

Create a "Invitation to contribute" page

Description: When you click to download OpenOffice.org, you are taken to this page that explains how you can contribute to OOo. Design a similar page for Geeklog.
Category: Outreach
Difficulty: medium
Time: about 4 hours
Possible Mentor: ???

Design a flyer

Description: Design a flyer / handout (for inspiration, here's an old flyer and a poster that can also be used as a flyer). Refer to the Geeklog Documentation for a list of features.
Category: Outreach
Difficulty: medium
Time: about 8-12 hours
Possible Mentor: ???

Update plugins list

Description: Update the plugins list and give some basic informations for each one (Description, last available version, last release date, link to support or contact).
Category: Documentation
Difficulty: medium
Time: about 1-2 days
Possible Mentor: ???

Review Patches

Description: We have quite a few patches for issues (bugs and feature requests) in our bugtracker. Your tasks would be to review such a patch, i.e. check that it can be applied to the current Geeklog version; fix it if it can't be applied as-is; check that it does resolve the issue; leave feedback and, if necessary, an updated patch on the issue in the bugtracker.
Category: QA
Difficulty: medium
Time: between 4 hours and 2 days, depending on the patch
Possible Mentors: ??? (preferably more than one)

List of Patches (one task per patch):

TBD

More programming tasks can be lifted from the bugtracker:

  • issues labelled "beginner"
  • issues that have a patch attached: try out the patch


Possible categories: Code, documentation, outreach, QA, research, training, translation, user interface