Overleaf: Docker 0.6.2 - Track changes and comments does not work

Created on 20 May 2017 · 8Comments · Source: overleaf/overleaf

Docker image 0.6.2 Track changes and comments does not work.

Source

ma-karai

Most helpful comment

Sorry, but this needs some further clarification for me. You are saying ShareLatex is under AGPL. If I upgrade a free account to "Collaborator" or "Professional", I will be able to use features for which I am not allowed to see the source code, which in turn violates AGPL. Am I mistaken here?

gitfortat on 18 Dec 2017

👍4

All 8 comments

only available in pro edition.

ma-karai on 23 May 2017

But the complete source for ShareLaTeX is available here, correct? If I compile my own docker container, shouldn't all features be available?

tarheels100 on 13 Jun 2017

Really disappointing that track changes and comments are pro-edition only.
I can understand why user management and sandboxing would be pro but leaving out such a feature in the open-source edition just seems mean!

zeigerpuppy on 30 Jun 2017

👍2 😕1

We have to draw a line in the sand somewhere I'm afraid. It takes a lot of developer time to build these new features meaning we can't afford to make every feature free.

henryoswald on 30 Jun 2017

I am very disappointed that tracking changes is actually not available in the normal version. Is it really ok to still say this software is under AGPL? I think you should point out that there are two versions. One under AGPL, with less features, one under whatever (proprietary?) license. I am not against making money with software; but it should still be free (libre). I would pay for development of features that I need and I would also donate money, but only for free software.

gitfortat on 16 Dec 2017

👍1

Hi,

this is a very common pattern used by many companies to build a business. ShareLaTeX is still AGPL, there is also a handful of premium features which we offer on ShareLaTeX.com and via premium self install (server pro). All our open source (AGPL) code is still open source and being maintained, just some new code is not being opened soured via AGPL.

henryoswald on 18 Dec 2017

gitfortat on 18 Dec 2017

👍4

Agreed, this sounds like an AGPL violation to me. Does the company have any intention of changing this - or must the community build their own tool for this?