Fundamentally broken sounds like a bit of a stretch. In fact, it was probably working quite well for our less-trafficked repositories. But the issues identified must be fixed and decent file exclusion rules written before it goes back on for the active ones.
-Chad On Jan 22, 2019 12:11 AM, "Thiemo Kreuz" <thiemo.kr...@wikimedia.de> wrote: > […] im adding that functionality to reviewers-by-blame. I'm afraid I don't understand. Does this mean all the issues that make the plugin send passive-aggressive, misattributed spam will still be in place, possibly hitting peoples inboxes again any time somebody decides it would be a good idea to turn this feature set on again? My impression was more that all the ideas that have been shared in this email thread describe an *entirely* different approach, following entirely different ideas, with an entirely different UI, and entirely different setup. What's the point of stuffing this into the same, fundamentally broken codebase? Sysops, please, for our sanity, do not let anybody enable this toxic plugin again. Best Thiemo _______________________________________________ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l _______________________________________________ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
