Ship as Federated Calendar, with the application ID
computer.federated.FederatedCalendar and the executable
federated-calendar, so it can be installed and run alongside GNOME
Calendar.
The settings schema follows the application ID too, so the two don't
share settings or install the same schema. The project name sets the
executable, gettext domain and data directory; the desktop file, D-Bus
service, search provider, metainfo and icons follow the application ID.
Internal resource paths and the template file names are unchanged, to
keep merging from GNOME Calendar simple.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This is mostly a nice touch of integration for when
using the Night Light feature. It can be disabled by
switching the 'follow-night-light' dconf key to false,
but no user interface widgetry was added.
This key will keep a list of the uid of the sources marked as disabled
in the interface in order to keep the same state between runs of the application
