3 ms·

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.

ValentineC 2y 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. Isn't it here? https://github.com/AdvancedCustomFields/acf https://github.com/AdvancedCustomFields/acf If you mean the licence, it's in readme.txt: https://github.com/AdvancedCustomFields/acf/blob/master/readme.txt https://github.com/AdvancedCustomFields/acf/blob/master/read...
- CharlesW 2y ago
  Thanks! The GitHub app reports it as "None" (https://imgur.com/a/5dyaTfX https://imgur.com/a/5dyaTfX), but now I see it's "GPLv2 or later".
- forrestthewoods 2y ago
  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.
  - ValentineC 2y ago
    > 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=US_APPLICATION&caseType=DEFAULT&searchType=statusSearch https://tsdr.uspto.gov/#caseNumber=98321164&caseSearchType=U... ACF — https://tsdr.uspto.gov/#caseNumber=98321135&caseSearchType=US_APPLICATION&caseType=DEFAULT&searchType=statusSearch https://tsdr.uspto.gov/#caseNumber=98321135&caseSearchType=U...
    - forrestthewoods 2y ago
      Oh nice. Then WordPress shouldn’t be able to take over without renaming, right?
      - prettymuchnoone 2y ago
        they renamed to "secure custom fields"
        everforward 2y ago
        They kept the permalink afaik, which is probably still likely to cause confusion in the marketplace and may still be a trademark issue. Without knowing this drama, if I found and clicked an ACF link on a 2 year old Reddit post and ended up at Secure Custom Fields, I’m not sure I’d know it wasn’t by the ACF folks. Just their branding for the v2 or whatever. I think customers have a reasonable expectation that permalinks won’t take them to unrelated products.
        mthoms 2y ago
        Yep. And the string 'acf' is used throughout the plugin and the plugin download page (in reviews, etc). And 'acf' is indeed a pending trademark registration. Not good.
        saaaaaam 2y ago
        Very much doubt they will be able to trademark “acf”.
danillonunes 2y ago
I think being GPL is a requirement to host plugins in wp.org, so yes, that free version available there is (was?) open source.
sureIy 2y ago
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.

ValentineC 2y 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. Isn't it here? https://github.com/AdvancedCustomFields/acf https://github.com/AdvancedCustomFields/acf If you mean the licence, it's in readme.txt: https://github.com/AdvancedCustomFields/acf/blob/master/readme.txt https://github.com/AdvancedCustomFields/acf/blob/master/read...

CharlesW 2y ago
Thanks! The GitHub app reports it as "None" (https://imgur.com/a/5dyaTfX https://imgur.com/a/5dyaTfX), but now I see it's "GPLv2 or later".
forrestthewoods 2y ago
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.
- ValentineC 2y ago
  > 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=US_APPLICATION&caseType=DEFAULT&searchType=statusSearch https://tsdr.uspto.gov/#caseNumber=98321164&caseSearchType=U... ACF — https://tsdr.uspto.gov/#caseNumber=98321135&caseSearchType=US_APPLICATION&caseType=DEFAULT&searchType=statusSearch https://tsdr.uspto.gov/#caseNumber=98321135&caseSearchType=U...
  - forrestthewoods 2y ago
    Oh nice. Then WordPress shouldn’t be able to take over without renaming, right?
    - prettymuchnoone 2y ago
      they renamed to "secure custom fields"
      - everforward 2y ago
        They kept the permalink afaik, which is probably still likely to cause confusion in the marketplace and may still be a trademark issue. Without knowing this drama, if I found and clicked an ACF link on a 2 year old Reddit post and ended up at Secure Custom Fields, I’m not sure I’d know it wasn’t by the ACF folks. Just their branding for the v2 or whatever. I think customers have a reasonable expectation that permalinks won’t take them to unrelated products.
        mthoms 2y ago
        Yep. And the string 'acf' is used throughout the plugin and the plugin download page (in reviews, etc). And 'acf' is indeed a pending trademark registration. Not good.
        saaaaaam 2y ago
        Very much doubt they will be able to trademark “acf”.

danillonunes 2y ago

I think being GPL is a requirement to host plugins in wp.org, so yes, that free version available there is (was?) open source.

sureIy 2y ago

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.