He's dead, Jim. --- Isn't he?
onex.de last edited by
As there are as good as no updates on Kopano since several months and the UCS 5 integration is lagging one year behind the UCS 5 announcement, I’d like to know, if someone is working on this project anymore or if we can consider Kopano as a nice tool of the past.
If second, rest in peace my little friend. I had a good time with Zarafa and later on Kopano, but everything comes to an end, unfortunately.
BusinessTux last edited by
@onex-de Hi Christian,
like you I’ve waited a long time for a new version. But unfortunally there was no sign. Thanks Kopano for the last years.
Now I’ve migrated to grommunio and it works very well, including the kopano-importer.
wleithner last edited by
Afaik, kopano team
is working on a new product which will not be part of UCS.
Kopano One was shut down early this year for all I know.
I’d rather stick with Kopano than cross over to grommunio.
tose last edited by tose
Yes, like you all I have for many years run Zarafa & later Kopano4UCS installations, not only for my own business, but also for several of my own customers. I’ve also maintained a paid Kopano subscription for many years.
While I’m loathed to criticise any open-source project, what I do find slightly disappointing in all of this is the lack of clear statements of intent from the stakeholders.
Univention for it’s part has had a clear warning/disclaimer on the Software Update module of it’s UCS Web management portal, making clear that Kopano Core, Webapp & Z-Push are not “UCS 5 compatible”. That rang alarm bells for me as soon as I saw it well over 12 months ago. And maybe that’s all Univention could say given they have no responsibility for Kopano development.
What I think would be really useful to all of us would be a clear statement of intent from Bytemine/Kopano on the future of the Kopano4UCS integration. It’s been abundantly clear both here and on the Univention Help forum that long time users are crying out for that.
Yes I’ve read the statements from Bytemine saying Kopano is in the UCS5 “Testing” repository. But it’s clear that there seems to be a lack of urgency &/or leadership on moving the Kopano4UCS integration forward, which is a great shame given how capable the product has been & still is. What we are all staring down though, is finding an alternative to Kopano should that sort of certainty not be forth-coming given the impending end-of-support for UCS4.
For my part I would be happy to make significant contributions to testing of a UCS5 compatible Kopano4UCS integration were there to be clear statements of commitment towards it’s future. Let’s hope he can be resuscitated Jim.
xthbx last edited by
I moved to mailcow except the missing synchronisation for notes I’m pretty happy
aBrAEUMER last edited by
like Scotty wasn’t dead in the end, it seems to be the same about kopano4ucs.
indicates it to be on the home straight and it’s univentions turn by now.
Univention itself gave a statement two days ago
(german; not available in english, yet)
about the end of life of UCS 4.4 (Sept.'22) and suggesting the Kopano-Updates (Kopano WebApp, Kopano Core and Z-Push for Kopano) will be available for UCS5 within “weeks or month”.
Spocks resurrection needed 24 month from Wrath Of Khan to Search For Spock. Let’s hope kopano4ucs to be a bit faster. Scotty did it within the 45-minutes episode.
mcostan last edited by mcostan
Sadly it is dead…
I think the options are as far as I can tell:
*freeze your present installation and keep it like this forever. This is what I am doing.
*move to another product.
It is something very very sad. Kopano (or zarafa in my case that’s where I started from originally) has been an amazing product.
Yet, I suppose once the support for direct integration with Microsoft Outlook ended, it must have been difficult to maintain paid subscriptions and without licenses coming in, I can only assume that there hasn’t been much money for further development and it is now in maintenance only mode, that is waiting for the customers to slowly disappear one by one, in the mean time maintaining a skeleton staff to support current paid installations.
For as much as I would like to think otherwise, I cannot see any other interpretations of what’s happening here.