Making WordPress.org

Opened 6 years ago

Last modified 5 years ago

#760 closed task

Extract and import plugins code and readme strings to GlotPress on SVN repo actions — at Version 3

Reported by: stephdau Owned by: stephdau
Milestone: Priority: normal
Component: Plugin Directory Keywords: has-patch

Description (last modified by stephdau)

The attached patches introduce new methods to achieve the task in the existing SVN tracker code.


  • Dotorg_Plugins_Tracker::process_i18n( $slug, $branch = 'dev', $type = 'all' )
  • Dotorg_Plugins_Tracker::process_code_i18n( $path_rel, $branch = 'dev' )
  • Dotorg_Plugins_Tracker::process_readme_i18n( $path_rel, $branch = 'dev' )


  • Dotorg_Plugins_Tracker::handle_translator_comment( $array, $key, $val )
  • Dotorg_Plugins_Tracker::import_to_glotpress_project( $project, $branch, $file )

The methods can be called from within the class, externally, or be run from the CLI as:

cd ./plugins/

# processes both code and readme in dev/trunk
php bb-load.php i18n blogware-importer

# processes code only, in stable branch
php bb-load.php i18n blogware-importer stable code

# processes readme only, in dev
php bb-load.php i18n blogware-importer dev readme



  • Need list of plugins we want to start with, since we decided to start with a finite number. Note: this might be better off being decided in private, asked Nacin
  • Need to define when/where to trigger the code/readme i18n reruns exactly (have options, need to pick with sys/perf in mind)
  • Logic to create GP projects on the fly for new and existing plugins, thing we can leave for the next cycle since only dealing with a set list of plugins at first.

Change History (4)

6 years ago

#1 @stephdau
6 years ago

  • Description modified (diff)
  • Owner set to stephdau
  • Status changed from new to accepted

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

6 years ago

#3 @stephdau
6 years ago

  • Description modified (diff)
Note: See TracTickets for help on using tickets.