(cc'ing you just in case but answering to the mailing list only is fine) > Here > there are lots of team collaborating on it such as Bangladesh, Nepal, > Mangolia etc... Hmmm, interesting to learn that some activity occurs in Mongolia. Would you mind pointing these people to me in case they would be interested in working on Debian localization? > > It was decided that > 1. To maximize content sharing and re-use. Training content is a > prime candidate for reuse for example, and we plan to build a list of > preexisting reusable content that can in turn be localized by > individual country. I suppose you mean "language" there..:-) > > 3. Intellectual property issues. If we are translating from existing > content, what is the copyright restriction on that content?A > guideline is to use content under some open content licensing if > possible, and only use proprietary ones when there is absolutely no > choice. We plan to create a set of templates that each country can ask the > publishers to sign to assign copyright or give explicit use > permission, whichever is applicable. One thing to note is that all > content developed will be documented "source" and IP > specification. You have two problems here: -copyright -licensing Abou tcopyright, it's widely accepted that a translation work carries its own copyright which, dependeing on the location in the world may or may not be transferable. I usually recommend keeping the translators' copyright in translated documents. I'm personnally not very fond of the Translation Project way to do it by transferring the copyright to the FSF. About licensing, a translation is usually considered as a derived work and therefore carries the same license as the original work. So, the question is more about choosing appropriate licensing for the original work. Be aware that GFDL has for instance a few debated points, particularly the restrictions put on documents modificiations. I deeply recommend asking for an advice on debian-legal in case you want to decide abou tthe appropriate license for a documentation work. > > 4.To come up with a methodology for assessing user needs when > creating content. For this task, we are gathering the published > literature on user needs and requirement assessment and analysis for > content creation > > I know that Debian Linux already generates most of its manuals using XML > and XSLT. I would be grateful if someone could provide me some details on > how it is being used in Debian Linux. It would be helpful even if some one > could point me to the right direction and I ll try to figure it out.... That's pretty vague and, indeed, while being very happy to hear about these projects, I'm not really sure about what you're expecting from this list's contributors..:-). After all, when it comes at documentation, the "only" (but significant) contribution of the D-I team is the Debian Installation Manual. I would say "just do things like the D-I installation manual" but tht makes a short answer.....:)
Attachment:
signature.asc
Description: Digital signature