Summer of Content 2008 Proposals: Difference between revisions
Line 34: | Line 34: | ||
:* Optional: also install the Halo extension for greater usability of SMW. |
:* Optional: also install the Halo extension for greater usability of SMW. |
||
:* Rework the translation infrastructure to take advantage of SMW features |
:* Rework the translation infrastructure to take advantage of SMW features |
||
::* Fix {{tl |
::* Fix {{tl|translation}}, {{tl|translations}}, {{tl|translationlist}}, and related templates to use multiple categories like spanish, translation in progress, translated from english, instead of composite categories. |
||
:::* While you're at it, modularise templates for readability |
:::* While you're at it, modularise templates for readability |
||
::* Optional: rework the [[activities]] page to use SMW inline-query features for the activity list. (This enables language versions of the activities list to stay up-to-date.) |
::* Optional: rework the [[activities]] page to use SMW inline-query features for the activity list. (This enables language versions of the activities list to stay up-to-date.) |
||
::* Optional: use SMW queries to create a {{tl |
::* Optional: use SMW queries to create a {{tl|ll}} language-link template which queries the current page language, detects if the link target exists in that language, and depending on that links to the target in that language or in its original language. |
||
::*An importance/quality rating scale for translations (optional: using a template on the original page which detects missing translations for important languages for important pages) |
::*An importance/quality rating scale for translations (optional: using a template on the original page which detects missing translations for important languages for important pages) |
||
:* Document your work |
:* Document your work |
Revision as of 18:25, 2 March 2008
This is an interim proposals page for the few weeks before the Summer of Content (SoCon) application site goes live.
Use the template below to add your project proposals to this page. Remember that a SoCon project term is 10 weeks long, usually full-time split between one or more contributors. If you leave us with a way to contact you (under "interested people" for each project - wiki user talk pages are great), we'll contact you when the new site is launched and help you port your application there.
Template
Description
A description of the project you're proposing. What are the project's goals? Its motivations (why is this important?) What will be its end deliverables? What skills and/or equipment will be needed to do this project - what are the prerequisite skills and knowledge should the interns working on this project have, what kind of tools or access will they need, and how will these resources be provided?
Discussion
Start some discussion about your proposal here - what questions remain to be worked out? What problems might it hit? What things about the project proposal could be improved? What resources might you pull for it? What people and organizations might it be good to get in touch with? Encourage others to contribute to this section (or contribute to this section, if you're not the original proposal author!)
Interested people
This is a place where people interested in the project can sign up for updates.
- Your name and contact info, and the role you're interested in playing (sponsor, mentor, intern)
- More names and contact info, and the role they're interested in playing (sponsor, mentor, intern)
Multilingual wiki
Description
The OLPC wiki is a respectably-sized mediawiki-based wiki with multilingual content. As deployment continues, it will only get more so. A good multilingual infrastructure for this wiki is IMO possible to implement in the time frame of one Summer of Content internship (for one or two people working together).
Discussion
Comments are of course welcome.
Tentative roadmap
- SMW
- Help install the Semantic Mediawiki (SMW) extension to Mediawiki for the OLPC wiki.
- Optional: also install the Halo extension for greater usability of SMW.
- Rework the translation infrastructure to take advantage of SMW features
- Fix {{translation}}, {{translations}}, {{translationlist}}, and related templates to use multiple categories like spanish, translation in progress, translated from english, instead of composite categories.
- While you're at it, modularise templates for readability
- Optional: rework the activities page to use SMW inline-query features for the activity list. (This enables language versions of the activities list to stay up-to-date.)
- Optional: use SMW queries to create a {{ll}} language-link template which queries the current page language, detects if the link target exists in that language, and depending on that links to the target in that language or in its original language.
- An importance/quality rating scale for translations (optional: using a template on the original page which detects missing translations for important languages for important pages)
- Document your work
- Insofar as possible, the templates should show brief appropriate instructions when they detect a problem (this work is already started).
- These instructions should link to more detailed instruction pages. Existing instructions need to be simplified without losing content.
- Translate/manage translation of documentation into one target language.
- Create pages with inline SMW queries to help keep track of work needed.
- Make a first pass at redoing existing pages to use the new infrastructure
- Ideally use a mediawiki bot to support, but manual intervention will be needed.
- Not necessary to clean up every last remnant, but the main core for the target language should be covered.
- Existing translations without /lang-xx names should get /lang-xx redirects pointing to them.
- (this does not assume that source language is always English, by the way)
- Code multilingual extension to mediawiki so that es.wiki.laptop.org (for example) can be a Spanish entry point to the same database of wiki pages.
- To fix the top bar (tabs and login) is probably an easy chore, involving replacing static checks of the language variable with a function.
- Make the language variable from the URL available to javascript, css, and wiki functions (as a parser function). This is probably a bit more work and some of it is optional. Hacks are acceptable if they work. (This is the one step I am not qualified to mentor -Homunq 13:24, 2 March 2008 (EST))
- To fix the sidebar requires translation, evaluation of available content, and using the results of the above work.
- extra points if the sidebars can be edited from within the wiki by users with the right privileges.
- optional: create a multi-redirect functionality that gives automatic disambiguation using the URL variable for collisions in language names of a page (eg, OLPC, or spanish-portuguese overlaps).
Skill set needed
The team of one or two people should cover the following skill set:
- some PHP experience and willingness to learn more
- Ability to work with complicated, conditional mediawiki templates (see an example)
- Desirable: ability to modify the Mediawiki bot template (in Python, Ruby, Java, or whatever...) to help with recategorizing
- clear writing style, willingness to spend time on documentation
- decent English and fluent in at least one OLPC target language. Preferably Spanish or Portuguese, also Ethiopian, Afghani, Thai, Indian, or Mongolian languages (Amharic, Dari, Pashto, etc.).
Interested people
This is a place where people interested in the project can sign up for updates.
- I could serve as a mentor for everything except the optional PHP step. For that, if there is a Summer of Code person on Mediawiki stuff, they could help with the mentoring. Homunq 13:24, 2 March 2008 (EST)