Hi all, What do you think about implementing something like this?.
This way we would reduce the final Django distribution file count removing abandoned translations (some of them translations that weren't even touched since added). We can post an announcement now early in the 1.7 dev cycle to give people time to react and perhaps this can even serve as a motivation trigger. If deemed a good approach, we can discuss the value of n and what to do with L10N formats.py files that accompany to-be-removed translations. To avoid this occurring again we also could raise the bar and implement a workflow like: We accept only new translations by teams of at least m translators and with a translation coverage of n%. We can keep all the teams/languages on Transifex so they can have a hub where work and coordinate. But skip pulling the ones that don't reach the proposed minimum to the Django Git repo right before a release. Regards, -- Ramiro Morales @ramiromorales -- You received this message because you are subscribed to the Google Groups "Django internationalization and localization" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-i18n. For more options, visit https://groups.google.com/groups/opt_out.
