Bug 1034575

Summary: RFE: Add Zanata integration to Pressgang CCMS WebUI
Product: [Community] PressGang CCMS Reporter: Tim Hildred <thildred>
Component: CCMS-CoreAssignee: pressgang-ccms-dev
Status: NEW --- QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 1.1   
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Tim Hildred 2013-11-26 06:37:05 UTC 
Description of problem:

Pushing content to translation is currently fraught with the potential for problems. The push-translation mechanism almost always reports topics skipped, so it is hard to tell if you've actually done anything. 

Different teams have come up with documentation on how to get Pressgang content into Zanata, for example:

https://mojo.redhat.com/docs/DOC-18783

Ideally, a process for getting content into Zanata would be mapped out in Pressgang, taking input from translators and writers. You'd wind up with something you could do in the UI, that provided clear feedback on success or failure with good troubleshooting tips on errors.

Then in the UI you'd have 2 to 3 clicks to make the needful thing happen with your current spec and push it through to Zanata, with some follow up checking and reporting on what actually happened on the Zanata side.
Comment 1 Lee Newson 2013-11-26 06:45:25 UTC 
I don't see that much of an issue with the push-translation command, as it always says at the bottom whether it succeeded or failed. Perhaps the errors should be grouped so that it's easier to see all the errors together.

As for doing it in the UI, that is not possible until an asynchronous api exists (see BZ#1013906).