this post was submitted on 01 Apr 2026
78 points (94.3% liked)

Technology

83502 readers
2865 users here now

This is a most excellent place for technology news and articles.

Our Rules

  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots

founded 2 years ago
MODERATORS
L3s@lemmy.world
enu@lemmy.world
technopagan@lemmy.world
L4s@lemmy.world
L3s@hackingne.ws
78
ONLYOFFICE accuses "Euro-Office" maker Nextcloud and IONOS of License Violation (www.onlyoffice.com)
submitted 4 days ago by zr0@lemmy.dbzer0.com to c/technology@lemmy.world
23 comments fedilink hide all child comments
 

Recently, IONOS and Nextcloud announced their new, sovereign office suite called “Euro-Office” and claimed they were using components of ONLYOFFICE. It seems they are doing so without checking the licences first and without cooperating with them.

Original announcement:

Nextcloud and Ionos are promising a modern, open-source office suite for the summer. To achieve this goal, they have forked OnlyOffice.

heise.de

ONLYOFFICE reply:

Based on publicly available information, the “Euro-Office” project uses technology derived from ONLYOFFICE editors in violation of our licensing terms and of international intellectual property law.

onlyoffice.com

you are viewing a single comment's thread
view the rest of the comments
[–] partial_accumen@lemmy.world 2 points 1 day ago

This is “open” source and it was the main reason it got forked (lots of proprietary bits included as binary, impossible to send a PR, obfuscated code)

Wasn't this methodology the whole reason GPL 2 evolved to GPL 3 because Tivo was doing this exact thing? They used the underlying open source free work of others, but then wrap their own contributions in priopriatry binaries not distributed with source code. This method wasn't in violation of the letter of GPL rules even though it was clearly a violation of the spirit of the GPL rules.

How are they able to skirt the GPL 3 rules this time?