feat: Added LGPL as a valid license.

[jhdub23]

No description provided.

[RobPasMue]

LGPL cannot be accepted as a license by default - investigations need to be performed on the way the impacted package is used on our side.

[jgd10]

The ability to release Python libraries freely but NOT as fully OSS (aka Freeware) is desirable and there is at least one library that falls into this category at the moment within ansys and there could be more in the future.

[jhdub23]

Under what circumstances would an LGPL package X be permissible while an LGPL package Y be denied? For example: GPL - internal use only, allowed. Shipped within a closed-source product: not allowed.

I'm trying to understand the decision factors that would apply for us to deny the use of an LGPL package. I can't think of any, assuming the product team has ok'd the use of the package.

[jorgepiloto]

As far as I am concerned:

• We allow the use of free software for development
• We don't allow free software dependencies in our projects

The reason for the last point is that we would be force to distribute our software under a free software license.

[ansys-cla-bot]

CLA Check Failed: Commit Author Verification Unsuccessful

One or more commits in this pull request contain missing or invalid author information. This issue may arise due to:

• A change in the contributor’s GitHub username
• Deletion of the contributor’s GitHub account
• Corruption or alteration of commit author metadata

Please update the commit author details and push the updated commit to proceed with the CLA verification.

[jhdub23]

As far as I am concerned:

• We allow the use of free software for development
• We don't allow free software dependencies in our projects

The reason for the last point is that we would be force to distribute our software under a free software license.

LGPL packages don't force us to distribute our software under a free software license. Also, software in the ansys org is already distributed as free; every repository has an MIT or equivalent license. That does NOT extent to components it uses (e.g. our proprietary code).