From vvasilev at redhat.com Mon Feb 1 13:07:23 2016 From: vvasilev at redhat.com (vvasilev at redhat.com) Date: Mon, 1 Feb 2016 13:07:23 +0000 (UTC) Subject: [zanata-users] http://fedora.zanata.org/ Scheduled Maintenance | 01-Feb-2016 13:00:00 UTC In-Reply-To: d9617a48-5ff4-4b11-a541-e40616416f39@support.engineering.redhat.com References: d9617a48-5ff4-4b11-a541-e40616416f39@support.engineering.redhat.com Message-ID: <1248692998.194.1454332043783.JavaMail.jboss@charnet.host.prod.eng.rdu2.redhat.com> COMPLETED ***// SCHEDULED MAINTENANCE REPORT //*** HostName: zanata-fedora.app.mwc.hst.phx2.redhat.com Priority: Medium Scheduled Date: 01-Feb-2016 13:00:00 UTC Estimated Time Required: 15 minutes Performed By: vvasilev People/Groups Impacted: users of zanata Services/Sites Impacted: http://fedora.zanata.org/ Description: Update to zanata 3.8.2 Impact: Service will be unavailable Sign Off: Vadim Grinco ***// SENT FROM CHARNET //*** https://support.engineering.redhat.com/status.jsf Want to escalate an issue find out more here: https://mojo.redhat.com/docs/DOC-1044941 From ttrinks at redhat.com Fri Feb 5 04:58:56 2016 From: ttrinks at redhat.com (ttrinks at redhat.com) Date: Fri, 5 Feb 2016 04:58:56 +0000 (UTC) Subject: [zanata-users] Zanata (translate.engineering.redhat.com) Scheduled Maintenance | 09-Feb-2016 04:00:00 UTC Message-ID: c3b50a9f-5828-47f4-a19a-92bfa5eb0e90@support.engineering.redhat.com --------------------------------------------------------- ***// SCHEDULED MAINTENANCE REPORT //*** HostName: translate.engineering.redhat.com Priority: Medium Scheduled Date: 09-Feb-2016 04:00:00 UTC Estimated Time Required: 30 minutes Performed By: ttrinks People/Groups Impacted: Translators using Zanata on translate.engineering.redhat.com Services/Sites Impacted: Zanata (translate.engineering.redhat.com) Description: Planned upgrade to Zanata 3.8.2. Impact: The Zanata translation framework will not be available during the outage. Sign Off: Vadim Grinco ***// SENT FROM CHARNET //*** https://support.engineering.redhat.com/status.jsf Want to escalate an issue find out more here: https://mojo.redhat.com/docs/DOC-1044941 -------------- next part -------------- A non-text attachment was scrubbed... Name: maintenance.ics Type: text/calendar Size: 1709 bytes Desc: not available URL: From ttrinks at redhat.com Tue Feb 9 03:40:00 2016 From: ttrinks at redhat.com (ttrinks at redhat.com) Date: Tue, 9 Feb 2016 03:40:00 +0000 (UTC) Subject: [zanata-users] Zanata (translate.engineering.redhat.com) Scheduled Maintenance | 09-Feb-2016 04:00:00 UTC Message-ID: c3b50a9f-5828-47f4-a19a-92bfa5eb0e90@support.engineering.redhat.com This maintenance will begin in approximately 20 minutes --------------------------------------------------------- --------------------------------------------------------- ***// SCHEDULED MAINTENANCE REPORT //*** HostName: translate.engineering.redhat.com Priority: Medium Scheduled Date: 09-Feb-2016 04:00:00 UTC Estimated Time Required: 30 minutes Performed By: ttrinks People/Groups Impacted: Translators using Zanata on translate.engineering.redhat.com Services/Sites Impacted: Zanata (translate.engineering.redhat.com) Description: Planned upgrade to Zanata 3.8.2. Impact: The Zanata translation framework will not be available during the outage. Sign Off: Vadim Grinco ***// SENT FROM CHARNET //*** https://support.engineering.redhat.com/status.jsf Want to escalate an issue find out more here: https://mojo.redhat.com/docs/DOC-1044941 From ttrinks at redhat.com Tue Feb 9 04:47:16 2016 From: ttrinks at redhat.com (ttrinks at redhat.com) Date: Tue, 9 Feb 2016 04:47:16 +0000 (UTC) Subject: [zanata-users] Zanata (translate.engineering.redhat.com) Scheduled Maintenance | 09-Feb-2016 04:00:00 UTC In-Reply-To: c3b50a9f-5828-47f4-a19a-92bfa5eb0e90@support.engineering.redhat.com References: c3b50a9f-5828-47f4-a19a-92bfa5eb0e90@support.engineering.redhat.com Message-ID: <288956998.344.1454993235973.JavaMail.jboss@charnet.host.prod.eng.rdu2.redhat.com> COMPLETED COMMENT ADDED BY ttrinks at 09-Feb-2016 04:47:15 UTC Outage complete. translate.engineering.redhat.com has successfully been upgraded. Please report any issues via eng-ops at redhat.com. --------------------------------------------------------- ***// SCHEDULED MAINTENANCE REPORT //*** HostName: translate.engineering.redhat.com Priority: Medium Scheduled Date: 09-Feb-2016 04:00:00 UTC Estimated Time Required: 30 minutes Performed By: ttrinks People/Groups Impacted: Translators using Zanata on translate.engineering.redhat.com Services/Sites Impacted: Zanata (translate.engineering.redhat.com) Description: Planned upgrade to Zanata 3.8.2. Impact: The Zanata translation framework will not be available during the outage. Sign Off: Vadim Grinco ***// SENT FROM CHARNET //*** https://support.engineering.redhat.com/status.jsf Want to escalate an issue find out more here: https://mojo.redhat.com/docs/DOC-1044941 From vvasilev at redhat.com Wed Feb 10 08:54:00 2016 From: vvasilev at redhat.com (vvasilev at redhat.com) Date: Wed, 10 Feb 2016 08:54:00 +0000 (UTC) Subject: [zanata-users] http://translate.zanata.org Incident | 10-Feb-2016 08:45:00 UTC Message-ID: 84c1e4cc-4858-48d4-87ef-ac6b89749ebe@support.engineering.redhat.com --------------------------------------------------------- ***// INCIDENT REPORT //*** HostName: Incident Date: 10-Feb-2016 08:45:00 UTC Elapsed Time of Incident: 15 minutes Performed By: vvasilev People/Groups Impacted: users of zanata Services/Sites Impacted: http://translate.zanata.org Impact: Zanata is unresponsive ***// SENT FROM CHARNET //*** https://support.engineering.redhat.com/status.jsf Want to escalate an issue find out more here: https://mojo.redhat.com/docs/DOC-1044941 -------------- next part -------------- A non-text attachment was scrubbed... Name: maintenance.ics Type: text/calendar Size: 1182 bytes Desc: not available URL: From vvasilev at redhat.com Wed Feb 10 08:56:56 2016 From: vvasilev at redhat.com (vvasilev at redhat.com) Date: Wed, 10 Feb 2016 08:56:56 +0000 (UTC) Subject: [zanata-users] http://translate.zanata.org Incident | 10-Feb-2016 08:45:00 UTC In-Reply-To: 84c1e4cc-4858-48d4-87ef-ac6b89749ebe@support.engineering.redhat.com References: 84c1e4cc-4858-48d4-87ef-ac6b89749ebe@support.engineering.redhat.com Message-ID: <377433328.551.1455094616381.JavaMail.jboss@charnet.host.prod.eng.rdu2.redhat.com> UPDATED COMMENT ADDED BY vvasilev at 10-Feb-2016 08:56:56 UTC Service is up now. There was a big memory usage and EAP had to be restarted. --------------------------------------------------------- ***// INCIDENT REPORT //*** HostName: Incident Date: 10-Feb-2016 08:45:00 UTC Elapsed Time of Incident: 15 minutes Performed By: vvasilev People/Groups Impacted: users of zanata Services/Sites Impacted: http://translate.zanata.org Impact: Zanata is unresponsive ***// SENT FROM CHARNET //*** https://support.engineering.redhat.com/status.jsf Want to escalate an issue find out more here: https://mojo.redhat.com/docs/DOC-1044941 -------------- next part -------------- A non-text attachment was scrubbed... Name: maintenance.ics Type: text/calendar Size: 1334 bytes Desc: not available URL: From sflaniga at redhat.com Fri Feb 12 04:52:42 2016 From: sflaniga at redhat.com (Sean Flanigan) Date: Fri, 12 Feb 2016 14:52:42 +1000 Subject: [zanata-users] [Fwd: NetworkManager and Zanata woes] In-Reply-To: <1455185514.25958.33.camel@v3.sk> References: <1455185514.25958.33.camel@v3.sk> Message-ID: Hi Lubo, (Comments are below.) On 11 February 2016 at 20:11, Lubomir Rintel wrote: > Hello. > > It never says on your site that the list is subscriber-only. :( > > I can't see a reason why it should be either; I'm probably not > interested in stuff that's not Cc-ed to me. > > I'm wondering if you could forward the message for me? > Sorry about the mailing list troubles. We don't allow non-subscribers to post to the lists because it helps to minimise spam. I've added zanata-users to the CC, since this isn't really a Zanata development question. Note that you won't be able to "reply all" unless you join the zanata-users list. > > Thank you, > Lubo > > -------- Forwarded Message -------- > From: zanata-devel-owner at redhat.com > To: lkundrak at v3.sk > Subject: NetworkManager and Zanata woes > Date: Thu, 11 Feb 2016 05:08:57 -0500 > Message-id: > > You are not allowed to post to this mailing list, and your message has > been automatically rejected. If you think that your messages are > being rejected in error, contact the mailing list owner at > zanata-devel-owner at redhat.com. > > > ---------- Forwarded message ---------- > From: Lubomir Rintel > To: zanata-devel at redhat.com > Cc: > Date: Thu, 11 Feb 2016 11:08:45 +0100 > Subject: NetworkManager and Zanata woes > Hi, > > I've tried to use Zanata for NetworkManager. So far my experience has > been rather frustrating. I'm writing in hope that you'd be able and > willing to help me, since I'm still convinced Zanata is the right tool > for the job. > > So, here's what bothers me: > > 0.) I had trouble finding out where to report problems. This is in > fact, why I'm writing a mailing list post instead. > > There's apparently a bugzilla.redhat.com product a JIRA instance and > GitHub issues. I'd prefer to use the Bugzilla, since I find it most > convenient, but I suspect you've deprecated it as it's not in the list > when I click "New". > It should be our JIRA: https://zanata.atlassian.net/ We migrated all our bugzilla issues to JIRA a while back. I'm not sure which Zanata repo has GitHub Issues enabled, but we should probably turn it off. Please let us know! > > 1.) What's the difference between fedora.zanata.org and > translate.zanata.org? > > I've added my project to the former, follwing the Fedora documentation, > only to find out OpenID doesn't work. I should probably have used the > latter, but why does the former exist then? I couldn't find out. > fedora.zanata.org is basically for Fedora projects - only Fedora contributors can log in and submit content or translations. (Think git.fedorahosted.org.) translate.jboss.org is intended for jboss.org projects. translate.zanata.org is intended for any open source project. (Think GitHub.) When you say OpenID doesn't work, are you saying you couldn't log in to fedora.zanata.org with a Fedora account? > > 2.) Presumably translations are often lost or duplicated. > > I've upload my project to the fedora.zanata.org and > translate.zanata.org. Both show different percentage on all languages. > > This really freaks me out. I don't want to loose our translators work. > Well, if the same project is uploaded to multiple instances, it is possible translators will find different instances and submit translations all over the place. I strongly recommend you make all but one of them read-only, and link to your choice of canonical instance. Another reason the stats could be different is the upload problems you've been having (partly because of the Python client). > > 3.) The downloads don't work > > I thought I'll download one translation (I chose "Asamese" language) > and compare them to see what's different, but after an hour it's stuck > on "Download as translation files with "This may take a few minutes to > complete. Processing 1 of 2 50%"". > How were you trying to download? Python client? Web UI? > > 4.) Everything is in general too slow; sometimes too slow to be > actually usable. > > Perhaps it's that the project is too big? > > The initial upload takes many hours to finish and I needed to run it in > busy loop since it's almost guaranteed to fail with a timeout at some > point. > Uploading can be slow, but it should be more reliable with the Java client. > > Also, loading [1] takes 36 seconds for me. > > [1] > https://translate.zanata.org/zanata/iteration/view/NetworkManager/master > > Yes, unfortunately that page has performance problems with the stats gathering. We're definitely hoping to improve that in future versions. > 5.) Python client seems somewhat buggy > > [lkundrak at belphegor NetworkManager]$ zanata version create > [INFO] Loading zanata project config from: > /home/lkundrak/src/NetworkManager/zanata.xml > [INFO] Loading zanata user config from: /home/lkundrak/.config/zanata.ini > [INFO] zanata server: https://fedora.zanata.org > [INFO] zanata python client version: UNKNOWN, zanata server API version: > 3.8.3 > Error 404 - The requested resource/project is not available > Please take a reference in > https://github.com/zanata/zanata/wiki/Python-Client-Troubleshooting > [lkundrak at belphegor NetworkManager]$ > > In fact the version create failed because the version is not there yet. > But there's no way I could tell this is a client bug; the error > handling seems totally broken. The only thing I got was a > broken/unrelated link. > (Which I'm guessing should probably point to https://github.com/zanata/zanata-python-client/wiki/Troubleshooting ) The Python client isn't really supported by the core Zanata team, and I don't recommend using it, partly because it tends to miss out on features which are added to the Java client first, eg features which help with larger file uploads. > > 6.) There's no option to enable tracing in client > > And the error messages are somewhat cryptic to the point the raw HTTP > response would be a lot helpful: > > "error: ''" > > "Exception while decoding No JSON object could be decoded its may due > to file already exists on the server or not a PO file" > > Turns out, the latter is because this is in the actual response body: > > warning: Could not find TextFlow for TextFlowTarget > dd139eab964f6527960f27dad31dfe48 with contents: [] > warning: Could not find TextFlow for TextFlowTarget > 875069b2bcfe1886deff764cb09e4f2c with contents: [??????? ????: nmcli > connection add { ARGUMENTS | help } > ... > > Not sure if it should bother me, but it does given I suspect some > translations get lost. > That just means those translations correspond to English strings which aren't in the POT file. This is usually because they are translations of obsolete strings. In fact, if you were to run msgmerge, they should be marked as obsolete. On the other hand, if you get hundreds and hundreds of them, it may be a sign that you have the wrong PO file for that POT file. > > So here I stand, confused, frustrated and worried about broken > translations. I'd hate to give up attempts to use Zanata since the > translator experience is good, but I completely rely on your help now. > > Perhaps some of you, the Zanata developers, could give importing > NetworkManager translations a try and see what goes wrong. It shouldn't > be too different from other gettext projects; just clone the git repo, > configure it and do a "make -C po NetworkManager.pot" to create the > template file. > > I tracked down the git repo here: git:// anongit.freedesktop.org/NetworkManager/NetworkManager I ran autogen.sh, but I couldn't find all the rpms it wanted - I gave up when I got to 'nss'. So I converted the latest PO I could find into a POT file (gd.po), and I was able to upload the POT and PO file to a test server successfully, so I don't think Zanata is having any trouble parsing your file. I think your upload problem (with the two minute proxy timeout) is because the Python client doesn't support batch uploads for translation files, perhaps combined with general slowness on the server side of things. BTW, the Java client has the HTTP tracing option you wanted: --log-http. I would encourage you to report the problems you have been seeing in the issue tracker: https://zanata.atlassian.net/ Thanks for the feedback, Lubo. > Thank you, > Lubo > Regards, Sean. -- Sean Flanigan Principal Software Engineer Globalisation Tools Engineering Red Hat -------------- next part -------------- An HTML attachment was scrubbed... URL: From aeng at redhat.com Wed Feb 24 00:43:19 2016 From: aeng at redhat.com (Alex Eng) Date: Wed, 24 Feb 2016 10:43:19 +1000 Subject: [zanata-users] Zanata new feature - private project settings Message-ID: Hi, As of Zanata version 3.8, we have introduced "private project" feature which allows project maintainers to control group of users that can translate in their project. You won't need to make any changes if you wish to keep your project open to all translators registered within Zanata. For more information, please see - http://docs.zanata.org/en/release/user-guide/projects/project-settings/#invite-only - https://zanata.atlassian.net/browse/ZNTA-524 --------------------------------------------- Alex Eng Globalisation Tools Engineering DID: +61 3514 8262 Mobile: +614 2335 3457 Red Hat, Asia-Pacific Pty Ltd Level 1, 193 North Quay Brisbane 4000 Office: +61 7 3514 8100 Fax: +61 7 3514 8199 Website: www.redhat.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From ttrinks at redhat.com Fri Feb 26 06:13:33 2016 From: ttrinks at redhat.com (ttrinks at redhat.com) Date: Fri, 26 Feb 2016 06:13:33 +0000 (UTC) Subject: [zanata-users] Internal Zanata instance Scheduled Maintenance | 26-Feb-2016 11:00:00 UTC Message-ID: e13746e6-aea1-4793-8dc4-44048b7cfde8@support.engineering.redhat.com --------------------------------------------------------- ***// SCHEDULED MAINTENANCE REPORT //*** HostName: translate.engineering.redhat.com Priority: High Scheduled Date: 26-Feb-2016 11:00:00 UTC Estimated Time Required: 120 minutes Performed By: ttrinks People/Groups Impacted: Zanata users on translate.engineering.redhat.com Services/Sites Impacted: Internal Zanata instance Description: The VM needs to be shut down in order to remove some obsolete snapshots. Impact: Zanata on translate.engineering.redhat.com will not be able for the duration of the outage. Sign Off: Vadim Grinco ***// SENT FROM CHARNET //*** https://support.engineering.redhat.com/status.jsf Want to escalate an issue find out more here: https://mojo.redhat.com/docs/DOC-1044941 -------------- next part -------------- A non-text attachment was scrubbed... Name: maintenance.ics Type: text/calendar Size: 1591 bytes Desc: not available URL: From ttrinks at redhat.com Fri Feb 26 11:56:17 2016 From: ttrinks at redhat.com (ttrinks at redhat.com) Date: Fri, 26 Feb 2016 11:56:17 +0000 (UTC) Subject: [zanata-users] Internal Zanata instance Scheduled Maintenance | 26-Feb-2016 11:00:00 UTC In-Reply-To: e13746e6-aea1-4793-8dc4-44048b7cfde8@support.engineering.redhat.com References: e13746e6-aea1-4793-8dc4-44048b7cfde8@support.engineering.redhat.com Message-ID: <1126701542.1206.1456487777291.JavaMail.jboss@charnet.host.prod.eng.rdu2.redhat.com> COMPLETED COMMENT ADDED BY ttrinks at 26-Feb-2016 11:56:17 UTC Outage complete. Zanata on translate.engineering.redhat.com is back up and running. Please report any issues via eng-ops at redhat.com. --------------------------------------------------------- ***// SCHEDULED MAINTENANCE REPORT //*** HostName: translate.engineering.redhat.com Priority: High Scheduled Date: 26-Feb-2016 11:00:00 UTC Estimated Time Required: 120 minutes Performed By: ttrinks People/Groups Impacted: Zanata users on translate.engineering.redhat.com Services/Sites Impacted: Internal Zanata instance Description: The VM needs to be shut down in order to remove some obsolete snapshots. Impact: Zanata on translate.engineering.redhat.com will not be able for the duration of the outage. Sign Off: Vadim Grinco ***// SENT FROM CHARNET //*** https://support.engineering.redhat.com/status.jsf Want to escalate an issue find out more here: https://mojo.redhat.com/docs/DOC-1044941