Pro License for open source project

[erdalkaraca]

Can I use the pro license for an open source project?

[claviska]

No, sorry. The pro license doesn't work for open source projects since it doesn't allow redistribution. When you put something on GitHub or any public repo, you're redistributing it, which breaks the pro license's terms.

The good news is Web Awesome Free is MIT licensed, so you can absolutely use and redistribute that part in your open source projects! The pro license is just for when you need the premium features in private/commercial projects where the code stays internal.

Hope that helps clarify things!

[erdalkaraca]

i am using width and height 100% everywhere :-)

[erdalkaraca]

So, how to use wa-page for open source projects?

[claviska]

Since <wa-page> is part of Web Awesome Pro, you can't use it and redistribute it as part of your open source project.

To be clear, you can use it, e.g. to build a website to promote an open source project, as long as the website itself isn't open source or redistributed.

[erdalkaraca]

I am not sure how the pro license key is handled as it is not mentioned in the docs: is the key embedded in the app/website in plain text? If it is somehow encrypted and verified, I could store my pro license as a CI/CD secret and "apply" it to the built app. So, the key itself would not be redistributed. In my case, there is only one official instance of the app served from the public internet. If others want to host their own instance of the web app, they would have to acquire their own license.

[claviska]

The pro CDN is configured to only allow requests from domains that you allow and are linked to your Project Token. (This is how Font Awesome's CDN works...theirs are called Kits.)

That said, it is possible to ship a project with, for example, the <wa-page> HTML tag inside your code and serve the Pro components via CDN — as long as no Web Awesome Pro code is being distributed with it. However, this creates an upstream dependency for all of your users who, if they don't have a Web Awesome Project Token, won't get access to any of the pro features and might think things are broken.

[cptspff]

Well, until recently, wa-page was available in the public MIT-licensed repository. Since it was always labeled as 'pro' on the webpage, I assume this was an oversight and have already migrated away from it. I'm just hoping this won't happen with other components as well in the future.

[claviska]

It was erroneously included in the free repo due to a build script issue with our new monorepo. The <wa-page> component is and always has been pro as the website and Kickstarter indicated.

I apologies for the confusion. That was on us and we should have noticed that sooner.