9 Commits
Author SHA1 Message Date
davidandClaude Opus 5.5 fa71e64ebb build-aux: Add an Arch package build
Builds federated-calendar from main for the "federated" pacman
repository in Gitea's package registry. The version comes from
meson.build plus the commit count and hash, so every commit
upgrades the package.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-29 09:38:17 -06:00
davidandClaude Opus 5.5 a818b79c0b Point metadata and README at Federated Computer
Federated Computer is the developer, CoreDesktop's site the homepage,
and the federated-calendar repository's issues the bug tracker and
support. Drop the GNOME links and project group, which don't apply
here; the About dialog now takes its support link from the metainfo.

The README says Federated Calendar is based on GNOME Calendar, links
to it, and explains how to build and run it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-29 09:12:38 -06:00
davidandClaude Opus 5.5 aa63bc3b3b data/icons: Draw a Federated Calendar icon
A calendar in CoreDesktop's colors, with its sparkle marking today:
navy header with a cyan edge, and a magenta sparkle among the days.
The development icon adds GNOME's construction tape, and the symbolic
icons show the sparkle in the calendar outline.

Drop GNOME Calendar's icon source, which nothing builds from.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-29 09:12:38 -06:00
davidandClaude Opus 5.5 333f7d9ec8 Revert "federated: Log why invitations aren't offered"
The invite field shows where it should; the logging was only needed to
track down why it didn't, which was the application ID clash with
GNOME Calendar.

This reverts commit dd1c1cd0.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-29 09:09:51 -06:00
davidandClaude Opus 5.5 93d2369724 Rename to Federated Calendar
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>
2026-10-29 09:01:27 -06:00
davidandClaude Opus 5.5 dd1c1cd014 federated: Log why invitations aren't offered
With -vvv, say which check stopped people from being invited to an
event: a read-only calendar, a calendar that isn't on a Core's
Nextcloud, or an event organized by someone else.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-29 08:59:22 -06:00
davidandClaude Opus 5.5 aac336c817 event-editor/attendees-section: Import Adw in Blueprint
The invite row is an Adw.EntryRow, so the template needs Adw imported
to compile.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-29 08:44:45 -06:00
davidandClaude Opus 5.5 8be61e439a build: Support libical 4
libical 4 changed several APIs used by GNOME Calendar:

 - libical-glib now provides autoptr cleanup for ICalTime, so only
   define it ourselves for older versions.
 - i_cal_recurrence_get/set_by_day() were removed in favor of the
   dynamically sized by-rule arrays; add local helpers on top of
   i_cal_recurrence_get/set_by().
 - i_cal_errno_return() was renamed to i_cal_error_icalerrno().

Also make the create-tzid event test independent of line folding,
which differs between libical versions.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-29 08:44:07 -06:00
david 8d9eb034c7 Invite people to events on Federated Core calendars 2026-10-29 08:18:52 -06:00