Difference between revisions of "Localization AOO/workPlan"

From Apache OpenOffice Wiki
Jump to: navigation, search
(Created page with "The following is a milestone plan for transition from the current l10n to the new l10n. There are 2 separate project, which will be executed in parallel: == Information project…")
 
 
(3 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 +
{{Note|This page is about a proposal, codename genLang, not implemented yet.}}
 +
 
The following is a milestone plan for transition from the current l10n to the new l10n.
 
The following is a milestone plan for transition from the current l10n to the new l10n.
 +
 +
The plan is updated whenever something major has happened, and only the missing parts are described.
  
 
There are 2 separate project, which will be executed in parallel:
 
There are 2 separate project, which will be executed in parallel:
Line 7: Line 11:
  
 
The milestones are as follows
 
The milestones are as follows
* Update top pages of l10n.openoffice.org (Done, await RTC and commit)
 
* Update all of l10n, remove/update old pages, so old pages have valid content (need RCT, lot of work for committer)
 
 
* Update all of wiki localization/l10n
 
* Update all of wiki localization/l10n
* Make php script for upload/download/register/stat (must be done interactively with committer), here I could really used a skilled php programmer
 
 
* Update country specific pages and contact NLC to get things running
 
* Update country specific pages and contact NLC to get things running
 +
 +
'''Due to what seems to a conflict of interest, this part has been postponed'''
  
 
== Development project ==
 
== Development project ==
Line 17: Line 20:
  
 
The milestones are as follows:
 
The milestones are as follows:
* make SVN branch, to secure stability of AOO while implementing (must be done by committer)
+
* change l10n tools to one tool (genLang) that generates module specific files (instead of a file pr source) and not sdf file
* change l10n tools to generate po files (changes will be quite often, and should be committed)
+
* build "extraction" in genLang tool
 +
* update local git branch, with svn trunk (requires committer)
 +
* build "merge" in genLang tool
 +
* update local git branch, with svn trunk (requires committer)
 +
* QA test of "extraction" process
 +
* update procedures for getting text to pootle
 +
* build "generate" in genLang tool
 +
* update local git branch, with svn trunk (requires committer)
 +
* build "insert" in genLang tool
 +
* update local git branch, with svn trunk (requires committer)
 +
* QA test of flow to/from sources
 
* change build/make to include new target, I need someone to ping-pong with about the best way forward
 
* change build/make to include new target, I need someone to ping-pong with about the best way forward
* QA !! here I could really use some help on how to test it
 
* Merge with SVN main branch (needs committer), at this point: sdf files R.I.P.
 
  
 
The second phase awaits the outcome of a discussion with pootle people (can SVN be used, etc), but assuming yes:
 
The second phase awaits the outcome of a discussion with pootle people (can SVN be used, etc), but assuming yes:
 
* Update Pootle server to work on SVN, here I need help since I have no access at all
 
* Update Pootle server to work on SVN, here I need help since I have no access at all
* activate php scripts
+
* Update Pootle server with missing funnctionality
 
* QA whole process, help would be appreciated (4 eyes are better than 2).
 
* QA whole process, help would be appreciated (4 eyes are better than 2).
* Merge with SVN main branch
 
 
* update documentation.
 
* update documentation.
  
Line 33: Line 43:
  
 
The total calendar time needed is about 2 months, if the committer and I have a very close working order.
 
The total calendar time needed is about 2 months, if the committer and I have a very close working order.
 +
 +
[[Category:L10n]]
 +
[[Category:Localization]]
 +
[[Category:Development]]

Latest revision as of 13:45, 7 July 2018

Documentation note.png This page is about a proposal, codename genLang, not implemented yet.

The following is a milestone plan for transition from the current l10n to the new l10n.

The plan is updated whenever something major has happened, and only the missing parts are described.

There are 2 separate project, which will be executed in parallel:

Information project

This project is the interface to offline translators, NLC and people interested in l10n.

The milestones are as follows

  • Update all of wiki localization/l10n
  • Update country specific pages and contact NLC to get things running

Due to what seems to a conflict of interest, this part has been postponed

Development project

This project is mainly developer and integrator oriented.

The milestones are as follows:

  • change l10n tools to one tool (genLang) that generates module specific files (instead of a file pr source) and not sdf file
  • build "extraction" in genLang tool
  • update local git branch, with svn trunk (requires committer)
  • build "merge" in genLang tool
  • update local git branch, with svn trunk (requires committer)
  • QA test of "extraction" process
  • update procedures for getting text to pootle
  • build "generate" in genLang tool
  • update local git branch, with svn trunk (requires committer)
  • build "insert" in genLang tool
  • update local git branch, with svn trunk (requires committer)
  • QA test of flow to/from sources
  • change build/make to include new target, I need someone to ping-pong with about the best way forward

The second phase awaits the outcome of a discussion with pootle people (can SVN be used, etc), but assuming yes:

  • Update Pootle server to work on SVN, here I need help since I have no access at all
  • Update Pootle server with missing funnctionality
  • QA whole process, help would be appreciated (4 eyes are better than 2).
  • update documentation.

it can be seen, that I need a lot of communication with a committer just for the pure work, I would anyhow appreciate input/comments from time to time.

The total calendar time needed is about 2 months, if the committer and I have a very close working order.

Personal tools