Comment by CharlesW
2 years ago
When I posted, I was under the impression that ACF was open source. But the GitHub repo doesn’t list one, so if it’s not open source…WTF.
2 years ago
When I posted, I was under the impression that ACF was open source. But the GitHub repo doesn’t list one, so if it’s not open source…WTF.
Forking isn't the issue. Here they just took the whole ID/address from which existing installations will continue to be updated from. This is theft. I have no doubt it will be added to the lawsuit.
While technically they own the platform and can do whatever they want, there is clearly ill intent here and it'll be used against them.
I think being GPL is a requirement to host plugins in wp.org, so yes, that free version available there is (was?) open source.
> When I posted, I was under the impression that ACF was open source. But the GitHub repo doesn’t list one, so if it’s not open source…WTF.
Isn't it here?
https://github.com/AdvancedCustomFields/acf
If you mean the licence, it's in readme.txt:
https://github.com/AdvancedCustomFields/acf/blob/master/read...
Thanks! The GitHub app reports it as "None" (https://imgur.com/a/5dyaTfX), but now I see it's "GPLv2 or later".
Clearly AdvancedCustomFields should have filed a trademark to prohibit Wordpress from fully stealing it.
GPL code, trademarked branding. If you want to fork then you have to actually fork.
Oh the irony.
> Clearly AdvancedCustomFields should have filed a trademark to prohibit Wordpress from fully stealing it.
They did:
Advanced Custom Fields — https://tsdr.uspto.gov/#caseNumber=98321164&caseSearchType=U...
ACF — https://tsdr.uspto.gov/#caseNumber=98321135&caseSearchType=U...
5 replies →