Advanced Branching - Revision history

Rdaly at 22:35, 9 July 2021

2021-07-09T22:35:00Z

← Older revision		Revision as of 22:35, 9 July 2021
Line 27:		Line 27:
	</pre>		</pre>

	Keeping track of what has been translated, what has been sent to translation, what is being returned from translation, in what order, for what locale, while passing validating checks on the resource files is time consuming and a pain point for most development organizations. Lingoport Resource Manager (LRM), the Lingoport product, seamlessly automates the checking, sending, and receiving of resource files.		Keeping track of what has been translated, what has been sent to translation, what is being returned from translation, in what order, for what locale, while passing validating checks on the resource files is time consuming and a pain point for most development organizations. Localyzer, formerly known as Lingoport Resource Manager (LRM), the Lingoport product, seamlessly automates the checking, sending, and receiving of resource files.

	~~LRM~~ needs a branch from which to find the resource files to be translated and to which to push the translated files. A straightforward way to [[Terms_and_Definitions#onboarding\|on-board]] ~~LRM~~ projects is to dedicate one branch to translation. ~~LRM~~ can rebase so that the translation branch also gets the commits from master or a deploy branch, keeping it up to date with the overall source code development. This makes for an easy ~~LRM~~ project, where files are picked up from the translation branch and pushed back to the translation branch exclusively.		Localyzer needs a branch from which to find the resource files to be translated and to which to push the translated files. A straightforward way to [[Terms_and_Definitions#onboarding\|on-board]] Localyzer projects is to dedicate one branch to translation. Localyzer can rebase so that the translation branch also gets the commits from master or a deploy branch, keeping it up to date with the overall source code development. This makes for an easy Localyzer project, where files are picked up from the translation branch and pushed back to the translation branch exclusively.

	The benefit with this approach is the simplicity of the on-boarding and knowing only the translation branch will be affected by ~~LRM~~. The drawback is that localization happens after all the development is done in a branch separate from everything else.		The benefit with this approach is the simplicity of the on-boarding and knowing only the translation branch will be affected by Localyzer. The drawback is that localization happens after all the development is done in a branch separate from everything else.

	= Feature Branching =		= Feature Branching =
Line 38:		Line 38:

	=Lingoport Advanced Branching=		=Lingoport Advanced Branching=
	LingoBot is a chatbot which works within collaborative environments such as Slack or MS Teams. The user issues commands that the chatbot passes along to ~~LRM~~. Here is an example of a session of LingoBot in Slack:		LingoBot is a chatbot which works within collaborative environments such as Slack or MS Teams. The user issues commands that the chatbot passes along to Localyzer. Here is an example of a session of LingoBot in Slack:

	[[File:AB1.png\|center\|500px]]		[[File:AB1.png\|center\|500px]]
Line 50:		Line 50:
	[[File:AB2.png\|center\|500px]]		[[File:AB2.png\|center\|500px]]

	When the translation is done and sent back to the repository automatically by ~~LRM~~, a Slack notification will let that room know:		When the translation is done and sent back to the repository automatically by Localyzer, a Slack notification will let that room know:

	[[File:AB3.png\|center\|500px]]		[[File:AB3.png\|center\|500px]]

	Note: It also provides a link to GitHub in this instance to the repository where the files were pushed and another link to the ~~LRM~~ Dashboard.		Note: It also provides a link to GitHub in this instance to the repository where the files were pushed and another link to the Localyzer Dashboard.

	= LingoBot and I18n =		= LingoBot and I18n =

Rdaly: /* LingoBot and I18n */

2019-07-18T23:59:36Z

LingoBot and I18n

← Older revision		Revision as of 23:59, 18 July 2019
Line 61:		Line 61:
	[[File:AB4.png\|center\|500px]]		[[File:AB4.png\|center\|500px]]

	LingoBot scanned the Myster branch of the CET.LiteDemo project using the ruleset for Java. It found no scan differences between the main branch and the code changes in the Mystero branch		LingoBot scanned the '''Myster''' branch of the '''CET.LiteDemo''' project using the ruleset for Java. It found no scan differences between the main branch and the code changes in the Mystero branch and reported it.

	= Conclusion=		= Conclusion=
	Lingoport provides an elegant solution to complex branching and all the resource files which works from collaborative environments that developers and other team members are already familiar with. They only need to know a few simple commands, and the automation takes over. This fits in with the way software development is done in most modern companies.		Lingoport provides an elegant solution to complex branching and all the resource files which works from collaborative environments that developers and other team members are already familiar with. They only need to know a few simple commands, and the automation takes over. This fits in with the way software development is done in most modern companies.

Rdaly: /* LingoBot and I18n */

2019-07-18T23:58:51Z

LingoBot and I18n

← Older revision		Revision as of 23:58, 18 July 2019
Line 60:		Line 60:

	[[File:AB4.png\|center\|500px]]		[[File:AB4.png\|center\|500px]]

			LingoBot scanned the Myster branch of the CET.LiteDemo project using the ruleset for Java. It found no scan differences between the main branch and the code changes in the Mystero branch

	= Conclusion=		= Conclusion=
	Lingoport provides an elegant solution to complex branching and all the resource files which works from collaborative environments that developers and other team members are already familiar with. They only need to know a few simple commands, and the automation takes over. This fits in with the way software development is done in most modern companies.		Lingoport provides an elegant solution to complex branching and all the resource files which works from collaborative environments that developers and other team members are already familiar with. They only need to know a few simple commands, and the automation takes over. This fits in with the way software development is done in most modern companies.

Rdaly: /* LingoBot and I18n */

2019-07-18T23:55:37Z

LingoBot and I18n

← Older revision		Revision as of 23:55, 18 July 2019
Line 57:		Line 57:

	= LingoBot and I18n =		= LingoBot and I18n =
	Another ~~usage~~ of LingoBot is to ask for the i18n issues for the files which were modified in that branch. A team of developers may modify a few files during a sprint. The overall code base may have a huge amount of files. To make sure the new code does not have more i18n issues, the command is ‘i18n scan’. It will use the Globalyzer configuration for that project to scan only those files which were modified in that branch.		Another use of LingoBot is to ask for the i18n issues for the files which were modified in that branch. A team of developers may modify a few files during a sprint. The overall code base may have a huge amount of files. To make sure the new code does not have more i18n issues, the command is '''‘i18n scan’'''. It will use the Globalyzer configuration for that project to scan only those files which were modified in that branch.

	[[File:AB4.png\|center\|500px]]		[[File:AB4.png\|center\|500px]]

Rdaly: /* Lingoport Advanced Branching */

2019-07-18T23:54:28Z

Lingoport Advanced Branching

← Older revision		Revision as of 23:54, 18 July 2019
Line 46:		Line 46:
	The system gives an overview of the status and a link to go to the Dashboard to see more information. In this case, he sees that '''German (de)''' is '''88%''' translated, but there are still '''7 files''' to be translated that have '''186 keys''' and '''871 words''' to be translated.		The system gives an overview of the status and a link to go to the Dashboard to see more information. In this case, he sees that '''German (de)''' is '''88%''' translated, but there are still '''7 files''' to be translated that have '''186 keys''' and '''871 words''' to be translated.

	At some point, when the development team is ready, the files need to be sent for translation. Instead of hand-picking the files from the right repository, the right directories, the right branch, verifying the correctness of the files to be sent, how many to send, tracking the files in a spreadsheet, sending an email with attached files, having the attached files downloaded on the translation side, checking the files, on-board a new TMS project, it’s simply a command to tell LingoBot to send whatever is needed to be translated:		At some point, when the development team is ready, the files need to be sent for translation. Instead of hand-picking the files from the right repository, the right directories, the right branch, verifying the correctness of the files to be sent, how many to send, tracking the files in a spreadsheet, sending an email with attached files, having the attached files downloaded on the translation side, checking the files, on-board a new TMS project, it’s simply a command ('''translate''') to tell LingoBot to send whatever is needed to be translated:

	[[File:AB2.png\|center\|500px]]		[[File:AB2.png\|center\|500px]]

Rdaly: /* Lingoport Advanced Branching */

2019-07-18T23:53:21Z

Lingoport Advanced Branching

← Older revision		Revision as of 23:53, 18 July 2019
Line 44:		Line 44:
	Here the user “Andrew Wong” wanted to check the '''translation status''' of a branch, '''F1404-desktop-group-delivery''', for a repository called '''‘SSTO.webapp’'''. There may be lots of different branches on this repository. The one that Andrew Wong is interested in is only the '''“F1404-desktop-group-delivery”''' branch. That’s where the feature is being developed.		Here the user “Andrew Wong” wanted to check the '''translation status''' of a branch, '''F1404-desktop-group-delivery''', for a repository called '''‘SSTO.webapp’'''. There may be lots of different branches on this repository. The one that Andrew Wong is interested in is only the '''“F1404-desktop-group-delivery”''' branch. That’s where the feature is being developed.

	The system gives an overview of the status and a link to go to the Dashboard to see more information. In this case, he sees that German (de) is 88% translated, but there are still 7 files to be translated that have ~~xxx~~ keys and ~~xxx~~ words to be ~~sent~~.		The system gives an overview of the status and a link to go to the Dashboard to see more information. In this case, he sees that '''German (de)''' is '''88%''' translated, but there are still '''7 files''' to be translated that have '''186 keys''' and '''871 words''' to be translated.

	At some point, when the development team is ready, the files need to be sent for translation. Instead of hand-picking the files from the right repository, the right directories, the right branch, verifying the correctness of the files to be sent, how many to send, tracking the files in a spreadsheet, sending an email with attached files, having the attached files downloaded on the translation side, checking the files, on-board a new TMS project, it’s simply a command to tell LingoBot to send whatever is needed to be translated:		At some point, when the development team is ready, the files need to be sent for translation. Instead of hand-picking the files from the right repository, the right directories, the right branch, verifying the correctness of the files to be sent, how many to send, tracking the files in a spreadsheet, sending an email with attached files, having the attached files downloaded on the translation side, checking the files, on-board a new TMS project, it’s simply a command to tell LingoBot to send whatever is needed to be translated:

Rdaly: /* Lingoport Advanced Branching */

2019-07-18T23:52:07Z

Lingoport Advanced Branching

← Older revision		Revision as of 23:52, 18 July 2019
Line 44:		Line 44:
	Here the user “Andrew Wong” wanted to check the '''translation status''' of a branch, '''F1404-desktop-group-delivery''', for a repository called '''‘SSTO.webapp’'''. There may be lots of different branches on this repository. The one that Andrew Wong is interested in is only the '''“F1404-desktop-group-delivery”''' branch. That’s where the feature is being developed.		Here the user “Andrew Wong” wanted to check the '''translation status''' of a branch, '''F1404-desktop-group-delivery''', for a repository called '''‘SSTO.webapp’'''. There may be lots of different branches on this repository. The one that Andrew Wong is interested in is only the '''“F1404-desktop-group-delivery”''' branch. That’s where the feature is being developed.

	The system gives an overview of the status and a link to go to the Dashboard to see more information.		The system gives an overview of the status and a link to go to the Dashboard to see more information. In this case, he sees that German (de) is 88% translated, but there are still 7 files to be translated that have xxx keys and xxx words to be sent.
	At some point, when the development team is ready, the files need to be sent for translation. Instead of hand-picking the files from the right repository, the right directories, the right branch, verifying the correctness of the files to be sent, how many to send, tracking the files in a spreadsheet, sending an email with attached files, having the attached files downloaded on the translation side, checking the files, on-board a new TMS project, it’s simply a command to tell LingoBot to send whatever is needed to be translated:		At some point, when the development team is ready, the files need to be sent for translation. Instead of hand-picking the files from the right repository, the right directories, the right branch, verifying the correctness of the files to be sent, how many to send, tracking the files in a spreadsheet, sending an email with attached files, having the attached files downloaded on the translation side, checking the files, on-board a new TMS project, it’s simply a command to tell LingoBot to send whatever is needed to be translated:

Rdaly: /* Lingoport Advanced Branching */

2019-07-18T23:50:55Z

Lingoport Advanced Branching

← Older revision		Revision as of 23:50, 18 July 2019
Line 42:		Line 42:
	[[File:AB1.png\|center\|500px]]		[[File:AB1.png\|center\|500px]]

	Here the user “Andrew Wong” wanted to check the '''translation status''' of a branch, '''F1404-desktop-group-delivery''', for a repository called '''‘SSTO.webapp’'''. There may be lots of different branches on this repository. The one that Andrew Wong is interested in is only the '''“F1404-desktop-group-delivery”''' branch. That’s ~~were~~ the feature is being developed.		Here the user “Andrew Wong” wanted to check the '''translation status''' of a branch, '''F1404-desktop-group-delivery''', for a repository called '''‘SSTO.webapp’'''. There may be lots of different branches on this repository. The one that Andrew Wong is interested in is only the '''“F1404-desktop-group-delivery”''' branch. That’s where the feature is being developed.

	The system gives an overview of the status and a link to go to the Dashboard to see more information.		The system gives an overview of the status and a link to go to the Dashboard to see more information.

Rdaly: /* Lingoport Advanced Branching */

2019-07-18T23:50:13Z

Lingoport Advanced Branching

← Older revision		Revision as of 23:50, 18 July 2019
Line 42:		Line 42:
	[[File:AB1.png\|center\|500px]]		[[File:AB1.png\|center\|500px]]

	Here the user “Andrew Wong” wanted to check the translation status of a branch, F1404-desktop-group-delivery, for a repository called ‘SSTO.webapp’. There may be lots of different branches on this repository. The one that Andrew Wong is interested in is only the “F1404-desktop-group-delivery” branch. That’s were the feature is being developed.		Here the user “Andrew Wong” wanted to check the '''translation status''' of a branch, '''F1404-desktop-group-delivery''', for a repository called '''‘SSTO.webapp’'''. There may be lots of different branches on this repository. The one that Andrew Wong is interested in is only the '''“F1404-desktop-group-delivery”''' branch. That’s were the feature is being developed.

	The system gives an overview of the status and a link to go to the Dashboard to see more information.		The system gives an overview of the status and a link to go to the Dashboard to see more information.
	At some point, when the development team is ready, the files need to be sent for translation. Instead of hand picking the files from the right repository, the right directories, the right branch, verifying the correctness of the files to be sent, how many to send, tracking the files in ~~some XL sheet~~, sending an email with attached files, having the attached files downloaded on the translation side, checking the files, on-board a new TMS project, it’s simply a command to tell LingoBot to send whatever is needed to be translated:		At some point, when the development team is ready, the files need to be sent for translation. Instead of hand-picking the files from the right repository, the right directories, the right branch, verifying the correctness of the files to be sent, how many to send, tracking the files in a spreadsheet, sending an email with attached files, having the attached files downloaded on the translation side, checking the files, on-board a new TMS project, it’s simply a command to tell LingoBot to send whatever is needed to be translated:

	[[File:AB2.png\|center\|500px]]		[[File:AB2.png\|center\|500px]]

Rdaly: /* Lingoport Advanced Branching */

2019-07-18T23:48:10Z

Lingoport Advanced Branching

← Older revision		Revision as of 23:48, 18 July 2019
Line 38:		Line 38:

	=Lingoport Advanced Branching=		=Lingoport Advanced Branching=
	LingoBot is a ~~Chatbot~~ which works within collaborative environments such as Slack or MS Teams. The user issues commands that the ~~Chatbot~~ passes along to LRM. Here is an example of a session of LingoBot in Slack:		LingoBot is a chatbot which works within collaborative environments such as Slack or MS Teams. The user issues commands that the chatbot passes along to LRM. Here is an example of a session of LingoBot in Slack:

	[[File:AB1.png\|center\|500px]]		[[File:AB1.png\|center\|500px]]
Line 48:		Line 48:
	[[File:AB2.png\|center\|500px]]		[[File:AB2.png\|center\|500px]]

	When the translation is done and ~~send~~ back to the repository automatically by LRM, a Slack notification will let that room know:		When the translation is done and sent back to the repository automatically by LRM, a Slack notification will let that room know:

	[[File:AB3.png\|center\|500px]]		[[File:AB3.png\|center\|500px]]

	Note: It also ~~provide~~ a link to GitHub in this instance to the repository where the files were pushed and another link to the LRM Dashboard.		Note: It also provides a link to GitHub in this instance to the repository where the files were pushed and another link to the LRM Dashboard.

	= LingoBot and I18n =		= LingoBot and I18n =