Hi, thanks a lot for your answers. It helps a lot to understand how SOGo has evolved during the last, years! To be honest, I wasn’t really aware of the shift from Inverse to Alinto.
I’d like to get back to one of answers. You wrote: > Am 04.11.2024 um 17:00 schrieb qhivert ([email protected]) <[email protected]>: > > >> Sogo is an opensource project from 2004 and Alinto only took the wheel 2 >> years ago. We were already using it, then the previous owner, Inverse, was >> abandoning it so they offer us to have it. Since, we're doing our best to >> make new releases (https://www.sogo.nu/news.html) and as much bug fixes as >> possible. However, our human and time resources are limited, and we must >> prioritize our tasks. Also, paid customers have a private bug tracker you >> can't see where the bugs reported are obviously prioritized. > The public bug is mainly used to communicate with Alinto. We do read all the > new bugs but only answer when we are sure to have the time to investigate and > fix it. Sometimes, other experienced user can give their inputs and help too. > The number of bugs can be alarming but there is so much different > configurations, environments, or way to use sogo that most of them are > peculiar cases and we and other users don't reproduce them. Also, we didn't > clean it after inverse so I'm sure a lot of the bugs are now obsolete or > already fixed. The largest users are impacted by a bug, the highest are the > chances we're going to fix it. We also are very careful when a new release is > made and when a bug is reported after one of our nightly commits. > There is not much PR from the community because sogo is old and complex, with > rare language (objective-c, angularjs material). So, it's kind of hard to get > into it. > That being said, SOGo is fully operational and not at all abandoned. We're > making new releases every 3/4 months with new features and bug fixes and our > community is actually growing. You should definitely give it a try if you're > interested in it. > Our company moved away from SOGo more than a year ago. A previous sysadmin installed a server - iirc - about 3-4 years ago; a „pre-production“ like test system. Our move was mostly motivated by a plethora of bugs that made it very frustrating for my colleagues to use SOGo. To be honest, finding bugs like https://bugs.sogo.nu/view.php?id=6053 shortly after a daylight-saving-time change somehow triggers a fear of Whac-A-Mole of timezone related bugs. As of today, I'm no longer super-positive about maintaining a server on our own. If you know of good cloudhosters (GDPR-compliant data-processor, competent end-user support), just let me know ;-). The partner list on the webpage is a little short and does not really advertise SaaS/Pay-as-you-go offers. But getting back on your answer "sogo is old and complex, with rare language (objective-c, angularjs material)“ This sounds a bit like technical debt. Server-side objective-C might qualify as eccentric, but angularjs was superseded by angular years ago. Do you have mid to long term perspective for addressing the design of SOGo? My gut feeling is that SOGo gains traction because it is one of the most (if not the most) attractive open-source groupware as of today w.r.t operations. It could also gain traction due to mailcow. As you already pointed out, it might not be very attractive for OpenSource committers, though. Do you have any thoughts on this? Thanks in advance, Jan
