681–690 of 717 posts
Earlier quoted context omitted.
Which document are you referring to?
Have a look at the trademark assignment document filed with the United States Patent and Trademark Office: https://tsdr.uspto.gov/caseviewer/assignments?caseId=7882673...
Earlier quoted context omitted.
Can you explain your reasoning? Wordpress is pretty scalable, if done right. Even Microsoft uses Wordpress in some of its microsites. I know some of the new federal government sites even use it (for instance whitehouse.gov as part of the USDS project). It's highly supported and has been tested vigorously for decades now. It can at least be considered for various projects, even large ones. Sometimes you don't need a c…
> in some of its microsites Exactly. That's not a large scale enterprise CMS. WordPress is fine for that. But if you wanted to do something that requires fine-grained access control, publishing control, audit logs etc, you're not going to use WP, or you're building a CMS on top of WP. I'm doing that all day because I work in an industry that loves WP and everybody knows WP, so it's easy to collaborate. I've built doz…
I adopted someone's node.js project once, overengineered and cost the company tons of money to run, I rebuilt it in Wordpress for a fairly large regional grocery chain and not only was it vastly cheaper, but the end product was also better and more reliable. So, I'm leery of anyone that writes something off, right off the bat. Pick the best tool for the job, not the ones that is suddenly in vogue to avoid judgement from random devs on HN or Reddit. You can't pigeonhole solutions, be it Wordpress or whatever you decide on.
Earlier quoted context omitted.
He has no self control. His interview on The Primeagen was especially telling. It’s deeply personal for him. His interactions with the WPEngine staff are all spoken about like casual personal relationships. Nothing was handled professionally. No matter who’s right, or to what extent, he’s publicly digging himself a hole.
I mean not only he hopped on a live stream to babble before going to court, he bragged about it and said the WP Engine people are afraid to do the same. This is school yard level big brain moves. https://ma.tt/2024/09/on-theprimeagen/ > I dropped on the livestream for ThePrimeagen earlier today after a colleague pinged me that he was talking about the Silver Lake / WP Engine situation. > Afterward, I also privately s…
You're meaning apart from the active law suit yeah? ;)
Earlier quoted context omitted.
I doubt it. I've been involved with a similarly priced law firm once for an investment in a company I had a small stake in. They misspelled the names of multiple people, fixed it in the next draft version after it was pointed out to them, and then had it pop back up in some of the names a few versions later.
I know more than I'd like to about this topic; I spent most of a decade supporting legal document management systems. Large law firms use document management systems[0] to store their documents. It's a really primitive VCS that integrates with Microsoft Office. The user who checks out a document usually has exclusive access to it until it's checked back in. Other people can check out a copy of the same document, but…
Optimistic locking might work better, as long as the underlying data can be automatically diffed and merged reliably well.
Git generally does well using this approach, though it's pretty easy to diff text.
Earlier quoted context omitted.
My understanding of Matt's position, and what that term sheet he posted is talking about, is that he feels that WP Engine needs a trademark license to cover what it's currently doing. He feels that their usage of the marks exceeds what's generally allowed under the "everyone can use it this way" terms that WordPress.org offers. His position isn't just that they can't use the trademark to apply to their forked version…
> The concessions include that they'd agree to not use their GPL-granted right to fork the code. The point is that including this stipulation (attempting to limit the GPL-granted right-to-fork) appears to be itself against the GPL, and voids Automattic's previously-granted GPL rights. In other words, if you even attempt to get someone to sign away their GPL granted rights, you lose your own GPL granted rights.
GPLv2 is silent on the subject of trademarks, and is a bit vague about additional restrictions -- section 4 would apply to trying to restrict usage of the code, but trademarks are a separate thing. GPLv3 explicitly allows you to decline to license your trademarks (see section 7, the paragraph starting "Notwithstanding any other provision of this License", clause e). This isn't generally called out as one of the big differences between v2 and v3, so I think it's intended more as a legally-spelled-out clarification than a change.
I'm not a lawyer, but the GPLv3 in particular seems compatible with the idea that you can tell someone that they can only use your trademarks so long as they behave in a certain way... so long as you're still allowed to fork the code, strip out those trademarks, and continue using it. Which does seem to be Matt's position. (I mean, he also wants to restrict access to Wordpress.org services, but that's even less in the GPL's area.)
Earlier quoted context omitted.
> The concessions include that they'd agree to not use their GPL-granted right to fork the code. The point is that including this stipulation (attempting to limit the GPL-granted right-to-fork) appears to be itself against the GPL, and voids Automattic's previously-granted GPL rights. In other words, if you even attempt to get someone to sign away their GPL granted rights, you lose your own GPL granted rights.
WordPress is GPLv2-or-later. GPLv2 is silent on the subject of trademarks, and is a bit vague about additional restrictions -- section 4 would apply to trying to restrict usage of the code, but trademarks are a separate thing. GPLv3 explicitly allows you to decline to license your trademarks (see section 7, the paragraph starting "Notwithstanding any other provision of this License", clause e). This isn't generally c…
The term sheet seems to show Automattic did precisely that (violated section 4 of the GPL license by trying to get someone to give up their GPL right to fork), ergo Automattic should lose their own GPL rights, including to parts of Wordpress. Trademarks don't factor in here.
Earlier quoted context omitted.
> in some of its microsites Exactly. That's not a large scale enterprise CMS. WordPress is fine for that. But if you wanted to do something that requires fine-grained access control, publishing control, audit logs etc, you're not going to use WP, or you're building a CMS on top of WP. I'm doing that all day because I work in an industry that loves WP and everybody knows WP, so it's easy to collaborate. I've built doz…
I guess I don't really understand what you consider "large" or "enterprise" there are very large sites that use Wordpress. I just gave you enterprise level consumers using it. You obviously aren't going to use it to build the next eBay or Amazon, but if you're a publisher or need a CMS that does publishing well? I don't really see your issue with it, if it's the right fit. Too many people try to reinvent the wheel. I…
When I hear "large enterprise CMS", I don't hear "a CMS that can be used by large enterprises" (because everything could, even if it's based on manually editing HTML files), I hear "a CMS suited to be used in large environments with complex requirements and no room for error".
"Enterprise" as an adjective is something that is tailored to the needs of very large entities that, due to the nature of their size, activities and legal environment, have very complex needs, and who also need to deal with things that normal website owners rarely do: legal compliance, different threat levels, audit-logs, fine-grained access privileges, publishing workflows etc.
WordPress isn't the right fit for that. WordPress isn't, and doesn't claim to be, an Enterprise CMS or targeting very large installations. Similarly: while you can manage data in WordPress, if someone suggested building a banking system on top of WordPress, I'd shake my head just the same. But that doesn't mean you can't set up a few post types and add some fields with ACF and have something you can use to organize and document your gardening efforts. They are just _very_ different requirements, and WP doesn't meet (and doesn't aim to meet) those that you associate with "enterprise" (adjective).
Like I said, I don't hate WP, I use it all the time and I know it very well. And for the vast majority of the internet, it's perfectly fine and usually the right choice because it guarantees that you'll always find somebody who can take over maintenance for your project, you'll find plenty of editors that are already familiar with your system, and there's a bajillion themes you can use and be done with it.
But if you need much more than that, you really shouldn't be using WP. Yes, you can (and I do), but you will build so much custom logic on top of it and wrestle it into behaving appropriately, that you'd be better off just not using WP. But 99% of WP sites never hit that ceiling, so for them WP is a fine choice.
Earlier quoted context omitted.
WordPress is GPLv2-or-later. GPLv2 is silent on the subject of trademarks, and is a bit vague about additional restrictions -- section 4 would apply to trying to restrict usage of the code, but trademarks are a separate thing. GPLv3 explicitly allows you to decline to license your trademarks (see section 7, the paragraph starting "Notwithstanding any other provision of this License", clause e). This isn't generally c…
Trademarks are a red herring here. What the GPL says is that if Automattic attempts to get someone to give up their GPL rights (e.g. the right to fork) , then Automattic automatically loses their own GPL rights as punishment for the attempt. This is the section 4 you speak of. Specifically, Automattic cannot offer terms that say "in exchange for trademark stuff (or anything else), you agree to give up your GPL rights…
Earlier quoted context omitted.
Just wait!
I’m with you Matt! I like your strategy here.
> A static site that is 100% free and open-source, competing with several businesses operating scammy subscription models.
https://news.ycombinator.com/item?id=30295629
Is this a competitor to Wordpress? Can you elaborate more about how the competition in this space uses scammy subscription models? It might help to illustrate the issues in the industry for outsiders like me.
Off topic, but I'm a bit of an amateur musician myself. I try to check out other musicians that I encounter, but I wasn't able to find anything about you or your music online. Do you have a bandcamp or something similar? The contrabass trombone is a really interesting instrument.