Skip to content

Increase clarity in NonFreeAssets policy

Sylvia van Os requested to merge NonFreeAssetsClarity into master

Fixes !936 (merged) and later changes properly by:

  1. Using the word "restricting" to make clear that the problem is restrictions on commercial usage
  2. Explicitly name very common licenses that would be marked as NonFreeAssets
  3. Avoids using terms like "commercial license" (which is a term coined by companies distributing proprietary software to brand FLOSS as "unsafe for commercial usage" which is untrue)

I hope this solves everyone's concerns with the previous version.

Ping @licaon-kter @simonpoole @obfusk

Merge request reports