This task tracks tasks that will be resolved by Gadgets 2.0, including any required ResourceLoader issues.
See Also:
This task tracks tasks that will be resolved by Gadgets 2.0, including any required ResourceLoader issues.
See Also:
Not wanting to tread on anyone's feet here, but this is an "epic" task with a clearly-defined endpoint, not a continuous "tracking" task.
In fact it is a Gadgets-2.0 release duplicate. (And all releases are obviously epics, therefore is not necessary to tag it Epic.) I was going to clean it up, but by removing Tracking-Neverending it goes out of my radar, so it may take longer now...
What's the current situation here? Is this task stalled? I can neither see any major contributions done to this (nearly done?) project in more then a year nor any major blockers.
Had been hoping to put "Work on Gadgets 2.0" on the wishlist this year, but they are excluding "Global" work, following up on @MGChecker's note from last year - has this been abandoned?
In a conversation last year on wmtech IRC I got an answer, that WMF pulled devs out of this task to do more important stuff. This task therefore have got no devs and money attached from a Foundation and it is not going to be fixed in a near future.
Just for the sake of not loosing the information: I noted that there seems to be something like a standard pattern of how other web-tech-based projects deal with this, namely the pattern of:
These patterns can be found in
– https://www.figma.com/plugin-docs/intro/
– https://wiki.mozilla.org/WebExtensions
– https://dev.jamovi.org/index.html
It might be helpful to look into these things. Particularly the way figma approached the security problems of sharing client-side run code is interesting; they published some blogposts about it.
There might also be a good connect to recent ideas to use react/MVVM that make hook into DOM hard (not that it is a sustainable idea in the first place…)
Is this task (which has 3 or 4 open subtasks) superseded by Gadgets-2.0 nowadays (which currently has 11 open tasks), or what is its exact difference (as it says "implement" and not "deploy")?