Talk:ResourceLoader/V2 Task management
- [History↑]
Contents
| Thread title | Replies | Last modified |
|---|---|---|
| ApiQueryGadgets | 1 | 10:29, 16 July 2011 |
| Revision vs. Logging | 0 | 15:01, 10 July 2011 |
| NS_GADGET editing | 0 | 14:56, 10 July 2011 |
Did someone look at the current API?
The proposal so far plans to have a mw_gadget table in which the current state of things is stored. There is no history and it's not on a wiki page, but in the database. This gives many advantages (hence we choose it). However, all actions are logged.
The down side to this:
- Either we get very long log messages or some info will simply not be retrievable from the past
- Hard to revert/undo
- Impossible to add to watchlist or show a diff
On the other hand, it's not a whole lot different from any of these:
- Block
- Delete
- Protect
- Patrol
- Rollback
- Move
All of these only leave a log-entry with details but not descriptive revision that is revertable or diff-able (they do leave null-revisions in some cases). Although these may not justify a lack, it may be worth considering to just keep the plan the way it was (eg. not creating mw_gadget_revision + all the complications [1].
What do you think: Current-state table with logging ? Or revisioned ? Something else ?
- ↑ complications, or perhaps feature-ideas: history view, diff view, possibly revdel and watchlist
It'd be protected/restricted to users with the "editgadget" right (a bit like NS_MEDIAWIKI and editinterface). I'm not quite sure to which group (if any) it should be assigned by default.
Traditionally and due to backwards-compatibility it could be assigned to the sysop-group (that is, in the current system sysops can edit gadgets since they have editinterface and gadget resources are stored in MediaWiki:Gadget-<name>.js).
On the other hand, perhaps we could start a new group, like "js developers" or "gadget artists", something like that (probably needed in the long run anyway).
Question being: Is the average sysop supposed to able to modify gadget resources ? Note that the editgadget user right is not the same as the "gadgetman-modify" user right. The latter is for the management of the gadgets through Special:GadgetManager (such as toggling "load by default") which is more of a sysop-thing. editgadget would (just) be for editing the gadget resource wiki-pages in the Gadget-namespace.
