On 25 July 2013 14:20, Tyler Romeo tylerromeo@gmail.com wrote:
On Thu, Jul 25, 2013 at 2:15 PM, Martijn Hoekstra < martijnhoekstra@gmail.com
wrote:
I find that somewhat hard to believe, but if it is true, should that
worry
us? I'm not sure that we should be comfortable with changes like these
not
giving pause to our engineers.
Well to be quite honest it was a pretty reasonable decision. I mean, if enabling an option all of a sudden broke Wikipedia, it makes sense to disable that option until it is fixed. Maybe the issue wasn't so big a deal such that it needed to be immediately disabled, but nonetheless it's a decision I trust the operations team to make.
The preference didn't break anything. It had been active for months during the alpha testing. It was a conscious decision not to permit its continued use after the deployment on July 1, and the way that it was "disabled" was by hiding it.
Those of you who know more about the system than do I pointed out that hiding the preference wasn't the appropriate step and if the VE team wanted to remove the option, it should be written out on their end. But the preference had been active for months before the July 1 deployment.
Risker