https://bugzilla.wikimedia.org/show_bug.cgi?id=69445
--- Comment #6 from MZMcBride <b...@mzmcbride.com> --- I'm not sure this problem is being approached in the best way. I think it would be helpful to look at use-cases and work backward from there. Why are administrators adding custom site-wide JavaScript? Looking through [[MediaWiki:Common.js]], for example, it seems as though a lot of code is deprecated and could be removed once de-referenced. The non-deprecated code should probably exist in MediaWiki core or in a MediaWiki extension, if it's generally useful functionality. Code is the enemy; less code is better. Rather than looking at ways to impose code review on wiki communities, we should first look for ways to centralize code (global gadgets) and we should look for ways to make the current site-wide JavaScript hacks no longer necessary. (In reply to Zell Faze from comment #4) > I think the community would likely reject attempts to use git or gerrit. > Whatever this system is, it will need to be implemented within Mediawiki. > People have a hard enough time leaving their home wiki, I seriously doubt > that most sysops are going to download and learn to use git. A smart front-end could mask that the user is using Git. I'm thinking about an interface similar to in-browser editing in the GitHub front-end. But again, I'd like us to more closely look at the underlying use-cases first. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
