Erik Moeller wrote:
In this case, we will keep the feature enabled by
default (it's easy
to turn off, both for readers and editors), but we'll continue to
improve it based on community feedback (as has already happened in the
last few weeks).
Thanks for the reply. :-)
If your feature development model seemingly requires forcing features on
users, it's probably safe to say that it's broken. If you're building cool
new features, they will ideally be uncontroversial and users will actively
want to enable them and eventually have them enabled by default. Many new
features (e.g., the improved search backend) are deployed fairly regularly
without fanfare or objection. But I see a common thread among unsuccessful
deployments of features such as ArticleFeedbackv5, VisualEditor, and
MediaViewer. Some of it is the people involved, of course, but the larger
pattern is a fault in the process, I think. I wonder how we address this.
MZMcBride