WordPress.org

Making WordPress.org

Opened 3 years ago

Closed 2 years ago

#1089 closed enhancement (maybelater)

gp-import-export plugin for translate.wordpress.org

Reported by: akirk Owned by:
Milestone: Priority: normal
Component: Translate Site & Plugins Keywords: has-patch
Cc:

Description

There has already been some discussion in Slack, this ticket is about installing the following plugin on translate.wordpress.org: https://github.com/Automattic/gp-import-export

The most important reason for this is to allow bulk importing and bulk exporting of iOS and Android strings.

Also included is a patch for the GP_WPorg_Rosetta_Roles plugin. It makes it possible to restrict the usage of this plugin even for people who have admin rights on translate.wordpress.org. This is because it allows the uploading of a ZIP file, which should be restricted as much as possible (the plugin will only be used by @jenia for the moment).

A user who wants to make a bulk-import has to have the GlotPress permission bulk-import for the project, for exporting bulk-export for the project. Also people who are defined as admin within GlotPress can bulk-import or bulk-export.

Attachments (9)

1089.diff (51.9 KB) - added by akirk 3 years ago.
import-step1.png (83.0 KB) - added by akirk 3 years ago.
import-step2.png (119.1 KB) - added by akirk 3 years ago.
import-step3.png (150.9 KB) - added by akirk 3 years ago.
export.png (182.3 KB) - added by akirk 3 years ago.
Screenshot from 2015-07-08 09-49-21.png (388.2 KB) - added by stephdau 3 years ago.
Without patch: all admin functions available
Screenshot from 2015-07-08 09-49-42.png (357.2 KB) - added by stephdau 3 years ago.
With patch applied: losing privileges
1089.2.diff (50.7 KB) - added by stephdau 3 years ago.
Working patch.
1089.3.diff (30.3 KB) - added by akirk 3 years ago.

Download all attachments as: .zip

Change History (16)

@akirk
3 years ago

@akirk
3 years ago

@akirk
3 years ago

@akirk
3 years ago

@akirk
3 years ago

This ticket was mentioned in Slack in #meta-i18n by akirk. View the logs.


3 years ago

@stephdau
3 years ago

Without patch: all admin functions available

@stephdau
3 years ago

With patch applied: losing privileges

#2 @stephdau
3 years ago

I've applied the patch to my dotorg sandbox, but I lose all my privileges as soon as the Rosetta file is patched.

#3 @stephdau
3 years ago

I therefore get the "You are not allowed to do this." message when trying to get to the importer and exporter routes.

@stephdau
3 years ago

Working patch.

@akirk
3 years ago

#4 @akirk
3 years ago

This new patch now includes improvements for importing bigger pot files (by importing each one separately).

#5 @samuelsidler
2 years ago

Thinking through this a bit longer, I'm confused as to why this needs to be on translate.wordpress.org. Can someone walk me through things?

From what I can tell (and please correct me if I'm wrong), currently the process is this:

  • The mobile apps are prepared for release.
  • Automattic pays someone to translate the top [n] languages. (What is [n] here? Which languages are not translated by community?)
  • The project is enabled on translate.wordpress.org for all translators.
  • Jenia goes in manually and uploads the paid-for translations to the relevant locales.
  • Mobile team posts a call for translations (like this).
  • Community translators translate all the other locales.
  • The mobile team bulk-exports translations and releases the apps.

A few thoughts on the above:

  • I didn't realize this process existed. Why is Automattic paying for translations versus relying on the community to translate them? Perhaps that's a bigger question, not for this ticket. :)
  • I don't feel all that great about a non-translation editor importing strings into a community project. Seems like a slippery slope and we're telling theme and plugin authors the opposite for their (upcoming) projects.
  • Bulk export already exists for the mobile team, so I'm unclear why we need to add it here.

In reality, it looks like this ticket exists to make it easier to import the top [n] translations, which, as I expressed above, I don't really like in the first place. (Again, export already exists for the mobile team.)

If the mobile apps want to use paid-for translations instead of community translations (and again, why?), I think we should just remove the locale from the relevant projects. For example, if German is one of the top [n] languages and Automattic is paying for translations for the iOS app, then we should remove the iOS app as an option for German translation on translate.wordpress.org. That's essentially what we do now anyway, we just don't tell anyone. (By uploading the translations and making the project 100%, we've essentially "disabled" the project for anyone who wants to translate that project into that language.)

One thing is clear: the status quo isn't great.

#6 @markoheijnen
2 years ago

Can we please move this to GlotPress? as this will be implemented in core.

#7 @ocean90
2 years ago

  • Resolution set to maybelater
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.