Are Block/ FSE theme CSS files exempt from GPL?

Everything hosted here on www.ads-software.com is GPL compatible. No exceptions.

With the advent of the Block/Site Editor, design tokens, official asset building, and all the other changes to WordPress, I am wondering if the above exemption still applies.

That still applies but all code hosted on www.ads-software.com needs to be GPL compatible. That includes block/FSE themes as well.

Thanks @otto42 and @jdembowski for the quick replies!

I am aware of the .org requirements, just requesting clarification about the actually GPL applicability for themes distributed publicly outside of the the respective directories.

@jdembowski does that exception only apply to standalone CSS or also those which use one of WP’s build tools to compile them (the practical implication being whether a theme would be required by GPL to make the src files available)?

Also, does that mean that .html files are also not automatically covered by the GPL (since GB comments are ignored similarly to design tokens)? And where does theme.json or block.json files fit in?

@justlevine To sort out questions like that, you would need to consult a qualified attorney. We are not such.

Basically, these are questions of law, not of code.

@otto42 let me perhaps ask in another way: Has .org or leadership provided any direction or guidance on GPL in themes either in direct relation to block themes/ FSE or even just chronologically after 5.0 fundamentally changed how WordPress uses non-PHP assets?

I’m asking from an ecosystem/docs perspective, not looking for legal advice on a specific product. As a champion of GPL, I’m finding it puzzling that all the official WP guidance I can find is extremely outdated (such as the referenced link in my OP) even though I’m sure these conversations must have happened some time over the last 4+ years.

• This reply was modified 1 year, 4 months ago by David Levine.

@justlevine No, no such direction or guidance has been given. You have to understand that we’re not really interested in that sort of thing. WordPress is a volunteer, open source project.

Our recommendation is that you use the GPL or GPL compatible licensing for all things. We believe in open source. We use it ourselves. We also require it for everything we host.

If you need more advice than that, you should speak to a lawyer. Our recommendation is that you use open source licensing and open source products.

Thanks @otto42 .

I can’t help shake the feeling that we’re talking on different wavelengths, and you’re trying to convince me to apply the GPL to my own code, when that’s not my motivation and I’m coming from the opposite direction. Of course WordPress should encourage open source and the correct – or even minimal – adherence to the GPL. The fact that there’s significantly more than a handful of docs (albeit outdated) describing the importance and application of GPL to distributed code attests to that interest. The fact that all hosted code on .org must be GPL (as you keep repeating) is similar testament.

As such, the fact that there’s a significant uptick in premium WordPress block themes and plugins potentially not adhering to the GPL – whether intentionally or out of ignorance due to outdated official recommendations – should indeed be of interest. Such as when they only release their compiled JS (despite using WordPress libraries) or possibly CSS. These actors anecdotally includes several premium offerings who’s (compliant) free versions are hosted on .org.

Regardless, I appreciate your answer to my question about the *existence* of up-to-date resources on the topic, and I’ll go ahead and open a ticket requesting a refresh with the docs team.

(the resolve checkbox isn’t working from my mobile, but feel free to close this ??)

• This reply was modified 1 year, 4 months ago by David Levine.