Difference between revisions of "On Boarding a Localyzer Project"

From Lingoport Wiki
Jump to: navigation, search
(Created page with "= Before On Boarding an LRM project= To on-board a project, a number of basic information is needed: === Globalyzer and LRM === * '''Code Repository Location''' ** The cod...")
 
Line 2: Line 2:
 
To on-board a project, a number of basic information is needed:
  
To on-board a project, a number of basic information is needed:
   
−
=== Globalyzer and LRM ===
 +
=== Code Repository Location ===
   
  +
* The code repository location and branch for the project.
−
* '''Code Repository Location'''
 
−
** The code repository location and branch for the project.
+
** Git locations could look like: https://github.com/group/project ; In addition, the branch for the Git project is needed
−
*** Git locations could look like: https://github.com/group/project ; In addition, the branch for the Git project is needed
 +
** SVN locations could look like: https://svn.group.com/project/trunk
−
*** SVN locations could look like: https://svn.group.com/project/trunk
  
 
** <b>Read and Write Access</b> granted to repository
  
** <b>Read and Write Access</b> granted to repository
   
−
=== LRM ===
 +
=== Users ===
   
  +
* The list of translation requesters. Those members to add to Jenkins so they have permission to trigger the Prep Kit job: <code> username1@company.org, username2@companyname.com </code>
−
* '''Users'''
  
−
** The list of translation requesters. Those members to add to Jenkins so they have permission to trigger the Prep Kit job: <code> username1@company.org, username2@companyname.com </code>
 +
* The list of emails to be notified of the LRM actions: <code> username1@company.org, username2@companyname.com, username3@companyname.com </code> Note: All emails will also be used as Dashboard user identifiers.
−
** The list of emails to be notified of the LRM actions: <code> username1@company.org, username2@companyname.com, username3@companyname.com </code> Note: All emails will also be used as Dashboard user identifiers.
 
   
−
* '''Locales'''
 +
=== Locales ===
−
** The locale of the files created by developers and to be translated
  
−
** The list of target translation locales
 
−
** The pseudo-locale
  
   
  +
* The locale of the files created by developers and to be translated
−
* '''Resource Files'''
  
  +
* The list of target translation locales
−
** Files types (for instance .properties, .resx, etc.)
  
  +
* The pseudo-locale
−
** Naming convention for the base file: for instance '''<filename>_en.properties''' or '''<filename>.properties'''
  
−
** Translated file naming convention: for instance '''<filename>_fr_FR.properties'''
  
−
** The files or directories which follow the above convention but should NOT be translated. For instance **/config*.properties
  
   
−
=== Globalyzer ===
 +
=== Resource File types ===
   
  +
* Files types (for instance .properties, .resx, etc.)
−
* '''Globalyzer Scan Information'''
  
  +
* Naming convention for the base file: for instance '''<filename>_en.properties''' or '''<filename>.properties'''
−
** The directories files to be scanned
  
  +
* Translated file naming convention: for instance '''<filename>_fr_FR.properties'''
−
** The rulesets to be used to scan the source code.
 
  +
* The files or directories which follow the above convention but should NOT be translated. For instance **/config*.properties
   
   
  +
−
== Next Step ==
  
−
[[On Boarding the Automation Job]]
 +
= On Boarding the Automation Job =

Revision as of 22:02, 10 December 2019

Before On Boarding an LRM project

To on-board a project, a number of basic information is needed:

Code Repository Location

Users

  • The list of translation requesters. Those members to add to Jenkins so they have permission to trigger the Prep Kit job: username1@company.org, username2@companyname.com
  • The list of emails to be notified of the LRM actions: username1@company.org, username2@companyname.com, username3@companyname.com Note: All emails will also be used as Dashboard user identifiers.

Locales

  • The locale of the files created by developers and to be translated
  • The list of target translation locales
  • The pseudo-locale

Resource File types

  • Files types (for instance .properties, .resx, etc.)
  • Naming convention for the base file: for instance <filename>_en.properties or <filename>.properties
  • Translated file naming convention: for instance <filename>_fr_FR.properties
  • The files or directories which follow the above convention but should NOT be translated. For instance **/config*.properties


On Boarding the Automation Job

Retrieved from "http://wiki.lingoport.com/index.php?title=On_Boarding_a_Localyzer_Project&oldid=94040"