[wp-meta] [Making WordPress.org] #5152: Put a limit on adding new translation after multiple warnings
Making WordPress.org
noreply at wordpress.org
Thu Apr 16 17:41:35 UTC 2020
#5152: Put a limit on adding new translation after multiple warnings
--------------------------------------+-----------------------
Reporter: Nao | Owner: dd32
Type: enhancement | Status: assigned
Priority: normal | Milestone:
Component: Translate Site & Plugins | Resolution:
Keywords: |
--------------------------------------+-----------------------
Comment (by ocean90):
Limiting users based on triggered warnings and adding new warnings should
be handled separately. This ticket should only be about creating solid
rules for a limit. Though, I agree that some of warnings from GlotDict
should be contributed back to GlotPress itself and not only to
translate.w.org.
Currently we only
[https://meta.trac.wordpress.org/browser/sites/trunk/wordpress.org/public_html
/wp-content/plugins/wporg-gp-custom-stats/stats/discarded-warning.php log
discarded warnings into a database table] while
[https://meta.trac.wordpress.org/browser/sites/trunk/wordpress.org/public_html
/wp-content/plugins/wporg-gp-slack-integrations/integrations/log-
warnings.php new warnings are only pushed to the #polyglots-warnings
channel] on Slack.
As a quick first step we should extend the database logging for warnings
in general so we have some structured data which can be exported. This
data can then be used to make some data driven decisions.
--
Ticket URL: <https://meta.trac.wordpress.org/ticket/5152#comment:7>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org
More information about the wp-meta
mailing list