feat: Add proton calendar

[anikdhabal]

What does this PR do?

• Fixes #14884
• Fixes CAL-3640

Mandatory Tasks (DO NOT REMOVE)

• [x] I have self-reviewed the code (A decent size PR without self-review might be rejected)
• [x] N/A I have added a Docs issue here if this PR makes changes that would require a documentation change
• [x] N/A I have added or modified automated tests that prove my fix is effective or that my feature works (PRs might be rejected if logical changes are not properly tested)

How should this be tested?

• Are there environment variables that should be set?
• What are the minimal test data to have?
• What is expected (happy path) to have (input and output)?
• Any other important info that could help to test that PR

Checklist

• I haven't read the contributing guide
• My code doesn't follow the style guidelines of this project
• I haven't commented my code, particularly in hard-to-understand areas
• I haven't checked if my changes generate no new warnings

[vercel[bot]]

@anikdhabal is attempting to deploy a commit to the cal Team on Vercel.

A member of the Team first needs to authorize it.

[anikdhabal]

As of now, Proton Calendar does not have any public API, so in v1, let's make it dependent on Google Calendar. In v2, if we obtain the public API, then we can integrate it properly with OAuth.

[graphite-app[bot]]

Graphite Automations

"Add community label" took an action on this PR • (06/19/24)

1 label was added to this PR based on Keith Williams's automation.

"Add consumer team as reviewer" took an action on this PR • (06/19/24)

1 reviewer was added to this PR based on Keith Williams's automation.

[Ryukemeister]

As of now, Proton Calendar does not have any public API, so in v1, let's make it dependent on Google Calendar. In v2, if we obtain the public API, then we can integrate it properly with OAuth.

@emrysal @ThyMinimalDev what do you folks think about this approach for v1?

[github-actions[bot]]

This PR is being marked as stale due to inactivity.

[ThyMinimalDev]

not sure to understand the goal of this if Proton Calendar does not have any public API ?

[anikdhabal]

not sure to understand the goal of this if Proton Calendar does not have any public API ?

Hey most third-party calendars offer a “subscribe to calendar” feature that allows to enter the shared calendar’s URL. Subscribing to a calendar in this way syncs the calendar to shared Proton Mail calendar.

In Google Calendar (web app), for example, go to Settings → Add calendar → From URL. Paste the shared calendar’s URL into the From URL field and click Add calendar.

And as you can see this calendar also dependent to google calendar. We have calendar apps like: vimcal, ammie etc. that is similar to this

[emrysal]

Although this works from a Calendar POV, Proton Calendar users are all about privacy and data ownership. Having this calendar work through Google makes little sense in my opinion because Proton users will never agree to this.

IMO this is not the way to implement - let's wait until Proton has a native way of calendar integration such as CalDav or at least some way native to us so we don't have to rely on Google for these users.

[anikdhabal]

Although this works from a Calendar POV, Proton Calendar users are all about privacy and data ownership. Having this calendar work through Google makes little sense in my opinion because Proton users will never agree to this.

IMO this is not the way to implement - let's wait until Proton has a native way of calendar integration such as CalDav or at least some way native to us so we don't have to rely on Google for these users.

Yeah, this makes sense. Make this PR a draft until we have some implementation details

[github-actions[bot]]

This PR is being marked as stale due to inactivity.

[Amit91848]

Since there is no definite timeline as to when things would progress, it's better to close this for now.