https://bugzilla.wikimedia.org/show_bug.cgi?id=57891
--- Comment #37 from Yuvi Panda <[email protected]> --- (In reply to Dan Garry from comment #36) > Here's the way I'd like to see us proceed: > * Puts the farm-wide common.js and common.css aspect of this extension > behind a feature flag, and make the configuration change that sets whether > them to being disabled on the Wikimedia cluster. Feature Flag done and merged yesterday https://gerrit.wikimedia.org/r/#/c/114079/ Deploy to betalabs with only the user-specific JS and CSS enabled (and site-wide css / js disabled) will be done when https://gerrit.wikimedia.org/r/#/c/114719/ gets merged. > * Start an in-depth discussion about the common.js and common.css aspect of > this extension with the Meta community and representatives from other wikis > that would be affected by this change. Present user stories for this > feature. Form an agreement that both the WMF, the Meta community, and the > individual wikis can support. We can then consider enabling the extension. So i guess that the extension can be enabled with the site-wide CSS/JS turned off, and then there is community consultation, etc before that particular feature can be turned on. However that does not need to block the deployment of the per-user CSS/JS parts of the extension. Is that accurate? -- 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 [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
