Federated calendar and contacts sharing [$360.00]

[georgehrke]

There already is a federated file sharing, that allows you to share files among different Nextcloud instances.
We need something similar for calendars and address books.

---

There is an open bounty on this issue. Add to the bounty at Bountysource

[mimi89999]

Any workaround to get that?

[georgehrke]

well, you can use public calendar sharing and webcal feeds for read-only "federated" shares, but that's only Nextcloud11+ and will only work in the web interface

[georgehrke]

@schiessle Let's tackle this at the next hackweek, deal?

[schiessle]

@georgehrke deal! 😃

[MorrisJobke]

Seem to not have happened :/

[georgehrke]

@MorrisJobke we discussed it, but it was too complex for one week.

@schiessle Do you mind posting the notes we took? :)

[MorrisJobke]

Looks like it is included in #9345 ;) cc @schiessle

[schiessle]

yes, I wrote you a mail with some details @georgehrke
As this can be implemented now without any changes to the server, we could work on this together after the Nextcloud 14 release

[MorrisJobke]

@schiessle What is the status of this? Doesn't seem to get into 14 anymore, right? move to 15?

[daraelmin]

Maybe this pull request will solve this issue: #9345

It should allow the implementation of federated calendar and contact sharing.

[georgehrke]

Not really. What will actually bring this forward is #20214

[daraelmin]

Ok but in the description of the pull request it is said "allow the implementation of federated calendar and contact sharing."

I don't want to see Bounty source take the money I've put on this issue for the nextcloud dev.
Read this thread for more info (https://help.nextcloud.com/t/dont-use-bountysource-anymore/84943/55)

If there's no solution to federate calendar, I'd really prefer that my money goes to someone whos working on the project I want to support.

[georgehrke]

#9345 moved this forward a lot, by allowing other apps to reuse the existing federation logic.

However, we still need #20214, to actually allow writing calendar / contacts without a user account, just by knowing a token.

[daraelmin]

I might be wrong, but wouldn't it be easier to add a caldav and carddav client function (module?) on the server side of nextcloud?

Especially since reading #20096, I'm wondering if, in the end, federated sharing isn't just going to be too limiting for the end user. Indeed, this type of design will not allow you to synchronize calendars hosted on other dns without administrator intervention (the externe calendar must be listed in trusted cloud and must accept federation).

Going through the federation plugin may not be the right solution, at least for my needs.

Is there a way or an existing module to connect via caldav er carddav from the server to another?

[georgehrke]

I might be wrong, but wouldn't it be easier to add a caldav and carddav client function (module?) on the server side of Nextcloud?

That is the plan. Public calendar endpoints are nothing else but CalDAV endpoints for that matter.

[daraelmin]

@rubo77 bounty increased to 250 dollars
Could you edit the issue title please ?

[rubo77]

done.

I thought, we should not use bountysource any more?

[daraelmin]

Thanks.

They gave up changing their condition in front of the reaction of the community, so....

[florom]

Hi All,

I would appreciate a login to another calendar (iCloud or Google) nativly in the calendar app to cause the issue came up within my family and I could not manage to switch to (my) nextcloud.
Since public calendars are per definition public I do not want to use them although it is very easy and the synchronisation interval can be changed easily.

I use a workaround for this issue using Outlook and the Addon CalDavSynchronizer.

I made a separate calendar Outlook for synchronisation.
With one profile I connect to iCloud using my login and password and with the other profil I connect to nextcloud using login and password.
So every time I start Outlook (which I use for emails so I start it at least once a day) iCloud and Nextcloud calendar are syncronising.

I am reasarching for a calendar program on linux (server) which can be run permanently as proxy(which is now Outlook) but I have not done much in this direction. I will give feedback if I find a solution.

Hope this helps a few people.

[sunjam]

That has nothing to do with this issue about federation of calendars and contacts

…

On Wed, Jul 14, 2021, 3:58 AM florom ***@***.***> wrote: Hi All, I would appreciate a login to another calendar (iCloud or Google) nativly in the calendar app to cause the issue came up within my family and I could not manage to switch to (my) nextcloud. Since public calendars are per definition public I do not want to use them although it is very easy and the synchronisation interval can be changed easily. I use a workaround for this issue using Outlook and the Addon CalDavSynchronizer. I made a separate calendar Outlook for synchronisation. With one profile I connect to iCloud using my login and password and with the other profil I connect to nextcloud using login and password. So every time I start Outlook (which I use for emails so I start it at least once a day) iCloud and Nextcloud calendar are syncronising. I am reasarching for a calendar program on linux (server) which can be run permanently as proxy(which is now Outlook) but I have not done much in this direction. I will give feedback if I find a solution. Hope this helps a few people. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#1440 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AANUKZVDRUY5JWI6XREC5FDTXVUWNANCNFSM4CP7V6TA> .

[florom]

Hi @sunjam ,

I agree with you that its not about federation but it is about sharing.

in
nextcloud/calendar#3318 (comment)
@ChristophWurst states that the other issue sounds like a duplicate to this one.

Since it is no good to open up new issues (or comment in different issues) on the same topic
I used this one.
If the decision will be changed I post the workaround in the other Issue.
That is fine with me.

[sunjam]

It is good to open new issues. Please do so so we can keep this related to the actual topic. just my .02

…

On Wed, Jul 14, 2021, 4:09 AM florom ***@***.***> wrote: Hi @sunjam <https://github.com/sunjam> , I agree with you that its not about federation but it is about sharing. in nextcloud/calendar#3318 (comment) <nextcloud/calendar#3318 (comment)> @ChristophWurst <https://github.com/ChristophWurst> states that the other issue sounds like a duplicate to this one. Since it is no good to open up new issues (or comment in different issues) on the same topic I used this one. If the decision will be changed I post the workaround in the other Issue. That is fine with me. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1440 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AANUKZQMJOVUVNF47C6NXEDTXVV67ANCNFSM4CP7V6TA> .

[florom]

Hi @sunjam ,

I am not considering as new:

but it is about sharing

so the issue has the correct topic.

[Booteille]

Hi.

Any plan to move on this topic anytime soon?

[labor4]

AFAIK there is subscription for CalDAV, but not für CardDAV.
Meaning read-only Calendar is possible, but not for Contacts.

First having subscriptions for Contacts to may be worth considering as an intermediate goal?

Use case: In some situations I think it preferable to separate an NC instance with calendar/contacts from a heavy lifting file-sharing NC instance. The file-NC could benefit from the contacts inventary while not strictly needing to have write permissions.