History: Cross Lingual Wiki Engine Project Proposal

Source of version: 43 (current)

||''One-liner summary:'' __We're going to develop and evaluate processes and tools for collaborative translation that can be used with any wiki engine. We're looking for partners!__|| !!Introduction Massively collaborative environments like Wikipedia, YouTube, Flickr and Second Life 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 grassroots. 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 demo provides an overview of the type of tools we are thinking about: * http://lizzy.iit.nrc.ca/LizzyHelp/uploads/demo_of_multilingual_LizzyWiki_features.mov A more detailed analysis of the issues can be found in the following research paper: * Désilets, A., Gonzalez, L., Paquet, S., Stojanovic, M. [http://iit-iti.nrc-cnrc.gc.ca/publications/nrc-48736_e.html|Translation the Wiki Way.] In: Proceedings of the WikiSym 2006 - The Conference Wiki of the 2006 International Symposium. Odense, Denmark. August 21-23, 2006. We are actively looking for partners who can provide in-kind and/or monetary resources to help advance this highly relevant project. We are especially short on programming resources. All code produced in the course of this project will be distributed as Open Source software. !!Project Participants and Resources During a meeting at the [http://www.wikisym.org/ws2007/|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 Huberdeau__, École de technologie supérieure|1 day per week|Programming __Marc Laporte__, TikiWiki| $2000 | Money, Requirements Gathering, Testing and Evaluation __Nelson Ko__, Carleton U| 0.5 day per week for 6 months | Requirements Gathering, Testing and Evaluation __Sebastien Paquet__, UQAM| 0.5 day per week for 6 months | Reqs, Evaluation, Writeups | __Colas Nahaboo__, ILOG|TBD (possibility of a full time intern for a few months)|Requirements Gathering, Programming| | | || We are currently looking for financial support for a full-time programmer for one year. !!Project Plan The project will take an agile, incremental and user-centered approach to developing the tools. We will start by implementing the "Simplest Thing That Could Possibly Work", and quickly deploy it for use on our own site (www.wiki-translation.com), and possibly other more corporate sites (ex: ILOG, the Mozilla support site). We will then enter a longer phase where we will 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 initial development platform. 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. In order to facilitate this type of emulation, the project team will strive to continuously document their own experience on a lessons learned page: * ((Lessons Learned from the Cross Lingual Wiki Engine Project)) as well as developer blogs and project discussion forums. The running code for the cross-lingual version of TikiWiki, and the list of lessons learned, will be the two 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 guaranteeing that specific outputs will be produced by specific 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||