document how translations are made for AspireUpdate

[asirota]

AspireUpdate is getting its own GlotPress setup: https://translate.aspirepress.org/projects/aspireupdate/ @afragen is working on it

To add to a translation without being a validator:

1 register on the GlotPress site https://translate.aspirepress.org//wp-login.php?action=register

2 Give administrator of Translate at AspirePress time to approve you as a new translator

3 Check https://translate.aspirepress.org//projects/aspireupdate/ for the list of languages

4 Let administrator know if there's a new language I need to add

5 Go forth and translate

@afragen is the project manager and lead of the Translations project-- questions go to him.

[afragen]

The language packs will live at https://github.com/aspirepress/aspireupdate-translations

[ipajen]

@asirota regarding step 3.
would it be worth to add a “plugins” in the url from start.

For example from Wp.org
https://translate.wordpress.org/projects/wp-plugins/wordpress-beta-tester/contributors/

So iAspirePress Glotpress site are prepared in the url structure for others plugins and themes.

https://translate.aspirepress.org/projects/plugins/aspireupdate/ or similar.

[asirota]

I'm not sure I understand your question. Can you restate?

[ipajen]

Sure

@asirota, regarding step 3, would it be worth adding “plugins” to the URL structure from the start?

For example, on WordPress.org:
https://translate.wordpress.org/projects/wp-plugins/wordpress-beta-tester/contributors/

This way, AspirePress’s GlotPress site would have a similar structure, ready to accommodate other plugins and themes. For instance:
https://translate.aspirepress.org/projects/plugins/aspireupdate/

[asirota]

I see @afragen is this possible? See what @ipajen suggests above. I would think yes.

[afragen]

I'm sure it's possible but would be a redirect. The standard URL for GlotPress seems to be as a project/<plugin|theme>

[afragen]

Nothing in GlotPress designates a project as a plugin or a theme.

[asirota]

Needs to be documented for AU testers

• Get the latest release of Git Updater from Github afragen/git-updater or https://git-updater.com
• Loads of information on the Knowledge Base at the website
• No license needed for public repos on GitHub
• In Git Updater, check to enable Branch Switching in the Settings
• From the plugins.php you will see info in the plugins row about branch switching
• Switching to a brach effectively re-installs the plugin from that specified branc
  .

[afragen]

The above is how to setup Git Updater for testing different branches of the AspireUpdate plugin. Switching to the translations branch

[verlev]

I can try to 'rehearse' the flow and write it out (will not be today though).
I'll ping in #polyglots whenever I have practical questions about scenario's!