Integrate CalDAV Protocol for appointment syncing #209
Comments
|
Hello Hendrik, thanks for posting! The CalDAV protocol seems to be very interesting. I will definitely check this out for a future release. I'm currently preparing v1.2 for Beta release so it's a bit too late for this release but it may be integrated for v1.3. In any case I am accepting donation through PayPal: paypal.me/alextselegidis |
alextselegidis
changed the title
|
Seconded |
|
Ohh, this feature would be great for me! At this moment i have to pay monthly for the CalDAV Feature to sync with my Smartphone and Thunderbird / Lightning. I want to be independent from Google Cal. I would donate for this feature! Is something planned about this? Actually i'm using this expensive service: https://de.doctena.de/ :-/ Hope to hear from you Best Mark |
|
Unfortunately this feature will not make it for v1.3, I'm actually almost done with the coding of the new release and will proceed to a beta release in the following days. Stay tuned for further updates :)
|
|
@alextselegidis any news on the CalDAV support? If not, I would like to start programming on this, in order to support at least a subset of the caldav standard. But in case anyone already started, I want to avoid the issue. What is the best way to extend on this code? We need some sort of REST API specification so We can start with a read-only CalDAV so people can at least see the calendars from easyappointments. |
|
@alextselegidis and @barrydegraaff I am also very excited about this feature and in my opinion this is a must have as we are working around Google & Co. with our own infrastructure such as nextcloud for calendars for example. Actually we are using a proprietary booking app that doesn't support CalDAV as well so we have to sync manually... |
|
Since this issue has been here for 2 years, probably no one at easyappointments want do implement it. We at https://zetalliance.org/ will be doing a crowdfunder in January to add easyappointments or something like that to Zimbra. But it is too early to tell if that is going to add WebDAV to this project. |
|
Hello @barrydegraaff, @mokkin thank you for your interest, I find this a great feature too and also think that will make the integration with other systems so much easier. Unfortunately other tasks are being prioritized for the v1.4 so that the overall performance and user experience is enhanced. I cannot promise an integration soon. Any help is always appreciated though, stay tuned for updates :)
|
|
I'd like to see this as well. I administer both Nextcloud and Zimbra. I would love to see this feature. Thanks for your work! |
|
CalDAV would make this unstoppable! |
|
We need this too. Currently using Harmonizely. |
|
I will donate up to $50 to the project when this is implemented. The sooner it's done the more money I'll donate. Right now I have to manually add events to both my main calendar (synced between all my devices with Nextcloud) and E!A, which is not an acceptable long-term solution. I'll even accept a script that runs via cron to sync the calendars with each other. If I end up taking a couple hours and writing some code for this, I'm keeping the $50. IMO this should be top priority (right under security bugs). This whole project is essentially a public UI for adding events to a calendar, so it's not helpful unless it can actually add events to a calendar! |
|
I made the beginning here and created a bounty at bountysourc.com |
|
Is the requested feature to connect/sync an easyappointment calendar over CalDAV |
|
@mocig I think the ideal feature would be new appointments appearing on a CalDAV calendar, and for events on the CalDAV calendar to appear in E!A as unavailable times. |
|
I just added 50$ to the bounty. If you need an example for a CalDAV client, I added on Github a software I wrote and I used to use : https://github.com/mpellegrin/weather-table ; it retrieves the events from CalDAV and parse it with ICS Parser. I can also provide you a full access to a demo Nextcloud instance with the CalDAV server enabled to test/develop the software, as well as help to debug if you need. |
|
@alextselegidis FYI the bounty for this issue is now $200. https://www.bountysource.com/issues/38115699-integrate-caldav-protocol-for-appointment-syncing |
of course https://harmonizely.comis not self hosted but it support CalDavsince a while ago. |
|
I already tried this, but it has no group capabilities which means you have to register separate accounts per user and resource, no matter if it's the free or paid version. |
|
..... 5 mounths later :-) First of all, thanks for easy appointments. written in a mood created by a mixture of google_api_pain, frustration and a tiny bit of hope for change |
|
@alextselegidis How much money would it take to implement this and when could this be done? |
|
I definitely would support this with money too and I would really like it, if @alextselegidis could realize. Otherwise, if he has no free capacities for it, I could imagine to collect money, give the job to a developer and ideally finish the implementation with a pull request to the main repository. |
|
Hello everyone, Thank you very much for your support and contributions on this. At the moment the v1.4.0 is almost ready and I'm working on the final touches before the beta comes out. More work is required for this item to be properly done, as you all know that synchronization is not an easy topic. Since there's much interest on this ticket, I've raised the bounty to 1000$, if this is met I will prioritize and make the changes for the next release. Otherwise it will still remain open but will be added in a future release.
|
|
The CalDAV feature should also consider different available calendars in one CalDAV server. This could be a second provider or a resource such as a room or a device required. Here is an example how other booking tool manage it:
I already pledged 100,- to the bounty and I am sure I can collect more. Are there any others wanting this asap? |
|
To speed things up herewith I'd like to remind this important ticket for CalDAV support. Please consider to make your donation to the bounty: So @alextselegidis can quickly prioritize this feature for all of us. |
|
In for $100. Let's get this done! |
|
It will be in 1.5, which is scheduled for September/October 2021 🚀
|
alextselegidis
changed the title
|
any updates for 1.5 ? |
You can follow progress here https://github.com/alextselegidis/easyappointments/milestone/9 |
|
Hello! Almost all planned code maintenance is completed, which means that the only thing left to be done will be the implementation of the remaining 1.5 features before we reach the alpha release state. Just like @jdaviescoates, you can spectate the progress under the milestones page. Cheers!
|
|
Very nice, I'm coming from Harmonizely but also deGoogle so having CalDav integration to work with e.g NextCloud but also Outlook is very exciting. I'm monitoring Releases, eager to be able to try! |
|
This is the only missing thing right now for me. What would be a fair amount to donate to get this completed? |
They are now cal.com, and also still open-source: https://github.com/calcom/cal.com |
|
Hello! Just a quick reminder here on this ticket: CalDAV support is coming with 1.5, which will be released this September 2022. Stay tuned! Alex |
|
Very exciting @alextselegidis . I recently cancelled my plan on Harmonizely due to their acquisition (I feel it's now part of a big "machine" rather than a carefully crafted product with a developer I could chat with directly, not the self-hosting mindset I want to support) but that is precisely the 1 feature that was preventing me from switching to easyappointments. Eager to try as soon as it's out! |
|
@Utopiah Glad to welcome you onboard, this is the last feature I'm working on for 1.5 so it will be soon be there for you to work with ;)
|
|
This is especially exciting for me in terms of consulting. It means I could rely one could rely on payment e.g #672 or more recently #1310 to provide short consultancy sessions or workshops and rely on their own self-hosted open-source infrastructure, e.g a Jitsi Meet, even enabling/disabling feature based on the type of sessions booked. All that is impossible without a reliable way to insure that time slots are available. This would otherwise be feasible but rather impractical because of the small amounts and the time to find a moment would be costlier than the event itself. This opens a lot of new possibilities. Can't wait to try that. |
|
Hey! Also taking a look here. Caldav support could be a game changer :) Eager to see that release! |
|
+1 |
|
Here's some fairly recent PHP code I found for connecting to a CalDAV server as a client: https://github.com/agendav/agendav/tree/main/web/src/CalDAV It has the same license as E!A so copying it won't create any legal issues. |
|
Hello @skylarmt, thanks for sharing!
|
|
+1 would be good if this worked with self hosted Baikal server please, happy to test once it's available for testing |
alextselegidis
changed the title
|
Hey folks, I've just found out about this project today, as I wish to integrate a booking interface with Zimbra 10 OS, which works with Caldav. Jack |
|
Hello! CalDAV will be there in a couple of days. Please star and follow the project and stay up to date with the latest changes.
|
|
Almost there!
|
|
Any update on this feature? Thanks!! |
|
Still in progress
|
|
Feature completed on develop!
|
|
Yay! |
and others
Hi,
I would like to become independent from Google or any other cloud service. I host my own CalDAV server so it ould be consequent to subscribe to Easy!Appointments as additional CalDAV ressource.
Use case
Similar to the existing Google sync a configurable sync with a CalDAV calendar.
I would suggest parameters like:
The CalDav ressource can be an iCloud account, a [own,next]cloud calendar or a Google calendar.
Or
If syncing is to complex to implement, maybe it is easier to integrate sabre/dav to offer the calendars with the bookings via CalDav. It would be one more calendar ressource to subscribe to, but this shouldn't be a problem.
Sponsoring (e.g. via Bountysource or FreedomSponsors) is an option.
With best regards,
Hendrik Eggers
The text was updated successfully, but these errors were encountered: