Review a draft proposal for translatable modules.
I was told that the Editing team is the owner of the Scribunto extension, at least in some formal way, and this extension will be affected by this project.
August 24.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | Feature | None | T66475 Make crosswiki bits and pieces truly global (tracking) | ||
| Open | None | T176787 Automatic infobox implementation | |||
| Open | None | T121470 Central Global Repository for Templates, Lua modules, and Gadgets | |||
| Stalled | None | T52329 We need a common repository for Scribunto modules and templates | |||
| Open | None | T238341 Structured localization framework for Templates, Lua modules, and Gadgets | |||
| Open | None | T238417 Structured localization framework for Scribunto modules | |||
| Resolved | Amire80 | T258792 Write a proposed detailed specification for discussion for translatable modules | |||
| Resolved | • ppelberg | T260459 [REQUEST] Review Translatable modules proposal |
Thank you for creating this, @Amire80.
RE the timing of this request, can we extend the deadline four days to 28-August? I will be OoO from 17-August through the first half of 24-August and would value having time when I return to review this.
(We've discussed this briefly in the engineering meeting last week, this is the summary as I remember it:)
I think we've gotten ourselves marked as the owner of everything parser-related, including Scribunto, so that we could review any proposed changes to the syntax with regards to their compatibility with VisualEditor. And from that angle, it obviously looks okay, as modules are rarely used directly in articles anyway and can't be edited visually themselves.
If you're planning to also create global templates and not just modules (the scope of the proposal is somewhat unclear), then you'll have to think about how to surface that in VE's template search and template information.
I don't think we have any other insights; you might want to talk to the Parsing team or the Core Platform team for technical feedback instead.
Thanks!
If you're planning to also create global templates and not just modules (the scope of the proposal is somewhat unclear), then you'll have to think about how to surface that in VE's template search and template information.
The scope here is definitely not global templates and not even global modules. The scope here is only conveniently translatable modules (not templates), and only within one wiki.
Some day—yes, there should definitely be global modules and templates, but not within this task. This task is hopefully a step in that direction.
@Amire80, to affirm what @matmarex shared T260459#6407160, from VE's perspective, the Editing Team sees no issues with the changes proposed in translatable modules doc, considering we read them as being limited to content/components that are almost never exposed within content pages.
Please let us know if any other questions arise as you continue down this path.