GeeklogWiki - User contributions [en]

Calendarv2

2010-11-23T16:49:03Z

Vladv:

== What needs to be done till the alpha release? ==

- Fix Ical Support. 
- Render recurring events immediately after an event was created, not just on page load.

== Future plans/improvements: ==

Calendarv2

2010-11-23T16:48:10Z

Vladv:

== What needs to be done till the alpha release? ==

- Fix Ical Support. 
- Render recurring events immediately after it was created not just on page load.

== Future plans/improvements: ==

Calendarv2

2010-11-23T16:47:16Z

Vladv:

== What needs to be done till the alpha release? ==

- Fix Ical Support. break.
- Render recurring events immediately after it was created not just on page load.

Future plans/improvements:

Calendarv2

2010-11-23T16:44:33Z

Vladv: New page: What needs to be done till the alpha release? - Fix Ical Support. - Render recurring events immediately after it was created not just on page load. Future plans/improvements:

What needs to be done till the alpha release?
- Fix Ical Support.
- Render recurring events immediately after it was created not just on page load.

Future plans/improvements:

Google Code-in

2010-10-29T18:15:30Z

Vladv: /* Test and provide feedback for the new calendar plugin */

= Information for students =

This is a collection of ''possible'' tasks for the [http://code.google.com/opensource/gci/2010-11/ 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 [http://code.google.com/opensource/gci/2010-11/faqs.html Google Code-in FAQ].

If you have questions about a specific task, please contact the mentor(s) listed for the task or post on the [http://eight.pairlist.net/mailman/listinfo/geeklog-devel geeklog-devel mailing list].

= Adding Tasks =

When adding a new task, please keep these things in mind:

* the task should be suitable for 13-18 year olds
* the task should be small-ish, doable in a few hours to a few days
* the task needs to be clearly defined, i.e. when can it be considered "done"?
* the task shouldn't need a lot of explaining to start

Also, when adding a task, please consider to volunteer mentoring it!

= Tasks =

== Move the FAQ to the wiki ==

Description: The [http://www.geeklog.net/faqman/ 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 [http://wiki.geeklog.net/ 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: [[User:Dirk|Dirk Haun]]

== FAQ: Fix occurences of config.php ==

Description: There are a lot of places in the [http://www.geeklog.net/faqman/ Geeklog FAQ] that still refer to the <tt>config.php</tt> 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 <tt>siteconfig.php</tt> or <tt>db-config.php</tt> file now instead.
 Category: Documentation
 Difficulty: easy
 Time: 1-2 hours
 Possible Mentor: [[User:Dirk|Dirk Haun]]

== Review the installation instructions ==

Description: Try to install Geeklog following the [http://www.geeklog.net/docs/english/install.html 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: [[User:Dirk|Dirk Haun]]

== Review the installation instructions ==

Description: Try to install Geeklog following the [http://www.geeklog.net/docs/english/install.html 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: [[User:Dirk|Dirk Haun]]

== Find a replacement for kses ==

Description: Geeklog uses [http://sourceforge.net/projects/kses/ 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: [[User:Dirk|Dirk Haun]]

== Provide a translation for a plugin ==

Description: Geeklog (i.e. the Geeklog Core) has been translated into more than 20 [[What Languages are Available?|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, [[Translations|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 [[What Languages are Available?|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, [[Translations|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 [http://download.openoffice.org/contribute.html 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 [http://www.geeklog.net/filemgmt/index.php?id=711 old flyer] and a [http://geeklog.info/filemgmt/index.php?id=170 poster] that can also be used as a flyer). Refer to the [http://www.geeklog.net/docs/english/ Geeklog Documentation] for a list of features.
 Category: Outreach
 Difficulty: medium
 Time: about 8-12 hours
 Possible Mentor: ???

== Update plugins list ==

Description: Update the [[Unofficial_Plugins|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 [[Submitting Patches|patches]] for issues (bugs and feature requests) in our [http://project.geeklog.net/tracking/ bugtracker]. Your task 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. Note: Your job here is to check that the patch can be applied and whether or not it solves the issue. If it doesn't solve the issue, then providing a correct patch would be a separate task (to be defined after your review).
 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):

* [http://project.geeklog.net/tracking/view.php?id=1143 Update bigdump.php]
* [http://project.geeklog.net/tracking/view.php?id=1141 nl2br breaks the HTML compliance]
* [http://project.geeklog.net/tracking/view.php?id=1111 e-mail autotag]
* [http://project.geeklog.net/tracking/view.php?id=1083 Allow autotag description and link to information page]
* [http://project.geeklog.net/tracking/view.php?id=1078 Provide a "Link Details" view for links in the Links plugin]
* [http://project.geeklog.net/tracking/view.php?id=1077 Use Admin lists in Spam-X plugin]
* [http://project.geeklog.net/tracking/view.php?id=1076 Add a use counter for Spam-X filtering rules]
* [http://project.geeklog.net/tracking/view.php?id=1056 Poll Plugin - Votes do not get counted correctly when updating a poll with multiple questions.]
* [http://project.geeklog.net/tracking/view.php?id=976 "Report this post" option should have a comment field]
* [http://project.geeklog.net/tracking/view.php?id=967 Get rid of the ereg functions]
* [http://project.geeklog.net/tracking/view.php?id=965 Cosmetics: Get rid of the extra yellow-ish borders in advanced editor template]
* [http://project.geeklog.net/tracking/view.php?id=879 The blogroll could be added to the link plugin]
* [http://project.geeklog.net/tracking/view.php?id=838 Make topics sortable like blocks]
* [http://project.geeklog.net/tracking/view.php?id=782 professional header.thtml language attribute]
* [http://project.geeklog.net/tracking/view.php?id=740 Allow users to enter a password on the registration page]
* [http://project.geeklog.net/tracking/view.php?id=728 Comments Form on same page as story]
* [http://project.geeklog.net/tracking/view.php?id=175 FCKeditor doesn't use RTL automatically]
* [http://project.geeklog.net/tracking/view.php?id=157 Add FCK editor to "mail users" utility]

The corresponding bugtracker entries have all been tagged with "[http://project.geeklog.net/tracking/search.php?hide_status_id=90&tag_string=task task]" (please ignore issues that have status "assigned" or "resolved").

To do: Update Time estimates (and possibly Difficulty) for each task before this list goes into Melange.

== Convert the Geeklog Documentation to XHTML ==

Description: The documentation that we ship with Geeklog (14 HTML files in <tt>public_html/docs/english</tt>) are currently HTML 4.01 compliant. Convert them to XHTML 1.0 Strict and confirm XHTML compliance using the [http://validator.w3.org/ W3C validator]. In other words, fix [http://project.geeklog.net/tracking/view.php?id=1145 bug #1145].
 Category: Documentation
 Difficulty: easy
 Time: 4-8 hours
 Possible Mentor: ???

== Rewrite the Geeklog Help Files ==

Description: Geeklog ships with 10 very simple help files in <tt>public_html/help</tt>. Effectively, they only contain a list of required fields for certain forms. Check that the list of required fields is still correct and rewrite the help pages to be more friendly and informative. Design suggestions welcome.
 Category: Documentation
 Difficulty: easy
 Time: about 10 hours
 Possible Mentor: ???

== Look into SPDX for possible use in Geeklog ==

Description: While most of Geeklog's code is licensed under the GPLv2, some third-party code and even some core components (e.g. feed read/write classes) are under different licenses. [http://www.spdx.org/ SPDX], Software Package Data Exchange, promises to help keeping an overview of the various licenses in a software package such as Geeklog, so that license conflicts can be detected easily. We know nothing about SPDX other than that it exists. Have a look into SPDX, provide a short summary of what it actually does, and provide a list of steps that would need to be taken to use if for Geeklog.
 Category: Research
 Difficulty: medium
 Time: 1-2 days
 Possible Mentor: ???

== Give a Geeklog Demo to a friend or family member ==

Description: Find a friend or family member who's interested in running their own website (or already has one). Give them a demonstration of Geeklog and show off it's features. Discuss with them whether Geeklog would be suited for them. Make a list of things that were considered good, bad, or missing.
 Category: Outreach
 Difficulty: easy
 Time: about 4 hours + some preparation
 Possible Mentor: ???

Obviously, this task could be done several times with different people.

== Coding: "Beginner" tasks from the Bugtracker ==

Description: There are some issues (bug reports and feature requests) in out [http://project.geeklog.net/tracking/ bugtracker] that are tagged with "beginner" to indicate that we consider them easy enough to do for a newcomer to the project. They will also help you understand some of the internal workings of Geeklog.
 Category: Code
 Difficulty: medium
 Time: between 4 hours and 2 days, depending on the issue
 Possible Mentors: ??? (preferably more than one)

List of issues (one task per issue):

* [http://project.geeklog.net/tracking/view.php?id=1215 Progress bar during SQL import doesn't move?]
* [http://project.geeklog.net/tracking/view.php?id=1115 More consistency in autotag behaviour with invalid ids]
* [http://project.geeklog.net/tracking/view.php?id=911 make staticpage textarea expandable like story editor + and - Buttons]
* [http://project.geeklog.net/tracking/view.php?id=706 Allow bypass of censorship filter]
* [http://project.geeklog.net/tracking/view.php?id=866 Implement a COM_versionCompare function to work around issues with version_compare]

The corresponding bugtracker entries have all been tagged with "[http://project.geeklog.net/tracking/search.php?hide_status_id=90&tag_string=beginner beginner]" (please ignore issues that have status "assigned" or "resolved").

To do: Update Time estimates (and possibly Difficulty) for each task before this list goes into Melange.

== Redesign the Plugin Editor ==

Description: Geeklog's plugin "editor" is mainly a form that displays some information about a plugin. It really only has options to enable/disable a plugin and possibly to update it. The main issue with this form, however, is that unlike all of the other editors in Geeklog, it has the buttons (save, cancel, ...) at the top of the form. But moving them to the bottom (for consistency) leave some ugly blank space at the top of the form. So the task is to come up with a new design for this form that's both consistent with the rest of Geeklog and also looks nice.
 Category: User interface
 Difficulty: medium
 Time: 2-4 hours
 Possible Mentor: ???

== Design a Stylesheet for Printable Views ==

Description: Geeklog provides simplified "printable" views for articles and static pages. These use a stripped-down <tt>print.css</tt> stylesheet that needs some work to make the printout look nicer, e.g. fonts, spacing, margins. Also: Is there a good way to make links appear in the printout (e.g. for a link saying "click here", make the URL it links to show up in the printout).
 Category: User interface
 Difficulty: medium
 Time: 4-6 hours
 Possible Mentor: ???

== Test and provide feedback for the new calendar plugin ==

Description: You need to install the new calendar plugin and test it. You should provide feedback about bugs you find and about your overall experience. Also, suggestions on improving the plugin are welcome.
 Category: QA
 Difficulty: Medium
 Time: a few hours - 1 day.
 Possible Mentor: [[User:vladv|Vlad Voicu]]

= Stats =

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

Mentors: Dirk, Vinny, Cordiste, Vlad Voicu, (your name here)

User:Vladv

2010-10-29T18:13:46Z

Vladv: New page: vladvoic gmail

vladvoic gmail

Google Code-in

2010-10-29T18:12:33Z

Vladv:

= Information for students =

This is a collection of ''possible'' tasks for the [http://code.google.com/opensource/gci/2010-11/ 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 [http://code.google.com/opensource/gci/2010-11/faqs.html Google Code-in FAQ].

If you have questions about a specific task, please contact the mentor(s) listed for the task or post on the [http://eight.pairlist.net/mailman/listinfo/geeklog-devel geeklog-devel mailing list].

= Adding Tasks =

When adding a new task, please keep these things in mind:

* the task should be suitable for 13-18 year olds
* the task should be small-ish, doable in a few hours to a few days
* the task needs to be clearly defined, i.e. when can it be considered "done"?
* the task shouldn't need a lot of explaining to start

Also, when adding a task, please consider to volunteer mentoring it!

= Tasks =

== Move the FAQ to the wiki ==

Description: The [http://www.geeklog.net/faqman/ 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 [http://wiki.geeklog.net/ 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: [[User:Dirk|Dirk Haun]]

== FAQ: Fix occurences of config.php ==

Description: There are a lot of places in the [http://www.geeklog.net/faqman/ Geeklog FAQ] that still refer to the <tt>config.php</tt> 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 <tt>siteconfig.php</tt> or <tt>db-config.php</tt> file now instead.
 Category: Documentation
 Difficulty: easy
 Time: 1-2 hours
 Possible Mentor: [[User:Dirk|Dirk Haun]]

== Review the installation instructions ==

Description: Try to install Geeklog following the [http://www.geeklog.net/docs/english/install.html 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: [[User:Dirk|Dirk Haun]]

== Review the installation instructions ==

Description: Try to install Geeklog following the [http://www.geeklog.net/docs/english/install.html 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: [[User:Dirk|Dirk Haun]]

== Find a replacement for kses ==

Description: Geeklog uses [http://sourceforge.net/projects/kses/ 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: [[User:Dirk|Dirk Haun]]

== Provide a translation for a plugin ==

Description: Geeklog (i.e. the Geeklog Core) has been translated into more than 20 [[What Languages are Available?|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, [[Translations|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 [[What Languages are Available?|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, [[Translations|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 [http://download.openoffice.org/contribute.html 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 [http://www.geeklog.net/filemgmt/index.php?id=711 old flyer] and a [http://geeklog.info/filemgmt/index.php?id=170 poster] that can also be used as a flyer). Refer to the [http://www.geeklog.net/docs/english/ Geeklog Documentation] for a list of features.
 Category: Outreach
 Difficulty: medium
 Time: about 8-12 hours
 Possible Mentor: ???

== Update plugins list ==

Description: Update the [[Unofficial_Plugins|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 [[Submitting Patches|patches]] for issues (bugs and feature requests) in our [http://project.geeklog.net/tracking/ bugtracker]. Your task 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. Note: Your job here is to check that the patch can be applied and whether or not it solves the issue. If it doesn't solve the issue, then providing a correct patch would be a separate task (to be defined after your review).
 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):

* [http://project.geeklog.net/tracking/view.php?id=1143 Update bigdump.php]
* [http://project.geeklog.net/tracking/view.php?id=1141 nl2br breaks the HTML compliance]
* [http://project.geeklog.net/tracking/view.php?id=1111 e-mail autotag]
* [http://project.geeklog.net/tracking/view.php?id=1083 Allow autotag description and link to information page]
* [http://project.geeklog.net/tracking/view.php?id=1078 Provide a "Link Details" view for links in the Links plugin]
* [http://project.geeklog.net/tracking/view.php?id=1077 Use Admin lists in Spam-X plugin]
* [http://project.geeklog.net/tracking/view.php?id=1076 Add a use counter for Spam-X filtering rules]
* [http://project.geeklog.net/tracking/view.php?id=1056 Poll Plugin - Votes do not get counted correctly when updating a poll with multiple questions.]
* [http://project.geeklog.net/tracking/view.php?id=976 "Report this post" option should have a comment field]
* [http://project.geeklog.net/tracking/view.php?id=967 Get rid of the ereg functions]
* [http://project.geeklog.net/tracking/view.php?id=965 Cosmetics: Get rid of the extra yellow-ish borders in advanced editor template]
* [http://project.geeklog.net/tracking/view.php?id=879 The blogroll could be added to the link plugin]
* [http://project.geeklog.net/tracking/view.php?id=838 Make topics sortable like blocks]
* [http://project.geeklog.net/tracking/view.php?id=782 professional header.thtml language attribute]
* [http://project.geeklog.net/tracking/view.php?id=740 Allow users to enter a password on the registration page]
* [http://project.geeklog.net/tracking/view.php?id=728 Comments Form on same page as story]
* [http://project.geeklog.net/tracking/view.php?id=175 FCKeditor doesn't use RTL automatically]
* [http://project.geeklog.net/tracking/view.php?id=157 Add FCK editor to "mail users" utility]

The corresponding bugtracker entries have all been tagged with "[http://project.geeklog.net/tracking/search.php?hide_status_id=90&tag_string=task task]" (please ignore issues that have status "assigned" or "resolved").

To do: Update Time estimates (and possibly Difficulty) for each task before this list goes into Melange.

== Convert the Geeklog Documentation to XHTML ==

Description: The documentation that we ship with Geeklog (14 HTML files in <tt>public_html/docs/english</tt>) are currently HTML 4.01 compliant. Convert them to XHTML 1.0 Strict and confirm XHTML compliance using the [http://validator.w3.org/ W3C validator]. In other words, fix [http://project.geeklog.net/tracking/view.php?id=1145 bug #1145].
 Category: Documentation
 Difficulty: easy
 Time: 4-8 hours
 Possible Mentor: ???

== Rewrite the Geeklog Help Files ==

Description: Geeklog ships with 10 very simple help files in <tt>public_html/help</tt>. Effectively, they only contain a list of required fields for certain forms. Check that the list of required fields is still correct and rewrite the help pages to be more friendly and informative. Design suggestions welcome.
 Category: Documentation
 Difficulty: easy
 Time: about 10 hours
 Possible Mentor: ???

== Look into SPDX for possible use in Geeklog ==

Description: While most of Geeklog's code is licensed under the GPLv2, some third-party code and even some core components (e.g. feed read/write classes) are under different licenses. [http://www.spdx.org/ SPDX], Software Package Data Exchange, promises to help keeping an overview of the various licenses in a software package such as Geeklog, so that license conflicts can be detected easily. We know nothing about SPDX other than that it exists. Have a look into SPDX, provide a short summary of what it actually does, and provide a list of steps that would need to be taken to use if for Geeklog.
 Category: Research
 Difficulty: medium
 Time: 1-2 days
 Possible Mentor: ???

== Give a Geeklog Demo to a friend or family member ==

Description: Find a friend or family member who's interested in running their own website (or already has one). Give them a demonstration of Geeklog and show off it's features. Discuss with them whether Geeklog would be suited for them. Make a list of things that were considered good, bad, or missing.
 Category: Outreach
 Difficulty: easy
 Time: about 4 hours + some preparation
 Possible Mentor: ???

Obviously, this task could be done several times with different people.

== Coding: "Beginner" tasks from the Bugtracker ==

Description: There are some issues (bug reports and feature requests) in out [http://project.geeklog.net/tracking/ bugtracker] that are tagged with "beginner" to indicate that we consider them easy enough to do for a newcomer to the project. They will also help you understand some of the internal workings of Geeklog.
 Category: Code
 Difficulty: medium
 Time: between 4 hours and 2 days, depending on the issue
 Possible Mentors: ??? (preferably more than one)

List of issues (one task per issue):

* [http://project.geeklog.net/tracking/view.php?id=1215 Progress bar during SQL import doesn't move?]
* [http://project.geeklog.net/tracking/view.php?id=1115 More consistency in autotag behaviour with invalid ids]
* [http://project.geeklog.net/tracking/view.php?id=911 make staticpage textarea expandable like story editor + and - Buttons]
* [http://project.geeklog.net/tracking/view.php?id=706 Allow bypass of censorship filter]
* [http://project.geeklog.net/tracking/view.php?id=866 Implement a COM_versionCompare function to work around issues with version_compare]

The corresponding bugtracker entries have all been tagged with "[http://project.geeklog.net/tracking/search.php?hide_status_id=90&tag_string=beginner beginner]" (please ignore issues that have status "assigned" or "resolved").

To do: Update Time estimates (and possibly Difficulty) for each task before this list goes into Melange.

== Redesign the Plugin Editor ==

Description: Geeklog's plugin "editor" is mainly a form that displays some information about a plugin. It really only has options to enable/disable a plugin and possibly to update it. The main issue with this form, however, is that unlike all of the other editors in Geeklog, it has the buttons (save, cancel, ...) at the top of the form. But moving them to the bottom (for consistency) leave some ugly blank space at the top of the form. So the task is to come up with a new design for this form that's both consistent with the rest of Geeklog and also looks nice.
 Category: User interface
 Difficulty: medium
 Time: 2-4 hours
 Possible Mentor: ???

== Design a Stylesheet for Printable Views ==

Description: Geeklog provides simplified "printable" views for articles and static pages. These use a stripped-down <tt>print.css</tt> stylesheet that needs some work to make the printout look nicer, e.g. fonts, spacing, margins. Also: Is there a good way to make links appear in the printout (e.g. for a link saying "click here", make the URL it links to show up in the printout).
 Category: User interface
 Difficulty: medium
 Time: 4-6 hours
 Possible Mentor: ???

== Test and provide feedback for the new calendar plugin ==

Description: You need to install the new calendar plugin and test it. You should provide feedback about bugs you find and about your overall experience. Also, suggestions on improving the plugin are welcome.
 Category: Testing
 Difficulty: Medium
 Time: a few hours - 1 day.
 Possible Mentor: [[User:vladv|Vlad Voicu]]

= Stats =

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

Mentors: Dirk, Vinny, Cordiste, Vlad Voicu, (your name here)