ICS files can come in two kinds:
1) ICS urls that are supposed to be kept and updated from the web, for example[1]:
  http://www.gnome.org/start/unstable/schedule.ics
  which we link as:
  webcal://www.gnome.org/start/unstable/schedule.ics
  to make subscribing easier (the browser won't try to download it locally before adding it)
2) ICS files that will be downloaded, and from which we want to only select certain items. For example, this FOSDEM schedule:
  https://fosdem.org/2015/schedule/track/embedded.ics
  For which you'd like to see a list of items, and select which of the items you want to add to your calendar

1) can probably be implemented by creating a new "Web" EDS calendar (as Evolution allows) and 2) will need a local parser for the ICS file, and a UI to go with it.

[1]: From https://wiki.gnome.org/ThreePointFifteen
[2]: From https://fosdem.org/2015/schedule/track/embedded/

All the work is happening at 'calendar-management' branch. Today I've just implemented "From file..." action, which corresponds to the 1st item of the list below.

I imagine that this bug covers:

[x] Adding .ics files (they will be treated as data sources, and users will be able to add/modify/remove stuff)
[  ] Importing .ics files into existant calendars
[  ] Export calendars as .ics files

Another possibility is to open .ics files from the command line, which will turn Calendar into a visualizer of .ics files. This should be discussed.

Targeting this bug for 3.21.3 milestone.

At this point (gnome-calendar 3.22.2), when having gnome-calendar set as the default calendar application instead of Evolution, gnome-calendar will be started when clicking on a .ics file in e.g. Geary or Nautilus. I assume this is due to the presence of "MimeType=text/calendar;" in "org.gnome.Calendar.desktop". The application will be attempted to be launched...and fail gracefully without any form of notification or visual clue.

The behaviour should be changed by either by fixing it or not opening the .ics files to begin with for the time being.
Not knowing the exact status of this bug, if it should or shouldn't (partially) work at this stage, does it fall under this bug or do you prefer me filing a separate issue?

-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gnome-calendar/issues/5.