Ok, so I just recently found out that OnlyOffice has a nice "community" (AGPLv3) version, and it can easily be integrated with NextCloud. So I've just set up a my own self-hosted instances of both. Wow. GoogleDocs ain't got nothing on this.
@lightweight I suspect that in most cases, "enterprise" editions are mostly just their specific server configs anyway, along with other stuff that wouldn't be inappropriate or useless to publish. Anything in #GitLab that the self-hosting community actually has a need for tends to get moved to the "#FOSS" edition once someone makes a case for it.
@strypey sadly, that doesn't seem to be the case with Gitlab. For example, the anti-spam user/content provisions... are only in the Enterprise version, and they don't seem to have plans to port them to the Community edition.
@strypey no - the fact that currently, there's no mechanism in Gitlab to allow admin vetting of new accounts, meaning that if you have open registration, it's easy for spam users to create accounts, and very difficult to delete them en mass.
@lightweight right, but what I'm saying is that up until recently they didn't have an in-house system for that either. They just used #reCAPTCHA, complete with non-free JS. There were a bunch of complaints about that on the Issues a few months back and they have been working on a #honeypot based alternative. Last I checked in they're testing it on GL.com, see:
If it's confirmed to work, I can't see why they wouldn't include it in the "FOSS" edition.
@strypey the main issue I have is how to delete large numbers of spam users and associated spam projects due to a year or two of open registrations and no one really paying attention to who's creating accounts... there's a new "bulk delete user" admin feature, as well as a "admin moderated account creation" workflow that have been implemented for the enterprise version, but not push to the #FOSS version.
@lightweight their practice seems to be to test new features on GL.com, where they can control for more variables, then rollout the code once they're sure the feature actually works. Also, as I say, the squeaky wheel seems to get oiled. I've seen code released after requests in HN threads. If you hit them up about needing those features on your instance, I suspect they will either reply with a timeline for that in their current plans, or add it to their release plans.
@strypey this is the issue I commented on: https://gitlab.com/gitlab-org/gitlab-foss/issues/17435
@strypey at the bottom of the thread you cited re reCAPTCHA, https://gitlab.com/gitlab-org/gitlab-foss/issues/46548 someone describes a way to remove existing spam users.... I think it'd be great (as do others) but no indication if it's been recorded and the issue's now closed...
> the issue's now closed
True, but removing spam users was not the focus on that issue. there's a whole cluster of issues related to the reCAPTCHA system and its proposed replacements, along with other user managements issues that have fallen out of those discussions. If you care to explore you can follow links from that issue to some of the others. But it seems all issues are being moved to the ee repo to reduce duplication, so it's all a bit hard to navigate at present.
@gitlab self-hosting users want access to some of the spam prevention and user management features that have recently been rolled out on GitLab.com. What's the prospects for that? a) is there already a timeline for moving these features to the free code edition? b) if not, could you be convinced to do so?
@lightweight that's not perfect, but seems to pay the bills for many foss enterprises I guess...
@bj00rn I'm not a fan of that model, myself... it undermines the goodwill, for sure. I think there are more ethically consistent ways to do it, but VCs won't go for it. Which is why I don't have time for VC...
@lightweight I'm running a public OnlyOffice instance and yes,it's really a cool software if you somehow managed to get it to work correctly.It was very difficult here.I don't like the idea with Enterprise versions but also it shouldn't be a big problem.The list shows some limitations like only 20 connections at the same time but as it's open source under AGPL,you can simply remove the limit which would be totally legal with this license.
@nipos Yes, I've been pondering that :) - and it's very straightforward getting it working with Docker-Compose, and it should be quite maintainable, too.
@lightweight It took me three days to get it to work using Docker.In the end I tried to install the Document Server directly on the server using apt-get and run only the Community Server within Docker.That worked better somehow but I still don't know why.Well,it works and that's what matters...
@lightweight hmm what is better than CollaboraOffice there?
@rugk At this point, a colleague and I've only played with it a bit, but it is faster with a more polished interface, and more features, with excellent (**spits**) OOXML compatibility. I hate fauxpen standards, but sadly, most of the world has been hapless (and short-sighted) enough to let it become the only viable "standard" for the moment.
@lightweight yeah I've heard that OOXML, but apart from this if you only edit odt etc. files, is it still better?
@rugk it doesn't really seem to support ODF formats very well - you can save that way, but it doesn't let you edit them - you have to import/convert them to OOXML formats.
@rugk my general early impression is that it's quite a bit more advanced than Collabora at the moment, usability-wise.
@lightweight This sounds interesting to me, I currently have a Nextcloud server behind Traefikv2 running and have been trying to integrate a Collabora server for 2 days now. Do you think it will work better with a OnlyOffice Community Server? I built everything with docker-compose without swarm or similar, just as a single server.
@lightweight Can you share any detail to get started? I've been looking into this a while back and then I couldn't really figure out how to do it?
@lightweight such a great idea, thanks for sharing!