Re: Ok. Looks like this one _may_ fulfill our calendering needs. Testing required.
On Mon, 2010-01-25 at 13:14 +0530, susmit shannigrahi wrote: As you are doing testing right now, would it help to have a instance here in fedora-infra so that we can figure out if it suites our needs? I think that would be nice, yeah. It would be good to have an egroupware instance up alongside the zarafa instance so people can try both and see which they prefer. What do you need from me? Fedorized packages for egroupware? Thanks! -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: Ok. Looks like this one _may_ fulfill our calendering needs. Testing required.
On Fri, 2010-01-22 at 14:18 -0500, Brennan Ashton wrote: I have deployed this as well a few times thought its history and it has served me well each time. One thing to consider is how large of a service it is, I have never really had to bother with trimming all the extra features (mail, address book etc...) from it. It's fairly well modularized. See the Mandriva package list: egroupware-developer_tools egroupware-egw-pear egroupware-emailadmin egroupware-etemplate egroupware-felamimail egroupware-filemanager egroupware-gallery egroupware-icalsrv egroupware-importexport egroupware-infolog egroupware-manual egroupware-mydms egroupware-news_admin egroupware-notifications egroupware-phpbrain egroupware-phpsysinfo egroupware-polls egroupware-projectmanager egroupware-registration egroupware-sambaadmin egroupware-sitemgr egroupware-syncml egroupware-timesheet egroupware-tracker egroupware-wiki egroupware-workflow all you really need installed for it to work at a basic level is the main package, emailadmin (the setup process won't complete without it), etemplate and calendar. Well, calendar was listed as a dependency by the previous maintainer, who I'm assuming knew what he was doing. I can't personally confirm that the app doesn't work without it. You don't need even the webmail chunk, let alone any of the more esoteric bits. I did test it some more today. I have working three-way sync of my real calendar and contacts - egroupware / desktop / laptop. Evolution seems quite flaky at transferring large amounts of data all at once - especially, for instance, trying to dump 50 contacts direct from a Google calendar (accessed by CalDAV) into the egroupware calendar (also accessed by CalDAV) tends to make it fall over. But I suspect that's as much Evo as anything else, I don't think anyone's really stressed its CalDAV capabilities much, and I'm running Rawhide. Once I got the data in, in small enough lumps, it works fine. I can't seem to make my Windows Mobile phone sync with the egroupware server; it should be possible via the Funambol client for Windows Mobile, which does SyncML synchronization. egroupware supports SyncML, and this is the method upstream recommends for syncing with WM devices. I can set it up and it claims to run correctly, but no data ever appears on the phone. That's not really a big deal from the Fedora viewpoint, though, it's not one of our requirements for the project and I'd guess most Fedora people have Android phones or iPhones, not WM phones. I'll probably give it a few more tries over the weekend or next week and see if I can figure out what's wrong. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: Ok. Looks like this one _may_ fulfill our calendering needs. Testing required.
On Sat, Jan 23, 2010 at 2:31 PM, Adam Williamson awill...@redhat.com wrote: On Fri, 2010-01-22 at 14:18 -0500, Brennan Ashton wrote: I have deployed this as well a few times thought its history and it has served me well each time. One thing to consider is how large of a service it is, I have never really had to bother with trimming all the extra features (mail, address book etc...) from it. It's fairly well modularized. See the Mandriva package list: egroupware-developer_tools egroupware-egw-pear egroupware-emailadmin egroupware-etemplate egroupware-felamimail egroupware-filemanager egroupware-gallery egroupware-icalsrv egroupware-importexport egroupware-infolog egroupware-manual egroupware-mydms egroupware-news_admin egroupware-notifications egroupware-phpbrain egroupware-phpsysinfo egroupware-polls egroupware-projectmanager egroupware-registration egroupware-sambaadmin egroupware-sitemgr egroupware-syncml egroupware-timesheet egroupware-tracker egroupware-wiki egroupware-workflow all you really need installed for it to work at a basic level is the main package, emailadmin (the setup process won't complete without it), etemplate and calendar. Well, calendar was listed as a dependency by the previous maintainer, who I'm assuming knew what he was doing. I can't personally confirm that the app doesn't work without it. You don't need even the webmail chunk, let alone any of the more esoteric bits. I did test it some more today. I have working three-way sync of my real calendar and contacts - egroupware / desktop / laptop. Evolution seems quite flaky at transferring large amounts of data all at once - especially, for instance, trying to dump 50 contacts direct from a Google calendar (accessed by CalDAV) into the egroupware calendar (also accessed by CalDAV) tends to make it fall over. But I suspect that's as much Evo as anything else, I don't think anyone's really stressed its CalDAV capabilities much, and I'm running Rawhide. Once I got the data in, in small enough lumps, it works fine. I can't seem to make my Windows Mobile phone sync with the egroupware server; it should be possible via the Funambol client for Windows Mobile, which does SyncML synchronization. egroupware supports SyncML, and this is the method upstream recommends for syncing with WM devices. I can set it up and it claims to run correctly, but no data ever appears on the phone. That's not really a big deal from the Fedora viewpoint, though, it's not one of our requirements for the project and I'd guess most Fedora people have Android phones or iPhones, not WM phones. I'll probably give it a few more tries over the weekend or next week and see if I can figure out what's wrong. As you are doing testing right now, would it help to have a instance here in fedora-infra so that we can figure out if it suites our needs? -- Regards, Susmit. = http://www.fedoraproject.org/wiki/user:susmit = Sent from Calcutta, WB, India ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: Ok. Looks like this one _may_ fulfill our calendering needs. Testing required.
On Wed, 2009-10-28 at 19:36 +0530, susmit shannigrahi wrote: Hi, Zarafa is up at Publictest16. Anyone want to test? Please refer to last three comments of https://fedorahosted.org/fedora-infrastructure/ticket/1197 As I posted to the ticket, I've come across another candidate which appears to meet the requirements and which I don't _think_ we've dismissed already - eGroupWare: http://www.egroupware.org/ it has a decent web interface, doesn't seem to be insane in any way, doesn't need Java (it's PHP), is fairly mature and actively developed, and has CalDAV support for the calendaring stuff. I'm probably going to deploy it on my own network for my own needs, will try to report back on how that goes. My servers run Mandriva, where it's packaged (though a very old version, I'm currently updating the packages). -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: Ok. Looks like this one _may_ fulfill our calendering needs. Testing required.
On Fri, Jan 22, 2010 at 6:16 AM, Adam Williamson awill...@redhat.com wrote: On Fri, 2010-01-22 at 00:08 -0800, Adam Williamson wrote: As I posted to the ticket, I've come across another candidate which appears to meet the requirements and which I don't _think_ we've dismissed already - eGroupWare: http://www.egroupware.org/ it has a decent web interface, doesn't seem to be insane in any way, doesn't need Java (it's PHP), is fairly mature and actively developed, and has CalDAV support for the calendaring stuff. I'm probably going to deploy it on my own network for my own needs, will try to report back on how that goes. My servers run Mandriva, where it's packaged (though a very old version, I'm currently updating the packages). Well...it works! http://www.happyassassin.net/extras/egroupware_caldav_it_works.png egroupware's web interface on the right showing the test appointment I set up, evolution on the left showing the same appointment: it's accessing the calendar from my personal egroupware server, via CalDAV (see the left hand pane). It seems like a pretty impressive little beastie, too. I managed to kill it by somewhat inadvisedly trying to use its webmail support with my fairly underpowered mail server's gigantic IMAP mail boxes, without using the imapproxy instance I have set up on the mail server. I think it timed out on something and left its MySQL database in a broken state. But that's the only problem I had. I haven't gone beyond setting up the test calendar appointment and verifying Evo could connect to it, really, but I'll stress it a bit more tomorrow by trying to get SyncML working, sticking my *real* calendar in it, and trying contacts as well. The server I'm using runs Mandriva; I've updated Mandriva's egroupware packages for this purpose. It'd be fairly trivial to convert the packages to Fedora. Upstream actually provides Fedora packages, but at a glance they're not terribly clean. I haven't checked whether there are any private copies of what ought to be shared resources in egroupware yet, really, but at a glance it doesn't involve any hideous packaging nightmares; it's all just PHP, and it seems to use shared resources where appropriate (it uses quite a lot of php-pear stuff). Do poke me on IRC if you have any questions. Will duplicate this post on the ticket. -- Adam Williamson I have deployed this as well a few times thought its history and it has served me well each time. One thing to consider is how large of a service it is, I have never really had to bother with trimming all the extra features (mail, address book etc...) from it. Brennan Ashton ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
