Massively collaborative sites like wikipedia, YouTube, Flickr and SecondLife are revolutionizing the way in which content is produced and consumed world wide. These new technologies and paradigm will also significantly impact the way that content is
translated. Indeed, the traditional top-down command and control translation paradigms commonly used today are simply not appropriate in a context where content is grown organically from the grassroot.
The
Cross Lingual Wiki Engine project aims at designing, developing and testing lightweight wiki tools that can be used to translate content in this new frontier. The following paper provides an overview of the type of tools we are thinking about:
We are actively looking for partners who can provide in-kind and/or monetary resources to help advance this highly relevant project. We are particularly short on programming resources.
Note that all code produced in the course of this project will be distributed as Open Source software.
Project Participants
During a meeting at the
WikiSym 2007 conference, the following people pledged resources to the project.
| Name and Affiliation | Amount pledged | Type of resource |
|
| Alain Désilets, National Research Council of Canada | 0.5 day per week for 12 months | Requirements Gathering, Programming, Testing and Evaluation |
|
| Louis-Philippe Huberleau, TikiWiki | 4 months full time | Programming
|
| Marc Laporte, TikiWiki | ???? | ????
|
| Nelson Ko, Carleton U | ???? | Requirements Gathering, Testing and Evaluation
|
| Sebastien Paquet, UQO | ??? | ???
|
| Cola Nahaboo, ILOG | Some of his time? + a full time intern for how long? | Requirements Gathering, Programming |
|
| | |
Project Plan
The project will use an agile, incremental approach to develop the tools. We will start by implementing the "Simplest Thing That Could Possibly Work", and quickly deploy them for use on our own site:
www.wiki-translation.com. We will then iteratively refine and expand these minimal features based on user feedback.
Our aim is to develop and evaluate processes and tools that can be used with any wiki engine. However, we will use TikiWiki as our platform for experiment with those concepts. Once we have figured out how to enable translation the wiki-way inside of TikiWiki, other wiki engines will be able to follow suit by emulating what we have done. The project team will strive to document their own experience on a lessons learned page:
The running TikiWiki version and this list of lessons learned will be the main outputs of the project.
Below is an approximate timeline with milestones. Note that those are just indicative of what we are aiming for. Given the highly distributed, mostly volunteer nature of this project, we have no way of garanteeing that certain outputs will be produced by certain dates.
| Time | Activities | Deliverables
|
| Nov-Dec 2007 | Requirements Gathering, User-Centered Design. | User Personaes, Usage scenario, Prioritized list of features
|
| Jan-Feb 2008 | Initial development | First release of running software, First set of lessons learned.
|
| Feb 2008 | Testing and validation of first prototype | Re-prioritized list of features
|
| March-Nov 2008 | Incremental expansion and refinement | Increasingly powerful versions of TikiWiki translation features, increasingly detailed list of lessons learned |
Jan-