dconf conflict issues

[castrojo]

Not a bug per se here but wanted to capture it. One of the first use cases I can think of is to allow a group of designers each be able to have a personal image so they can prototype what they want, and then maybe as a group they maintain a "GNOME OS NG" or something that pulls in all those ideas downstream, etc.

However while the system layer remains clean when rebasing, things like dconf settings will remain unchanged. This can lead to issues like this: ublue-os/bluefin#191

I've already had to dconf reset my settings more than once and that got old fast. Maybe there's a way we can perhaps have a different dconf preset or something?

[castrojo]

Or maybe we explicitly document to create a new user for each one? That would be annoying but would be safer.

[cassidyjames]

If it's to do with settings per-session, I believe dconf supports this. It wouldn't help with two images with a GNOME session, but could allow you to set defaults for Budgie vs GNOME for example. I believe elementary, Ubuntu, and Pop!_OS use this to retain the ability to install/use vanilla GNOME session.

[cassidyjames]

We could also consider if there's a way to actually have Beyond (and Bluefin) represent themselves as separate sessions, though that seems like more work. Maybe the more-correct approach, though, as long as they are also detected as being GNOME-based. Maybe check how the GNOME Classic session represents itself?