https://bugzilla.wikimedia.org/show_bug.cgi?id=49860
--- Comment #51 from MZMcBride <[email protected]> --- (In reply to comment #45) >> but also general consensus and policy and technical reasons > > I'd like to see proof that this is a common interpretation of "other > considerations" on > https://meta.wikimedia.org/wiki/Requesting_wiki_configuration_changes - or > wherever else that interpretation comes from (sources?). I think you want [[m:Limits to configuration changes]]. > I'm asking all this because I currently do not see a *clear* ground for > rejecting this request, which seems to be supported by a large number of > members of PT community. There are fundamental principles on Wikimedia wikis that cannot be violated. For example, even if a project really wanted to add Google Analytics or Google Adwords to its site (and had a vote with overwhelming consensus to implement the change), that would not be allowed. Plenty of requests are unambiguous and easy to resolve. Some requests get murky when they threaten core principles. Using the "shellpolicy" keyword to mark bugs that fall into the latter category doesn't seem particularly inappropriate to me. But it seems like a silly thing to argue over. The real question is whether any shell user is willing to merge and deploy the proposed change. My bet is that the answer is yes, but I'm still not sure merging the change is the best course of action. Perhaps as a temporary measure with a finite expiry. -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
