Nice idea.

1. I think WordPerss core should offer a way to update everything. The good thing is that it already does. The first step is taken.

2. It must be opt-in, default off, for old installs, even if they update to newest core, and default on for brand new sites, with ability to opt-out on the install screen or later as an option.

3. It must be opt-out-able for each individual (auto updatable) plugin and theme by site admin

4. It must be enabled only for some very well-maintaned, "class A", plugins. These must be developed by at least three, or so, leads on a public repo, follwing a set of rules for good practice and versioning.

a) The plugin must have at least 10 (or so) alpha sites to which the plugin is first pushed to as auto updates. Then wait 48 hours or so before next step, with an easy abilty to halt the process.

b) the plugin must have atl east 100 or so volunteering beta sites to which the plugin or theme is then pushed to as an auto update. Then wait 96 hours, or so, before proceeding

c) The release must not do any database schema changes automatically

5. WordPress core must have a full revert/rollback ability for plugin and theme auto updates, like it has today for core secutiy updates. It must revert if anything detactable breaks. If anything breaks in alpha or beta pools of sites, the update is set to halt.

If, and only if, all these criteria is met, a theme or plugin is allowed to perform a global auto update.

We will have a "class A" set of plugins and themes. When isntalled they will say so, and offer to disable if the admin wants. The rest must either strive to get class A status or not be able to auto update.

For core should also be a hook and documentation on how backup plugins can be triggered to make a full or patrtial backup and signal back to the update system that it's now safe to perform the update. This could also work for manual updates, automatically running a backup, then update.

Jetpack was once auto updated to bring a security release, riding on cores' current mechanism. I suggest making this possible for other plugins, and for themes, in a very controlled way.

I already have fuly automated updates of core (major), plgins and themes on 40 of the about 50 sites I manage. I mostly miss the ability exclude a plugin or two.

No one, I have seen, has suggested to force WordPress users to auto update if they don't want to. Yet, someone is mentioning totalotarian ideologies and dictators by name. Those sayig such thing are the ones who know exactly how to circumvent anything in WordPress. Are they speaking on behalf of anyone else? Not the common user, that is for sure. I would say the commun user need a way to stay updated without having the knowledge on how to do it safely and easily (install and auto update plugin, as per today). Many common userss are afraid to press the update button because they thing it might break something. And it may, sometimes. So what we need is to get the most important things updated safely, and then it might just as well go automatically. If they haven't said no thanks, that is.

When I buy I car I would welcome automated service and tyre changes, if available from well reputated garages, approved by the car manufacturer, picking up my car at midnight (or whenever agreed upon) and returning my the morning. If it was free, I wouldn't mind if was an opt-out thing when buying a brand new car, but would like it to be opt-in when buying a used car. Analogy not perfect, though.

I never update Chrome. Chrome updates itself. I don't know where to turn it off, and i don't bother finding out. I am sure there is a way. I sure hat if I wanted to look for it I would find it. I'ms sure there are thousands who have disabled it. Add-ons may break after an update, but I only depend on "class A" addons. I guess they are well tested on thousands before I receive an update.

This is the future of WordPress, a web OS, offering to keep your site safe and secure for the majority. The majority are do-it-yourself-amateurs, only seeking help when they see the immediate need. The advanced users and developers will, as always, go their own way, taking more manual control, and even making a living on maintaining others web sites, like I do.

Thank you for speaking the best for the majority, Jeff. It can be done, with enough caution. We may start walking the path today, but it's a long way to go. And it won't be for everyone, just the majority.