One design issue is the current status has a limitation or two. For example, you can't have overlapping status events. Another is there's no notion of "accepted", "maybe", "declined" which is probably important v2 calendar functionality. It might be best to build a more generic "calendar" back-end for this and migrate status over / otherwise sort out how that works with calendar events.

Yeah, I'm going to create more tasks to better get our Calendar into a more standard backend that need completed before this.

Adding Google Calendar support would make the Calendar immediately useful to a lot of people. Right now the Calendar is just isolated and thus largely unusuable. Eventually it would be great to add task deadlines and milestones to the Calendars (if/when these features are added).

Well, I think that the most useful feature in the immediate term would be to allow phabricator to export a calendar url to import into your google calendar. Then google-calendar would just periodically update your information. I know that liquidplanner current supports an export ics url, which you import into google-calendar.

Are you also planning a way to manage Phabricator's calendar using standard email programs? I.e. will it be possible to embed the Phabricator calendar into Akonadi (and thus KMail) or Thunderbird/Lightning? I assume this would require that Phabricator exposes a CalDAV API.

@epriestley, You can't send this to v2 because it blocks T7924 through T7929. Huh, a task dependency tree tool might be cool.

So CalDAV support (for iCloud and others) is not planned? Google Calendar API is propritary while CalDAV is a standard. There is a really good php implementation of client/server and card parsers: https://github.com/fruux/sabre-dav
@devurandom yes that is true, and it is really simple using save/dav.

See T7924 for current Calendar roadmap items.

I'm super excited about this feature.

I'm so excited about this ticket :)

Is there someone working on this feature?

See Planning.