https://www.theregister.com/2025/02/27/adverse_appeals_court...
41 karma · joined December 6, 2022
https://www.theregister.com/2025/02/27/adverse_appeals_court...
There will be case law after appeal - FSF seems too timid to sue Neo4j (which they could do) and save decades of work.
maybe I misunderstood what you were saying…
https://www.fsf.org/news/fsf-submits-amicus-brief-in-neo4j-v...
Neo4j quietly slipped the Commons Clause into what looked like a standard AGPL license, complete with the FSF copyright and preamble, until a single person called them out.
Instead of owning up, Neo4j spent nearly a decade and tens of millions trying to crush one person. Not the best business minds over there…
Anyway - it sounds like Liquibase didn’t go to that extreme and fixed their messaging as soon as the community educated them.
Calling it Infinigraph is a much better marketing move than saying “We finally fixed our clustering implementation to properly shard and scale”.
Have they finally managed to fix the scalability issues?
I would avoid Neo4j open source offerings (community edition, etc) like the plague until their court case is over. They are fighting to be able to use their interpretation of what GPL terms means - and from their past behavior - it’s probably going to be bad news for anyone who adopted it because it was open source.
Neo4j got to where they are on the backs of the open source community, which makes this situation that much more maddening.
The case centers on who has the authority to interpret the terms of an open-source license:
1.The software developers who adopt licenses like GPLv3, MIT, or Apache 2.0 for their projects OR 2. The original authors of those licenses (FSF, Apache Foundation, etc)
If the appeal fails to overturn the flawed lower court ruling, it will set a precedent allowing legal cases to focus on how software developers themselves interpret the terms of licenses like GPLv3, MIT,Apache 2.0, etc. This is precisely what happened with Neo4j.
This issue is significant enough that two of the leading open-source foundations submitted amicus briefs in the case.
I think Neo4j knows it is wrong after this latest Amicus and they have the power to stop this in its tracks by simply settling the case before the ninth circuit makes a ruling which will be precedent.
Pretty crazy situation!
Adobe and Microsoft must love that.
1.The software developers who adopt licenses like GPLv3, MIT, or Apache 2.0 for their projects
OR
2. The original authors of those licenses (FSF, Apache Foundation, etc)
If the appeal fails to overturn the flawed lower court ruling, it will set a precedent allowing legal cases to focus on how software developers themselves interpret the terms of licenses like GPLv3, MIT,Apache 2.0, etc.
This is precisely what happened with Neo4j.
This issue is significant enough that two of the leading open-source foundations submitted amicus briefs in the case.
I think Neo4j knows it is wrong after this latest Amicus and they have the power to stop this in its tracks by simply settling the case before the ninth circuit makes a ruling which will be precedent.
Pretty crazy situation!
Many in the community are only just starting to realize the potential impact of this case on FOSS licensing
If the Ninth Circuit upholds the lower court’s ruling, it won’t just threaten the GPL, it could undermine all open-source licenses, undoing years of work to protect software freedom.
From your comment, it sounds like you don’t really understand what is at stake, which is understandable considering the complexity.
The GPLv3 (including AGPLv3) will effectively die as no one can trust projects using these licenses if upheld.
GPLv3 will be decimated if the ruling is upheld. You could never trust that a GPLv3 licensed project could not pull a bait and switch like Neo4j in the future.
The lower court’s ruling effectively says that a licensor can override open-source freedoms by tacking on new restrictions, even when using a license that explicitly prohibits them.
If upheld, this decision could be cited in future cases to argue that a licensor’s intent matters more than the actual terms of the license, opening the door for companies to attach proprietary restrictions to open-source projects without consequence.
In other words, the entire legal framework that ensures open-source licenses are binding and enforceable is at risk, making it easier to impose restrictions after distribution—something previously considered legally untenable.
This isn’t just about “virality” in GPLv3, it’s about whether any open-source license can still be trusted to mean what it says.
That is a big deal.
Neo4j’s actions are very disappointing.
It’s hard to ignore that this litigation is aimed at someone who also happens to be the founder of the two largest free and open-source Neo4j forks, ONGDB and DOZERDB.
Makes you wonder if this litigation is really about stifling open-source competition.
GlassDoor reviews depicting internal turmoil, an ongoing trial likely heading to appeal, and their US trademark facing possible cancellation are not painting the prettiest of pictures.
This combination of factors contributes to the peculiar timing of the IPO announcement and the lack of marketing around it.
The way the investor jumped on the board and announced the IPO feels like he was commandeering a sinking ship trying to save it.
I may be completely wrong - only a few people really know what is going on.
https://github.com/neo4j/neo4j/commit/b6237ca4e31706b1efbd0f...
On another note - does anyone know if Apache Age can be used to achieve multi database functionality?