Nieścierowicz Adam wrote:
So when looking through google, I found resources on the stand AGPL license client thought that maybe someone is willing to finish on AGPL license.
The calendar module provided by Kolab is under APGL but currently lacks a CalDAV backend. There are plans to add this but the work for that isn't scheduled yet.
Personally, I am ready to sponsor a programmer, maybe others willing to help?
I could connect you with the programmers who announced their intents to add CalDAV to the Kolab calendar module. Or maybe they're even listening on this list (therefore cc-ing the dev list).
Regards, Thomas
W dniu 13.02.2013 23:04, Bob Miller napisał(a):
The only caldav client I found compatible with roundcube is provided by the myroundcube folks, but as of about last december it will cost about 20 euros for the caldav/carddav packages. I have deployed this twice, once before it became a pay program and once since, and I have good things to say about it. -- Computerisms Bob Miller
867-334-7117 / 867-633-3760 http://computerisms.caOn Tue, 2013-02-12 at 00:52 +0100, Nieścierowicz Adam wrote:Looking for a calendar with support for CalDAV W dniu 12.02.2013 00:46, Steve Perkins napisał(a):
Try: http://git.kolab.org/roundcubemail-plugins-kolab/tree/plugins Calendar and Tasklist. Kolab or MySQL backends. Both seem pretty good. I use them (in a small way) anyway. On 12.02.2013 07:34, Nieścierowicz Adam wrote: Hello, searching a calendar for RC I found a http://code.google.com/p/myroundcube/source/browse/trunk/plugins/#plugins%2F... Reading license (AGPL) shows that the code can be modified, perhaps there is someone willing to deal with this plugin? Regards
On 14/02/2013 09:00, Thomas Bruederli wrote:
Nieścierowicz Adam wrote:
So when looking through google, I found resources on the stand AGPL license client thought that maybe someone is willing to finish on AGPL license.
The calendar module provided by Kolab is under APGL but currently lacks a CalDAV backend. There are plans to add this but the work for that isn't scheduled yet.
Personally, I am ready to sponsor a programmer, maybe others willing to help?
I could connect you with the programmers who announced their intents to add CalDAV to the Kolab calendar module. Or maybe they're even listening on this list (therefore cc-ing the dev list).
I'm interested!
A couple of years back I really liked your idea for using the imap server for storage of everything, but imap servers never developed the necessary searching capabilities to integrate and caldav/carddav is on the tip of becoming decently well supported (and some clients aren't too buggy now...) So, my vote is that DAV looks like it's going to win this...
I like what you are doing with Kolab, but my vote is that it's time to start looking at DAV. DAV is a really good fit for your requirements... (In fact, OwnCloud is potentially a really good fit as the dav server for Kolab...)
Cheers
Ed W
On 2013-02-18 17:34, Ed W wrote:
In fact, OwnCloud is potentially a really good fit as the dav server for Kolab...
Appreciate the sentiment, but I'm afraid I'm going to have to decline for a variety of reasons, including but not limited to those I've discussed with it's developers face-to-face.
Kind regards,
Jeroen van Meeuwen
On 14/02/13 10:00, Thomas Bruederli wrote:
Nieścierowicz Adam wrote:
So when looking through google, I found resources on the stand AGPL license client thought that maybe someone is willing to finish on AGPL license.
The calendar module provided by Kolab is under APGL but currently lacks a CalDAV backend. There are plans to add this but the work for that isn't scheduled yet.
Personally, I am ready to sponsor a programmer, maybe others willing to help?
I could connect you with the programmers who announced their intents to add CalDAV to the Kolab calendar module. Or maybe they're even listening on this list (therefore cc-ing the dev list).
Regards, Thomas
Hello,
we at GMS (http://www.gms.lu/ - https://github.com/GMS-SA/)are the company Thomas hinted at who are working on CalDAV and CardDAV support.
The Calendar support is implemented by extending the Kolab plugin(s). A CalDAV driver is being implemented for calendar and tasklist plugins.
The CardDAV support is being implemented as a new and independent plugin as the Kolab addressbook is completely different and does not support backend 'drivers'.
Our CalDAV implementation is using the SabreDAV (http://code.google.com/p/sabredav/) and the sabre-vobject (https://github.com/evert/sabre-vobject) Libraries.
In both cases our target CalDAV/CardDAV server is SOGo (http://www.sogo.nu/). Development is trying to stay as RFC complaint as possible. There are cases, however, where SOGo diverges from the RFC or the RFCs were published later than features were implemented in SOGo. In such cases it is planned to have config options for server support so that this does not become a SOGo plugin. Our main focus is SOGo as this is what we are using.
Work is well underway. Most functionality is implemented but there is still lots to do before a release is expected. We are not talking years but probably over 1 month.
Regards,
Chris
P.S. Thomas, if you wish to re-post this to the 'users' list, to which I am not subscribed, please feel free.
On 2013-02-22 12:14, Chris Moules wrote:
On 14/02/13 10:00, Thomas Bruederli wrote:
Nieścierowicz Adam wrote:
So when looking through google, I found resources on the stand AGPL license client thought that maybe someone is willing to finish on AGPL license.
The calendar module provided by Kolab is under APGL but currently lacks a CalDAV backend. There are plans to add this but the work for that isn't scheduled yet.
Personally, I am ready to sponsor a programmer, maybe others willing to help?
I could connect you with the programmers who announced their intents to add CalDAV to the Kolab calendar module. Or maybe they're even listening on this list (therefore cc-ing the dev list).
Regards, Thomas
Hello,
we at GMS (http://www.gms.lu/ - https://github.com/GMS-SA/)are the company Thomas hinted at who are working on CalDAV and CardDAV support.
The Calendar support is implemented by extending the Kolab plugin(s). A CalDAV driver is being implemented for calendar and tasklist plugins.
The CardDAV support is being implemented as a new and independent plugin as the Kolab addressbook is completely different and does not support backend 'drivers'.
Our CalDAV implementation is using the SabreDAV (http://code.google.com/p/sabredav/) and the sabre-vobject (https://github.com/evert/sabre-vobject) Libraries.
In both cases our target CalDAV/CardDAV server is SOGo (http://www.sogo.nu/). Development is trying to stay as RFC complaint as possible. There are cases, however, where SOGo diverges from the RFC or the RFCs were published later than features were implemented in SOGo. In such cases it is planned to have config options for server support so that this does not become a SOGo plugin. Our main focus is SOGo as this is what we are using.
Work is well underway. Most functionality is implemented but there is still lots to do before a release is expected. We are not talking years but probably over 1 month.
Regards,
Chris
This is great news!
I have been using the caldav calendar plugin from myroundcube, with a radicale caldav backend. However, a while back they moved the caldav support into a non-free "calender_plus" plugin and I've been wondering what I would do in the future.
Also looking forward to not having to use their plugin manager.
I can understand why they've done this, but it's not for me.
Roy
Hi
The CardDAV support is being implemented as a new and independent plugin as the Kolab addressbook is completely different and does not support backend 'drivers'.
Our CalDAV implementation is using the SabreDAV (http://code.google.com/p/sabredav/) and the sabre-vobject (https://github.com/evert/sabre-vobject) Libraries.
In both cases our target CalDAV/CardDAV server is SOGo
This sounds very cool. Kolab seems like the best implemented PHP calendar/contacts/Notes frontend right now.
However, SOGo already has an excellent web interface which does almost everything Kolab does - I'm slightly curious as to why you don't use it?!
My interest is that I find roundcube slightly more responsive and also simpler to deploy. It's also easier to modify and extend. However, whilst I'm a bit scared by a lot of the code, OwnCloud is looking like my best partner and it's basically a wrapper around sabredav. (I like the DAV filesharing piece for our solution)
As such my initial thought for integration with roundcube was to talk directly to the backend databases. Kolab expects all the fields to be in separate columns, but owncloud simple stores the original vcard/ical field as a blob and it requires parsing. Interested in the design you have gone for - my (naive) thoughts were just to add an ical/vcard parser and connect the DB tables directly - this does require some duplication of business logic though
What is your basic design? Are you connecting directly to DAV? With a local cache? Or directly talking to the backend db structure?
Thanks
Ed W
On 24/02/13 13:24, Ed W wrote:
Hi
The CardDAV support is being implemented as a new and independent plugin as the Kolab addressbook is completely different and does not support backend 'drivers'.
Our CalDAV implementation is using the SabreDAV (http://code.google.com/p/sabredav/) and the sabre-vobject (https://github.com/evert/sabre-vobject) Libraries.
In both cases our target CalDAV/CardDAV server is SOGo
This sounds very cool. Kolab seems like the best implemented PHP calendar/contacts/Notes frontend right now.
Yes, the Kolab team have done a great job on this plugin.
However, SOGo already has an excellent web interface which does almost everything Kolab does - I'm slightly curious as to why you don't use it?!
We have been using Roundcube for longer than SOGo. We have an investment into Roundcube in the way of plugins etc. The SOGo interface, although fully functional, does not have the same level of polish that Roundcube has. Asking people to swap from the Roundcube to the SOGo UI for using groupware technology is not something we want to do.
I would not want to presume or dictate anything for SOGo, however if the SOGo team would have an alternative end-user UI and does not need to spend time and effort maintaining their own webmail/addressbook/calendar product. It would be possible for them to spend more time on the backend core and possibly a management UI that would be more beneficial to the community as a whole
My interest is that I find roundcube slightly more responsive and also simpler to deploy. It's also easier to modify and extend. However, whilst I'm a bit scared by a lot of the code, OwnCloud is looking like my best partner and it's basically a wrapper around sabredav. (I like the DAV filesharing piece for our solution)
We evaluated OwnCloud a while back. We were not so impressed and decided not to look at it further. With regards to DAV file-sharing, we had a AjaXplorer system deployed before OwnCloud existed.
As such my initial thought for integration with roundcube was to talk directly to the backend databases. Kolab expects all the fields to be in separate columns, but owncloud simple stores the original vcard/ical field as a blob and it requires parsing. Interested in the design you have gone for - my (naive) thoughts were just to add an ical/vcard parser and connect the DB tables directly - this does require some duplication of business logic though
What is your basic design? Are you connecting directly to DAV? With a local cache? Or directly talking to the backend db structure?
As stated, we are talking CalDAV and CardDAV. We are working from the RFCs as far as they are implemented in the SOGo backend.
There is no dependency on the backend implementation, which for SOGo could be MySQL, PostgreSQL, Oracle or LDAP and for other servers could be anything. Data is communicated via HTTP requests like PROPFIND from/to URLs like "/principals/" and "/.well-known/". Data is read, parsed and written as standard iCalendar/vCalendar and vCard objects.
There is no client side caching implemented as of now. As the Kolab plugin assists in only requesting the data that is to be displayed the requests are relatively small. As the server supplies an ETAG for the calendar as a whole, it should be possible, without too much effort, to cache the data without risk of using stale information.
Regards,
Chris
Thanks
Ed W _______________________________________________ Roundcube Development discussion mailing list dev@lists.roundcube.net http://lists.roundcube.net/mailman/listinfo/dev
On 2013-02-22 12:14, Chris Moules wrote:
The Calendar support is implemented by extending the Kolab plugin(s). A CalDAV driver is being implemented for calendar and tasklist plugins.
Hi Chris,
please feel more than welcome to ask us to pull in the CalDAV backend as a driver for the Kolab calendar plugin, when you're ready, in fact I'd much appreciate if you did.
If you feel so inclined, I'm also open to discuss direct commit access to our GIT repository, and/or bounce back and forth some GitHub push/pull requests.
Kind regards,
Jeroen van Meeuwen
Hello,
Does this code is actually accessible somewhere, as I would like to participate.
I have a caldav server (davical), and I should be able to test it.
My page on github: https://github.com/arodier/Roundcube-Plugins, where I have developed three small plugins useful for enterprises.
Kind regards, André
On Friday, 22.02.13 at 13:14, Chris Moules wrote:
On 14/02/13 10:00, Thomas Bruederli wrote:
Nieścierowicz Adam wrote:
So when looking through google, I found resources on the stand AGPL license client thought that maybe someone is willing to finish on AGPL license.
The calendar module provided by Kolab is under APGL but currently lacks a CalDAV backend. There are plans to add this but the work for that isn't scheduled yet.
Personally, I am ready to sponsor a programmer, maybe others willing to help?
I could connect you with the programmers who announced their intents to add CalDAV to the Kolab calendar module. Or maybe they're even listening on this list (therefore cc-ing the dev list).
Regards, Thomas
Hello,
we at GMS (http://www.gms.lu/ - https://github.com/GMS-SA/)are the company Thomas hinted at who are working on CalDAV and CardDAV support.
The Calendar support is implemented by extending the Kolab plugin(s). A CalDAV driver is being implemented for calendar and tasklist plugins.
The CardDAV support is being implemented as a new and independent plugin as the Kolab addressbook is completely different and does not support backend 'drivers'.
Our CalDAV implementation is using the SabreDAV (http://code.google.com/p/sabredav/) and the sabre-vobject (https://github.com/evert/sabre-vobject) Libraries.
In both cases our target CalDAV/CardDAV server is SOGo (http://www.sogo.nu/). Development is trying to stay as RFC complaint as possible. There are cases, however, where SOGo diverges from the RFC or the RFCs were published later than features were implemented in SOGo. In such cases it is planned to have config options for server support so that this does not become a SOGo plugin. Our main focus is SOGo as this is what we are using.
Work is well underway. Most functionality is implemented but there is still lots to do before a release is expected. We are not talking years but probably over 1 month.
Regards,
Chris
P.S. Thomas, if you wish to re-post this to the 'users' list, to which I am not subscribed, please feel free. _______________________________________________ Roundcube Development discussion mailing list dev@lists.roundcube.net http://lists.roundcube.net/mailman/listinfo/dev
-
Andre Rodier -
Chris Moules -
Ed W -
Jeroen van Meeuwen (Kolab Systems) -
Roy Thompson -
Thomas Bruederli