They use a modified version of the AGPL that includes a requirement to use their logo.
They also, in a separate subsection, note that no permission is granted to use their trademarks.
As far as I can tell, the goal is to create a catch-22 that prevents you from forking the project: if you don’t include the logo, they complain that you didn’t include it, and if you include the logo they complain that you’re infringing their trademark.
Edit: Or more specifically, OnlyOffice’s position is that the logo requirement is not a modification because they think it’s an attribution requirement allowed under section 7(b).
Fun fact - GNU / FSF doesn’t let you claim it’s a GPL variant if you have added claims to it. If you say it’s GPL then others gets to assume it’s GPL proper
You can legally use the GPL terms (possibly modified) in another license provided that you call your license by another name and do not include the GPL preamble, and provided you modify the instructions-for-use at the end enough to make it clearly different in wording and not mention GNU (though the actual procedure you describe may be similar).
If you want to use our preamble in a modified license, please write to licensing@gnu.org for permission. For this purpose we would want to check the actual license requirements to see if we approve of them.
Although we will not raise legal objections to your making a modified license in this way, we hope you will think twice and not do it. Such a modified license is almost certainly incompatible with the GNU GPL, and that incompatibility blocks useful combinations of modules. The mere proliferation of different free software licenses is a burden in and of itself.
In summary, people who modify programs released under the GNU GPLs can still change where and how an interactive program displays those notices. For example, if the original program put these notices at the bottom of every page, someone modifying the software could conceivably remove those and have them appear only on a single “About this software” page.
Apart from some specific situations, logos are neither “legal notices” nor “author attributions” as normally understood.
Putting trademarked links or logos in the program’s interface and explicitly declining a trademark license thus gives the trademark holder a way to stop uses harmful to their reputation, balanced by the users’ option to remove the trademarks in order to distribute modifications freely
They use a modified version of the AGPL that includes a requirement to use their logo.
They also, in a separate subsection, note that no permission is granted to use their trademarks.
As far as I can tell, the goal is to create a catch-22 that prevents you from forking the project: if you don’t include the logo, they complain that you didn’t include it, and if you include the logo they complain that you’re infringing their trademark.
Edit: Or more specifically, OnlyOffice’s position is that the logo requirement is not a modification because they think it’s an attribution requirement allowed under section 7(b).
Fun fact - GNU / FSF doesn’t let you claim it’s a GPL variant if you have added claims to it. If you say it’s GPL then others gets to assume it’s GPL proper
https://www.gnu.org/licenses/gpl-faq.html#ModifyGPL
As for attribution requirements;
https://www.fsf.org/blogs/community/gpl-compliant-legal-notices-author-attributions