Scott K Peterson authored content

Authored content by Scott K Peterson

Shipping containers stacked in a yard

When software is distributed via container images, source code should be made available in order to ensure seamless compliance with licensing.
a magnifying glass looking at a brain illustration

Open source licensing is different for good reasons that support the collaborative development that makes open source so great.
a magnifying glass looking at a brain illustration

The difference has consequences for how we structure the development process.

Although forking is undesirable, the potential for forking provides a discipline that drives people to find a way forward that works for everyone.
A diagram of a branching process

The implications of distributing software through container images are quite different from those of the package managers many people are familiar with.
a magnifying glass looking at a brain illustration

Conventional wisdom says the Apache License has a "real" patent license. But what about the MIT License?
patent document with lights shining on it

For open source software, license information is embedded in the source code. To reduce complexity, you can generate different views.
Green open envelope with Open overlay

Free software, open source software, FOSS, FLOSS. Are they the same? Different? Does it matter?
sticky notes making a palm tree on an island

Open source licenses give the permission necessary to remove the restrictions created by copyright law.
mozilla public license illustration

Licenses are valuable shared resources. What might we do to support these shared resources?