Bug 1172618

Summary: [RFE] [Fedora] Allow anonymous pull from Zanata
Product: [Retired] Zanata Reporter: Vojtech Trefny <vtrefny>
Component: UsabilityAssignee: Alex Eng <aeng>
Status: CLOSED CURRENTRELEASE QA Contact: Zanata-QA Mailling List <zanata-qa>
Severity: high Docs Contact:
Priority: high    
Version: unspecifiedCC: atodorov, camunoz, damason, dcantrell, dchen, djansen, jreznik, mattdm, mkim, mkolman, noriko, sbueno, sflaniga, vpodzime, zanata-bugs
Target Milestone: ---   
Target Release: 3.6   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: 3
Clone Of:
: 1206995 (view as bug list) Environment:
Last Closed: 2015-04-20 00:29:52 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 1203516, 1206995    

Description Vojtech Trefny 2014-12-10 13:19:30 UTC
Pulling translations from Zanata currently requires login/apikey. It would be great if anonymous users could pull translations.

It would allow us to include a "translation update" target directly into Makefile without forcing people to create an account at Zanata.org or without storing po files in Git repository.

Currently for example Anaconda uses downloading new translation files as part of make target for a new version release (we are using Transifex, (that also doesn't allow anonymous pull) but with planned Fedora to switch to Zanata, anonymous pulls would be really great for us).

Comment 1 Vratislav Podzimek 2014-12-10 13:41:19 UTC
There are many projects that would really welcome such feature.

Comment 2 Martin Kolman 2015-01-07 11:10:41 UTC
I'm the maintainer of Initial Setup and python-meh, both of which will also use Zanata for translation in the near future, so I would also appreciate anonymous pull support in Zanata, so that users/potential-contributors could build these two applications more easily (without the need to register somewhere).

Comment 3 Carlos Munoz 2015-01-14 02:15:18 UTC
Notes from our estimation:

- Only for pull source and translation, stats (project level and contributor level).
- Rate limiting by IP
  - Verify it works with direct jboss, Apache, nginx type setups

Comment 4 Alexander Todorov 2015-02-24 12:52:10 UTC
+1 from a user stand point. 

I'm currently trying to build anaconda from git and don't even have an account with Transifex or Zanata.

Comment 5 David Cantrell 2015-03-06 20:37:22 UTC
This is a huge workflow issue right now.  Can the priority be increased on this functionality?  The functionality right now requires any contributors to our projects to also set up a Zanata account just to do local test builds of projects.  This is because our build process pulls down the latest translations at build time, which then feeds in to the images that are built.

This was a limitation in Transifex too, it would be nice to not also have the same limitation in Zanata.

Comment 6 Michelle Kim 2015-03-09 22:48:48 UTC
Thanks everyone for your comments. As I see increased demand for this feature, I am moving this RFE to high priority in our backlog.

Comment 7 Alex Eng 2015-03-19 02:57:08 UTC
Security implementation for Zanata server:

| Client          | Authenticated | Allowed action(Server) |
| have zanata.ini | Yes           | READ/WRITE             | 
| have zanata.ini | No            | READ                   |
| no zanata.ini   | No            | READ                   |

Comment 8 Alex Eng 2015-03-19 03:14:20 UTC
Updated: Security implementation for Zanata server:

| Client             | Authenticated | Allowed action(Server) |
| username/apiKey    | Yes           | READ/WRITE             | 
| username/apiKey    | No            | REJECT                 |
| no username/apikey | No            | READ                   |

Comment 9 Ding-Yi Chen 2015-03-20 00:43:52 UTC
Note that client also need to modify to delegate the check to server.

Comment 12 Brian Lane 2015-03-26 17:01:52 UTC
Please remember that we (Anaconda team) are using zanata-python-client in our build scripts. This applies to Fedora as well as RHEL6 and RHEL7.

Comment 13 Alex Eng 2015-03-26 20:44:10 UTC
This feature involve changes in Zanata-server as well as supported zanata-client (see http://zanata.org/help/cli/cli-install/ for supported client).

However, we are in the progress of bringing our python client up to scratch but unfortunately it's not part of this development.

But as current Zanata user that has authentication, you still can use zanata-python-client to do translation pull from our server.

We will track changes of python client for anonymous pull as separate bug.

Comment 14 Ding-Yi Chen 2015-03-30 01:56:54 UTC
VERIFIED Zanata 3.6.1-SNAPSHOT (git-jenkins-zanata-server-github-pull-requests-3141)

Comment 15 Ding-Yi Chen 2015-03-30 02:07:50 UTC
(In reply to bcl from comment #12)
> Please remember that we (Anaconda team) are using zanata-python-client in
> our build scripts. This applies to Fedora as well as RHEL6 and RHEL7.

zanata-python-client anonymous support should be tracked using Bug 1206995

Comment 17 Ding-Yi Chen 2015-03-31 06:44:41 UTC
zanata-client-3.6.0-1 is pushed to bodhi branch rawhide, fc22, fc21, fc20

Comment 18 Alex Eng 2015-04-20 03:05:08 UTC
Python client request: https://bugzilla.redhat.com/show_bug.cgi?id=1213205

Comment 19 Alex Eng 2015-04-20 03:10:40 UTC
See https://bugzilla.redhat.com/show_bug.cgi?id=1206995 for python client