Permissive open source license

As explained in Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform

A permissive open source license allows code to be used, modified, and distributed with relatively few conditions, typically including preservation of license and copyright notices.

A permissive open source license allows code to be forked, modified, and distributed when users preserve the license and original copyright notice. It generally does not require modified code to be released publicly. section 13.1.3 section 13.5

Assessing an MIT-licensed module

A team evaluating a database module asks legal specialists to review its MIT license. Approval permits the team to modify or maintain a fork without publicly releasing its changes, provided it retains the license and copyright notice. section 13.1.3

Before adopting a permissively licensed infrastructure module:

• Confirm that the license and original copyright notice remain with forks or modifications. section 13.1.3
• Ask legal specialists to assess organizational risk and distinguish permissive terms from copyleft release obligations. section 13.1.3 section 13.5

Figure 13.4 Decision flow for assessing usage of a module or tool based on tool or module life cycle

Use the decision flow to assess a module or tool’s lifecycle, maintainership, testing, and license before adoption. section 13.1.3

How Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform covers it

How deep it goes

Defines preservation obligations, contrasts copyleft requirements, and stops short of detailed license interpretation.

Examples

Uses an MIT-licensed database module, forks, modifications, copyright notices, and legal approval as concrete examples.

What it assumes

Assumes familiarity with infrastructure modules and teaches the distinction between permissive and copyleft obligations.

What you can do after

Evaluate whether an open source infrastructure module can be adopted, modified, or maintained internally.

How it connects

Connects license choice with copyleft licenses, infrastructure as code, legal review, and supply-chain security.

liveBookmanning.com

Read Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform on liveBook Get the book at manning.com

Related concepts

• licensekind of · A license is a legal grant of permission to use, access, modify, copy, distribute, or perform an asset or activity under specified terms and conditions.
• copyleft open source licensecontrasts with · A copyleft open-source license permits use and modification of covered work while requiring distributed derivative works to preserve specified open licensing terms and freedoms.
• open sourceused by · Open-source software is software whose source code is available under a license permitting use, study, modification, and redistribution.
• training datasetconfigures · A collection of examples or observations supplied to a learning procedure to fit or adapt a model or learn its patterns or parameters.

This explainer was generated by Manning's knowledge graph from the text of Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform. The section links point to the parts of the book it draws on.