ABCDEFGHIJKLMNOPQRSTUVWXYZ
1
https://make.wordpress.org/polyglots/2019/06/26/proposal-for-handling-pte-requests/
2
https://meta.trac.wordpress.org/ticket/3423
3
CategoryProposalFeedback
4
Form to collect the dataMaybe: Ask if plugin/author or translatorsAsk if ‘contributor’ or ‘author’, then ‘List contributor(s) per locale’ is not needed in case the answer was ‘contributor’. If 'author’ on the form, only show their projects.
5
Select plugin/theme slugs (autocomplete)
6
Select Locale(s)
7
List contributor(s) per locale
8
Form can be submitted by the theme/plugin author but also contributors
9
Request can include many projects/locales/contributors
10
Data validationDoes the contributor exist? (error)
11
Are the locales correct? (error)
12
Are the plugins/themes available?Also, is the plugin/theme translation-ready?
13
Pre-requirements: Does the contributor have submitted at least 5? translations for the requested projects in the locale? (warning)5 may be too few?
5 strings was based on plugin/theme header data like plugin name, description, etc.. I can also imagine a threshold based on a percent value.
30? - shouldn't be too high to avoid the burden of the review process
14
Pre-requirements: Check number of requested locales, maybe CLPTE? (warning)
15
Is the contributor already an approved PTE? => Make they automatically a PTE for the new project?Auto assign PTE rights is worst idea, if one completes 2-3 simple plugins with just several strings, and then gets the possibility to automatically get PTE for anything, that would be nightmare. New requests handling will be simplified, but an element of control by GTEs should be kept, so, no auto PTE, thats worse than just bad.
As for requests left unreplied, a remind notification after 2 weeks and then 2 more weeks until request autofulfillment sounds reasonable. But keep in mind that some locales can be added by editing initial post and no notifications are sent in this case, so request will remain unseen, autocompleting them will be not pleasant surprize.
16
If the plugin is translation ready (if not, direct the plugin author to plugin i18n handbook)
17
If the PTE candidate is a native speaker
18
19
Data storeCustom post type (benefit: Removes the requests from the index page of the polyglots p2)As we have a CPT, it might be handy to expose also something in an API (like https://api.endpoints.stream/polyglots/openrequests that I’ve setup as a test) so it can be used in different systems.

-> For the first version an API is probably a low priority item as it usually comes with more maintenance work.
20
Output of requestsTable to list all requests, similar to teams page
21
Split requests into locales
22
Filterable by locale, date, …
23
Notifications to all GTEs
24
Link to the project on translate.w.org with active user filter
25
Tell the GTE whether the user is already a PTE
26
Approve button for GTE without visiting the wp-admin for all GTEsButtons won’t only be added for existing contributors, they’re planned for anyone added to any PTE request but they will be a part of the controls in the request itself, not on translate.wordpress.org.

→ Adding buttons to approve PTEs from translate.wordpress.org is a functionality that’s separate from this MVP and needs to be added to translate.wordpress.org as a GP add-on, but it’s a good candidate for a separate task on the GlotPress track. (edited from the original comment for clarification)
27
Show some stats about the user
28
Send reminder about requests that are two weeks old, automatically approve a week after the reminder?
29
Post request on the team p2 or just summary/activity log
30
Show comments from team p2 at the global requests (depends on previous point, discussions need to be in English)
31
Show the “Resources for translation contributors” in the request (automated comment, see French, …)
32
Reject with feedback only with predefined reasons (grammar, punctuations, typos, style guide)(additional suggestions)
1. Grammar, punctuation, capitalization are not as per style guide or as in the original
2. Vocabulary is not following the locales glossary.
3. You did not join our local slack channel as requested
4. Translation is incorrect or seems automated.
5. Translation differs too much from the original meaning.
6. Translation is too direct / literal and therefore hard to understand.
7. Translated strings are too short to judge the quality of your work.
33
(Nice to have) Activity log for each new PTE (user x by user y/automatically) on date)
34
Email notifications1. GTEs & Contributor: New PTE request was posted
2. Contributor: Your PTE request was accepted / declined with feedback
3. GTEs & Contributor: No response from GTEs after 2 weeks, will wait 1 more week and assign PTE automatically (if turned on for this locale or at all)
4. Contributor: PTE status assigned automatically due to GTE inactivity
5. Contributor: PTE status assigned automatically because certain criteria were met.
35
MVP?1. Request form which allows adding multiple projects and the same PTE requests for all chosen projects.
2. Form is saved in a Custom Post Type.
3. Table of currently open requests with options to accept / reject with feedback.
4. Email notifications (number 1 & 2).
36
Request: stats of GTEs1. How many PTE requests were tackled by each GTE
2. How many strings for all projects combined were moderated (rejected / approved / fuzzied) by each GTE
3. How many strings were translated for all projects combined by each GTE
4. How many posts on local Rosetta sites each GTE published
5. Separate stats for all-time and last year, for all of the above
6. Nice to have for gamification: cross-locale GTE activity table with all of the above

This will help in filtering out inactive GTEs and maybe would allow shining some spotlight on hard working GTEs, especially by Automattic
37
Activity stats are very important too. Especially for users with “extended” rights (so called global PTE), at least we want to see log of date – project name for editor activity.
38
Conditional judgementinactive team
Does the contributor have submitted at least 5%?
automatically approve a week after the reminder?
…
active team
Does the contributor have submitted at least 20%?
automatically approve two week after the reminder?
…
super active team
Does the contributor have submitted at least 50%?
automatically approve four week after the reminder?
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100