MDN Web Docs
Add automated pull request comment that warns that a locale is "frozen" #93
-
|
Quoting Peter from the original issue:
|
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 12 replies
-
|
If we want to consider labeling as opposed to a comment, then this could be a boilerplate we can base this on: |
Beta Was this translation helpful? Give feedback.
-
|
Thinking about this more, I wonder how often we get pull requests for frozen locales. @mdn/localization-team-leads I would appreciate your input here. If we get very few, I will vote for either doing nothing or using the above labeling approach. |
Beta Was this translation helpful? Give feedback.
-
|
I have created some PRs against frozen locales to get rid of some macros, else we never can get rid of any of them (unless lucky). |
Beta Was this translation helpful? Give feedback.
-
|
Thank you, @teoli2003. In these cases, though, I think adding a label would make more sense than informing the contributor that you are opening a pull request against a frozen locale that is not actively maintained. We can then use the label to create a view to know how many of these happen. If we see a number of these being opened that grow stale over time, we might consider adding a comment instead of just a label. |
Beta Was this translation helpful? Give feedback.
-
|
FWIW, whenever new contributors create issues or PRs against such locales, I'm using a saved reply after applying a locale label (if necessary): Given the volume (and this tool (saved reply) I'm using), (and at least for me), this doesn't take too much time; |
Beta Was this translation helpful? Give feedback.
-
|
@Rumyra ^^ |
Beta Was this translation helpful? Give feedback.
-
|
The bigger question I think is what do we want to do with these frozen locales (I believe we have two German & Polish) they haven't been updated for 18 months now, so if anyone were to volunteer to work on them I think too much has changed for it to be effective. I'm happy to move them out of translated-content altogether, but am unsure of the repercussions of that from a platform perspective. Maybe @caugner or @fiji-flo has insight |
Beta Was this translation helpful? Give feedback.
-
|
If I may comment here, I would second @Rumyra here and also (partly) reply to @schalkneethling regarding the current path for those locales. Without looking at a technical level in Yari, any German or Polish speaking team would have to:
The tasks listed above are not, strictly speaking, localisation in themselves (e.g. any German page's content/wording would lightly benefit from it but not as much as a proper l10n update). I don't know the state of German nor Polish at the moment, but should a new locale team want to contribute, I would consider offering them the choice to either (re)start from scratch (and work from In terms of activity/"contribution signal", here are the list of:
|
Beta Was this translation helpful? Give feedback.
-
|
Thank you for the detailed feedback, @SphinxKnight. This helps a lot. |
Beta Was this translation helpful? Give feedback.
-
|
I agree that at this point, starting fresh from |
Beta Was this translation helpful? Give feedback.
-
|
Yeh I've been pretty much thinking the same as @SphinxKnight - if these locales do want to unfreeze in the future, they would have to do the markdown conversion and macro removal first before they are moved back - add to that all the updates that would be needed now, there's a strong case to start again (although that's also a lot of work). |
Beta Was this translation helpful? Give feedback.
-
|
(for cross-reference: #147 ) |
Beta Was this translation helpful? Give feedback.
-
|
We have retired German and Polish, so this is no longer an issue. 🎉 |
Beta Was this translation helpful? Give feedback.
We have retired German and Polish, so this is no longer an issue. 🎉