How to Keep an Open Source Register — and Why Buyers Ask for One

Maintain a register of all open-source licenses and dependencies used in your product so you can disclose them to potential buyers.

Maintained in the open at github.com/Golden-Section-Tx/playbook · CC BY-SA 4.0

PlayersCTO
Initial Effort3 SP
Ongoing3 SP
FrequencyQuarterly
StagePre-Revenue

Much like your English professor wanted to see a Works Cited page, potential buyers will want to see all the open-source material your code uses disclosed.

The goal: Create a simple register of all open-source licenses used and dependencies.

Steps:

  1. Task a member of your dev team with identifying all open-source licenses and dependencies used.
  2. Fill in the appropriate information on the template provided.

Questions this play answers

What open-source licenses am I using?

Much like your English professor wanted to see a Works Cited page, potential buyers will want to see all the open-source material your code uses disclosed.

Why do buyers ask for an open-source register?

Much like your English professor wanted to see a Works Cited page, potential buyers will want to see all the open-source material your code uses disclosed.

How do I create an open-source register?

Much like your English professor wanted to see a Works Cited page, potential buyers will want to see all the open-source material your code uses disclosed.