Is this going to become a trend? Project starts making trademark claims years after a downstream library has been using it without issue. Bit rich, given how accessible libraries can bootstrap an initial product ecosystem.
Is it ever safe to use a trademark name? Will all packages now have to be generic enough to imply the product for which they connect? It”s not a Java/AWS/Redis/Wordpress/Shopify extension, but a thingbob, which just so happens to connect to That-Which-Shall-Not-Be-Named.
Trademark claims are also defended by the otherwise useless PSF. Here GvR objects to someone continuing Python-2 uńder the name "python-2.8" as well as "py28". Informally, bringing in lawyers was threatened at one point:
This serves as a lesson when naming projects -- call it something different to the core product. If you must have a package called ${name}-rs make it a wrapper around your repo.
While it's difficult to compare the pettiness, this is definitely sillier than the WordPress thing as far as trademark enforcement goes.
Trademark-as-a-Weapon is becoming too common now. Are we going to be forced to use legally distinct (and confusingly different) names for all our libraries now to defend against this nonsense? Pick projects based on the brand protection posture of the licensors? What a waste of time.
I would love for someone to fight out these bullshit trademark claims. Are you seriously going to win against a crate author for using your business name after letting them do it for 10 years and even featuring and recommending them on your own website?
Who is going to pay to defend? The rust author is making it clear they want no part of this legal mess. Which is going to be true for nearly any open source contributor. The only people with legal representation are going to be the VCs looking for value extraction.
Yes, that’s the problem. I understand the perspective of the maintainers but it leads to a situation where the large corporation can do illegal stuff and bully people around because it’s too much effort to fight back.
Looks like Mysqlization tragedy, the best would be when FOSS maintainers join their corporate agile sprints to meet roadmap demands, with naming rights gun aimed under table lol.
First time I hear about Valkey, it acts as MariaDB in this drama. /s
Twitter essentially hasn't loaded for me since Musk took over, so: https://archive.is/c5lnW or,
> Looks like Redis is trying to take over the all the OSS Redis libraries.
> Jedis, Lettuce, and redis-py are down, they are now threatening redis-rs (link in reply).
There's no link in the post, and I don't have a link to the referenced reply, but I'm guessing the link is https://github.com/redis-rs/redis-rs/issues/1419
Is this going to become a trend? Project starts making trademark claims years after a downstream library has been using it without issue. Bit rich, given how accessible libraries can bootstrap an initial product ecosystem.
Is it ever safe to use a trademark name? Will all packages now have to be generic enough to imply the product for which they connect? It”s not a Java/AWS/Redis/Wordpress/Shopify extension, but a thingbob, which just so happens to connect to That-Which-Shall-Not-Be-Named.
Trademark claims are also defended by the otherwise useless PSF. Here GvR objects to someone continuing Python-2 uńder the name "python-2.8" as well as "py28". Informally, bringing in lawyers was threatened at one point:
https://github.com/naftaliharris/tauthon/issues/47
The project was renamed to "tauthon".
This serves as a lesson when naming projects -- call it something different to the core product. If you must have a package called ${name}-rs make it a wrapper around your repo.
You can’t do that and expect it to be used. When someone needs a redis client library they search for ‘redis’ not ‘thingamabob’.
While it's difficult to compare the pettiness, this is definitely sillier than the WordPress thing as far as trademark enforcement goes.
Trademark-as-a-Weapon is becoming too common now. Are we going to be forced to use legally distinct (and confusingly different) names for all our libraries now to defend against this nonsense? Pick projects based on the brand protection posture of the licensors? What a waste of time.
I would love for someone to fight out these bullshit trademark claims. Are you seriously going to win against a crate author for using your business name after letting them do it for 10 years and even featuring and recommending them on your own website?
(Referencing https://github.com/redis-rs/redis-rs/issues/1419 )
This looks a lot like the wordpress issue… i think the oss wars of the 2020s will be fought around trademarks?
One more reason to move to valkey i guess.
Who is going to pay to defend? The rust author is making it clear they want no part of this legal mess. Which is going to be true for nearly any open source contributor. The only people with legal representation are going to be the VCs looking for value extraction.
Yes, that’s the problem. I understand the perspective of the maintainers but it leads to a situation where the large corporation can do illegal stuff and bully people around because it’s too much effort to fight back.
At least they offered to buy it.
Is that any different from someone offering to buy a browser extension to add malware?
Sic transit gloria mundi
Looks like Mysqlization tragedy, the best would be when FOSS maintainers join their corporate agile sprints to meet roadmap demands, with naming rights gun aimed under table lol. First time I hear about Valkey, it acts as MariaDB in this drama. /s