Translation gate for doc jobs
Inspired by some discussions here at the summit, I'd like to setup some translation gate for jobs. Patch https://review.openstack.org/93526 (merged) sets up a test that can be invoked with "tox -e checklang" which builds all "supported" manuals. I propose the following: * Setup checking/gating jobs that runs this test and mark it as non-voting. * Create policy on how to handle failures. Proposed policy: * We only gate on manual/language combinations that are translated sufficiently. Right now that's for openstack-manuals Japanese with the Security Guide, HA Guide and Install Guides only. * If an import from transifex fails, creates a failure, we do not approve the import. * If any other patch fails, the failure might get ignored. * In any case of failure, let's send an email to the openstack-i18n mailing list asking them to investigate and fix. What do you think? Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
On 15/05/14 16:49, Andreas Jaeger wrote:
Inspired by some discussions here at the summit, I'd like to setup some translation gate for jobs.
Patch https://review.openstack.org/93526 (merged) sets up a test that can be invoked with "tox -e checklang" which builds all "supported" manuals.
I propose the following:
* Setup checking/gating jobs that runs this test and mark it as non-voting. * Create policy on how to handle failures.
Proposed policy: * We only gate on manual/language combinations that are translated sufficiently. Right now that's for openstack-manuals Japanese with the Security Guide, HA Guide and Install Guides only. * If an import from transifex fails, creates a failure, we do not approve the import. * If any other patch fails, the failure might get ignored. * In any case of failure, let's send an email to the openstack-i18n mailing list asking them to investigate and fix.
What do you think?
Good, but I'd prefer the creation of a bug in openstack-i18n on launchpad, instead of a mailing list post. This way people who are interested in fixing such things can get notified by email (through bug tracker subscriptions), and the mailing list is kept clear for people who just want to translate things and participate in the community in other ways :)
On 05/16/2014 02:02 PM, Tom Fifield wrote:
On 15/05/14 16:49, Andreas Jaeger wrote:
Inspired by some discussions here at the summit, I'd like to setup some translation gate for jobs.
Patch https://review.openstack.org/93526 (merged) sets up a test that can be invoked with "tox -e checklang" which builds all "supported" manuals.
I propose the following:
* Setup checking/gating jobs that runs this test and mark it as non-voting. * Create policy on how to handle failures.
Proposed policy: * We only gate on manual/language combinations that are translated sufficiently. Right now that's for openstack-manuals Japanese with the Security Guide, HA Guide and Install Guides only. * If an import from transifex fails, creates a failure, we do not approve the import. * If any other patch fails, the failure might get ignored. * In any case of failure, let's send an email to the openstack-i18n mailing list asking them to investigate and fix.
What do you think?
Good, but I'd prefer the creation of a bug in openstack-i18n on launchpad, instead of a mailing list post. This way people who are interested in fixing such things can get notified by email (through bug tracker subscriptions), and the mailing list is kept clear for people who just want to translate things and participate in the community in other ways :)
fine with me. I'll document this in the wiki once the job is in, Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
On Thu, May 15, 2014 at 3:49 PM, Andreas Jaeger <aj@suse.com> wrote:
Inspired by some discussions here at the summit, I'd like to setup some translation gate for jobs.
Patch https://review.openstack.org/93526 (merged) sets up a test that can be invoked with "tox -e checklang" which builds all "supported" manuals.
I propose the following:
* Setup checking/gating jobs that runs this test and mark it as non-voting.
I'm fine with this, the only difficulty is that we need to be sure there are knowledgeable people who can troubleshoot when a job fails.
* Create policy on how to handle failures.
Yep, that's what I need, preferably a contact person.
Proposed policy: * We only gate on manual/language combinations that are translated sufficiently. Right now that's for openstack-manuals Japanese with the Security Guide, HA Guide and Install Guides only.
Is sufficiently defined as 50% translated or more? Is a single additional language at 50% enough? Just wanting some metric definition.
* If an import from transifex fails, creates a failure, we do not approve the import.
Agreed.
* If any other patch fails, the failure might get ignored. * In any case of failure, let's send an email to the openstack-i18n mailing list asking them to investigate and fix.
Yep, I like the bug idea as well, seems to help with tracking and "is anyone assigned" sorts of questions. Thanks for working through this! Anne
What do you think?
Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
_______________________________________________ Openstack-docs mailing list Openstack-docs@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
On 05/19/2014 07:27 PM, Anne Gentle wrote:
On Thu, May 15, 2014 at 3:49 PM, Andreas Jaeger <aj@suse.com <mailto:aj@suse.com>> wrote:
Inspired by some discussions here at the summit, I'd like to setup some translation gate for jobs.
Patch https://review.openstack.org/93526 (merged) sets up a test that can be invoked with "tox -e checklang" which builds all "supported" manuals.
I propose the following:
* Setup checking/gating jobs that runs this test and mark it as non-voting.
I'm fine with this, the only difficulty is that we need to be sure there are knowledgeable people who can troubleshoot when a job fails.
There are some as noticed with the last failure ;)
* Create policy on how to handle failures.
Yep, that's what I need, preferably a contact person.
With a bug report, we abstracted this ;)
Proposed policy: * We only gate on manual/language combinations that are translated sufficiently. Right now that's for openstack-manuals Japanese with the Security Guide, HA Guide and Install Guides only.
Is sufficiently defined as 50% translated or more? Is a single additional language at 50% enough? Just wanting some metric definition.
We agreed on only downloading files that are at least translated to 75% - see https://review.openstack.org/92997. So, metric is better than 75 %.
* If an import from transifex fails, creates a failure, we do not approve the import.
Agreed.
* If any other patch fails, the failure might get ignored. * In any case of failure, let's send an email to the openstack-i18n mailing list asking them to investigate and fix.
Yep, I like the bug idea as well, seems to help with tracking and "is anyone assigned" sorts of questions.
Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
The jobs are running, and I've started documenting this here: https://wiki.openstack.org/wiki/Documentation/Builds#Gates Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
participants (3)
-
Andreas Jaeger
-
Anne Gentle
-
Tom Fifield