|
1 | | -Use case: A person wants to contribute to the Backdrop translation of a specific |
2 | | -language. |
3 | | - |
4 | | -## (1) Prospective contributor registers for user account |
5 | | - |
6 | | -- The prospective contributor goes to https://localize.backdropcms.org/user/register. |
7 | | -- They fill the form with User name, Mail address and a Message. The latter is |
8 | | - to let the moderators know about the kind of contribution and the language |
9 | | - they're interested in. (Example: "I'd like to submit translation suggestions |
10 | | - for Spanish.") |
11 | | - |
12 | | -## (2) Site manager activates the account |
13 | | - |
14 | | -- The new account triggers the action "Send e-mail about new account to a site |
15 | | - manager". Recipients of the action (currently [Olaf](https://github.com/olafgrabienski) |
16 | | - and [Greg](https://github.com/klonos)) receive an email containing user |
17 | | - information (and, in theory, the message, see https://github.com/backdrop-ops/localize.backdropcms.org/issues/35). |
18 | | -- The site manager goes to localize.backdropcms.org/user?destination=admin/people, |
19 | | - looks for the new account, and (until https://github.com/backdrop-ops/localize.backdropcms.org/issues/35 |
20 | | - is fixed) looks for the message of the prospective contributor. |
21 | | -- If the registration and the message look good, the site manager activates the |
22 | | - account. |
23 | | - |
24 | | -## (3) Site manager checks for language and translation group |
25 | | - |
26 | | -Depending on the contributor message, there are two possible situations: the |
27 | | -language of interest exists on the translation server, or it doesn't exist yet. |
28 | | -If it doesn't exist, the language and the respective translation group have to |
29 | | -be created first: |
30 | | - |
31 | | -- Go to https://localize.backdropcms.org/admin/config/regional/language/add, and |
32 | | - add a new language. |
33 | | -- Go to https://localize.backdropcms.org/node/add/l10n-group, and add a |
34 | | - translation group for the language. |
35 | | - |
36 | | -Note: As node author, you are the first member of this group, and you'll reveive |
37 | | -group application messages (see below). |
38 | | - |
39 | | -## (4) Site manager gets in touch with the contributor |
40 | | - |
41 | | -Assumption: Language and translation group exist. |
42 | | - |
43 | | -Go to the newly activated user account (double check if it has been enabled, |
44 | | -and enable it if not), switch to the "Contact" tab, and send a welcome message |
45 | | -to the contributor. The text details will depend on the situation (new vs. |
46 | | -existing language, etc.). Here's an example regarding a contributor who wants to |
47 | | -contribute to a new language: |
48 | | - |
49 | | -> Subject: [LANGUAGE] translation group |
50 | | -> |
51 | | -> Hello [USER NAME], |
52 | | -> |
53 | | -> Thanks for registering an account on https://localize.backdropcms.org! |
54 | | -> |
55 | | -> You wrote, you'd like to translate Backdrop to [LANGUAGE]. I've created the |
56 | | -> [LANGUAGE] group and activated your user account. As a next step, please visit |
57 | | -> https://localize.backdropcms.org/translate/languages/[LANGUAGE-CODE], look for |
58 | | -> the group block at the bottom of the right sidebar, and apply for group |
59 | | -> membership. |
60 | | -> |
61 | | -> As we're not able to evaluate translations into [LANGUAGE], it would make |
62 | | -> sense to provide your account then with the role of a "Translation |
63 | | -> supervisor". As a user with that role, you'd be able to translate right away, |
64 | | -> and import language files without the need of another member to confirm your |
65 | | -> suggestions. Are you fine with being assigned that role? |
66 | | -> |
67 | | -> All the best, |
68 | | -> [NAME] |
69 | | -
|
70 | | -## (5) Manage new group membership |
71 | | - |
72 | | -When the new contributor applies for group membership, the group author |
73 | | -receives an email notification. |
74 | | - |
75 | | -- Go to `group/node/NID/admin/people`, set the Status of the new member to |
76 | | - "Active", and update the membership. |
77 | | -- (optional) Edit the group account again, and choose an additional role, |
78 | | - usually "translations supervisor". |
79 | | -- Go to the user account contact tab, and send a message with instructions. |
80 | | - Example: |
81 | | - |
82 | | -> Subject: [LANGUAGE] translation instructions |
83 | | -> |
84 | | -> Hello [NAME], |
85 | | -> Thanks for your group application! I've enabled your membership and updated |
86 | | -> your role for the [LANGUAGE] group. You can translate single language single |
87 | | -> strings on the page https://localize.backdropcms.org/translate/languages/[LANGUAGE]-CODE/translate, |
88 | | -> or import .po language files with translations on the page |
89 | | -> https://localize.backdropcms.org/translate/languages/[LANGUAGE]-CODE/import. |
90 | | -> |
91 | | -> By the way, if you have translation files of Drupal core, or of Drupal modules |
92 | | -> that have been included in Backdrop core (like Views or CKEditor), you can |
93 | | -> also import these. |
94 | | -> |
95 | | -> Please send me a message when you've done any import(s), or whenever you've |
96 | | -> completed a larger quantity of translations. To make sure that these strings |
97 | | -> show up in the download files, we have to 'repackage' the releases on the |
98 | | -> translation server. |
99 | | -> |
100 | | -> All the best, and happy translating, |
101 | | -> [NAME] |
102 | | -
|
103 | | -## (6) Repackage language release |
104 | | - |
105 | | -When a contributor has imported or translated many language strings, the files |
106 | | -have to be repackaged. |
107 | | - |
108 | | -- Go to https://localize.backdropcms.org/admin/l10n_server/packager |
109 | | -- Choose a project (usually Backdrop) |
110 | | -- Select a language |
111 | | -- Click "Repackage now" |
112 | | -- Flush the "Page and else" cache |
| 1 | +Moved to: https://github.com/backdrop/backdrop-issues/wiki/Localize:-Account-Activations |
0 commit comments