Let the cat out of the bag (Successfully open source your code and documentation)

In this section, we’ll discuss different methods and approaches to open sourcing your materials, from the bare minimum to standard and formal approaches. By the end, you should have a good idea of your options and the benefits of each one.

Each of the options listed in this section share some common assumptions. Chief among those assumptions is that each repository should explicitly call out (meaning, draw attention to or otherwise direct the reader to) the main or default license. Do not make code available publicly without specifying a software license. Other assumptions are that each repository lists the maintainers, contributors, security reporting process, ways to contribute, and adopters. Finally, each repository should contain a README file (meaning, a file literally named “README” that contains information that should be consulted first) and a pointer to any other documentation...