No trademarks in upstream source [LWN.net]

No trademarks in upstream source

Posted Mar 4, 2025 12:45 UTC (Tue) by ballombe (subscriber, #9523)
In reply to: No trademarks in upstream source by NYKevin
Parent article: Fedora discusses Flatpak priorities

What about trademark reference included in API/ABI ?

But fundamentaly, if the trademark make it too onerous to modify the software, we still have option to declare the software non-free. This is not a legal determination.

to post comments

No trademarks in upstream source

Posted Mar 4, 2025 13:36 UTC (Tue) by Wol (subscriber, #4433) [Link] (4 responses)

> What about trademark reference included in API/ABI ?

> But fundamentaly, if the trademark make it too onerous to modify the software, we still have option to declare the software non-free. This is not a legal determination.

Your problem, then, is that you are unable to copy the software without breaking the GPL !!!

I think it was Nintendo? - lost a lawsuit over "unremovable trademarks" probably thirty years ago. If removing the trademark breaks the software, then the trademark is "essential to the operation" and loses its protection.

But why is everybody so obsessed with defrauding their own downstream? Why is everybody so obsessed (in the name of freedom) with violating the GPL?

The GPL itself requires you - unless it's a verbatim copy! - to *prominently* *mark* *it* *as* *your* *own* *version*. This is the problem with Fedora - their own users simply had no idea it was not the genuine upstream article. That's a GPL violation!

The threat of trademarks is simply a way of enforcing the GPL - "If you don't add your own marks, you have to remove mine". That's not a demand to remove marks - it's a demand that you follow your GPL obligations!

Cheers,
Wol

No trademarks in upstream source

Posted Mar 4, 2025 14:48 UTC (Tue) by draco (subscriber, #1792) [Link] (1 responses)

> The GPL itself requires you - unless it's a verbatim copy! - to *prominently* *mark* *it* *as* *your* *own* *version*.

Wol, please cite the exact license text (and context/location in the license)

The only things I find in GPLv3, GPLv2, & LGPLv2.1 are:
* In the preamble, it says modified versions should be clearly identified so the original author isn't besmirched. It then says the exact terms are specified later, so while there's an intent there, it's not (as I read it) the binding text
* Later it says that the *sources* must be marked as modified and when (but not how)
* License must be clearly marked
* Original source must be clearly marked if in a combined work
* GPLv3 does allow you to add licence terms to strengthen this further, but it's not the default.

There is nothing about "must mark the resulting version as your own"—just that it must be clear what the license is (so they know they can request source) and then that source must make the modification clear.

I dunno about flatpaks, but assuming there's some way to track them back to their sources/build recipes, then it should be clear they're based on the RPM.

RPM versions inherently identify themselves as distinct from the upstream version (due to the RPM release version added) so that format plus its storage in Git by the Fedora project addresses all the license terms of use (or should).

I didn't read the terms exhaustively, so if I missed something, please point it out.

You've also filed a bug, I assume? From what I've seen, the project takes licensing extremely seriously (they've done intensive license audits, catching numerous violations and defective licenses that other distributions missed)

No trademarks in upstream source

Posted Mar 4, 2025 19:44 UTC (Tue) by Wol (subscriber, #4433) [Link]

Thanks to NYKevin for this, but ...

> 5. Conveying Modified Source Versions.

>You may convey a work based on the Program, or the modifications to produce it from the Program, in the form of source code under the terms of section 4, provided that you also meet all of these conditions:

> a) The work must carry prominent notices stating that you modified it, and giving a relevant date.

> 7. Additional Terms.

> c) Prohibiting misrepresentation of the origin of that material, or requiring that modified versions of such material be marked in reasonable ways as different from the original version; or

Hmm ... so it sounds like misrepresenting the origin isn't *automatically* a GPL violation, but it's certainly acceptable for it to be one.

Cheers,
Wol

No trademarks in upstream source

Posted Mar 4, 2025 18:10 UTC (Tue) by ballombe (subscriber, #9523) [Link] (1 responses)

> But why is everybody so obsessed with defrauding their own downstream? Why is everybody so obsessed (in the name of freedom) with violating the GPL?

Quite the contrary. I do not want to defraud anyone. If upstream does not want that I distribute modified versions, I will not do it. But then I will not consider the software FOSS. That is as simple as that.

No trademarks in upstream source

Posted Mar 4, 2025 19:50 UTC (Tue) by Wol (subscriber, #4433) [Link]

> Quite the contrary. I do not want to defraud anyone.

So why don't you care that *your* *downstream* has no idea of the true origin of the software in question? It's morally indefensible (and quite likely illegal) to misrepresent someone else's software as your own; so why do you consider it perfectly acceptable to misrepresent your software as someone else's? That's what I mean about defrauding your own downstream.

(And that's why trademarks got dragged into this, that is exactly what trademarks are for.)

Cheers,
Wol