@glyph It very depends. You need a lot of things in place to make this work. First and foremost, a faculty willing to give it a go. If the machines can't easily do what students and teachers need, that's the ballgame. Forget your principles for a second. If the damned things can't print or run the necessary apps, you're donezo with the experiment (and probably looking for a new job).

But if there is an appetite, then you want to lean into it as much as possible. I never got to go as far as Charlie Reisinger did, but that was always the goal.

But yeah everything must proceed first from curriculum. What the students need should drive tech decisions, not whatever flights of fancy the IT department might have. And that gets complicated, because you'll have some folks claim that proprietary applications are necessary for "preparation." And of course there are some testing regimes that require specific OSes to function. Chromebooks have obviated that somewhat, but it's still true to some degree.

But if all that comes together, I would first explore identity management, followed by provisioning by Ansible or Puppet, followed by Wireguard-enabled networking for always-available resources and support.

https://www.youtube.com/watch?v=f8Co37GO2Fc