¹ú²úÊÓƵ

A series of guides recommended by the United States General Services Administration that introduce readers to the open source development model.

A short introduction to the various types of open source licenses, including the history of OSS licenses and the differences between permissive and copyleft licenses.

A brief article about improving the security, effectiveness, and reusability of code.

Resource that delves into the difference between OSS and open standards. This tool also discusses benefits such as readily-available software, saving time and resources to solve common challenges, lower implementation and running costs, and the ability to integrate with closed-source software.

Explains OSS economics, describes a historical description of the rise of OSS and its contrast with traditional proprietary software.

Blog post from the Canadian Digital Service (CDS) that describes the benefits of open source, the approach taken by the CDS, and an FAQ about security, personally identifiable information, and what to not open.

Nine reasons why the United Kingdom’s Government Digital Service recommends coding in the open.

Identifies common challenges with collaborative software development and its use in government, including misconceptions and questions about open source and policies that obstruct OSS development.

Long-form FAQ from the DoD about OSS, licensing, security, and its development, use, and release by the U.S. government.

The Alliance hosts a platform that aids organizations in discovering openly-licensed technologies, data models, and other resources that can be deployed to support the sustainable development goals (SDGs).

A set of resources to help open source developers who are responsible for maintaining a software project, including clearly communicating project expectations, mastering documentation, and empowering contributors to find solutions to shared challenges.

Summarizes the grounds for keeping code closed and why other code should be open.

A set of simple suggestions if government offices want to open previously proprietary code.

Guidance from the United Kingdom’s Government Digital Services about security and open source software.

Advice on how to assess security risks of a government program, including performing access audits, building risk mitigation plans, and fostering a culture of constant monitoring and improvement.

A report by the Linux Foundation presenting the initial findings of a census assessing the scope of open source software used in programs and infrastructure within the private and public sectors.

The United Kingdom Government Digital Service provides guidance on the different situations in which it is most secure to keep source code closed to the public versus when it is safe to offer it openly.

GitHub’s high-level primer for legal teams to understand the legal implications of open source.