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).
There are many projects that would really welcome such feature.
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).
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
+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.
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.
Thanks everyone for your comments. As I see increased demand for this feature, I am moving this RFE to high priority in our backlog.
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 | ------------------------------------------------------------
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 | ---------------------------------------------------------------
Note that client also need to modify to delegate the check to server.
Pull request: Server: https://github.com/zanata/zanata-server/pull/737 Client: https://github.com/zanata/zanata-client/pull/54
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.
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.
VERIFIED Zanata 3.6.1-SNAPSHOT (git-jenkins-zanata-server-github-pull-requests-3141)
(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
VERIFIED client: https://github.com/zanata/zanata-client/commit/ec984ab39b6a7fc437d3244557209bfd131872e2
zanata-client-3.6.0-1 is pushed to bodhi branch rawhide, fc22, fc21, fc20
Python client request: https://bugzilla.redhat.com/show_bug.cgi?id=1213205
See https://bugzilla.redhat.com/show_bug.cgi?id=1206995 for python client