After talking with a friend about this, I’m still kinda ready to strike over my heart and assume that snap developers would have the best intentions for us, but I have a few questions and suggestions:
-
Who’re snaps aimed at? Users, developers, or system administrators? Do snaps have a home on homelabs and user laptops/desktops, or is the target audience inclusive of large-scale production servers?
-
Please give or release a “total control” version of snapd, where a sysadmin can define, program, hook and set up hooks and callbacks on certain events, to include the refresh features into their workflow, but allow their tooling and implementation to make the final say. (For example: allow rolling updates between a cluster of machines for a particular snap, but coordinate reverts when one of the machines fail, or ignore and uncordon that machine, depending on the severity. Allow sysadmins to roll out updates under controlled automated circumstances, where production load gets shifted to a temporarily-provisioned cluster on standby to hold the load during the update, or do the same if an update breaks.
-
(Probably a bit out of scope) Please provide clear feedback to the community regarding features and visions, but also please respect a community’s wishes if they demand or require a certain package-manager-standard configurational feature for their workflow, allowing them to take advantage of snapd with no catch.