Doing the open source thingy

This document discusses open source and provides guidance on how to do open source. It explains what open source is, why developers should consider it, and how to structure an open source project. Key steps include identifying the scope of the project, abstracting the code, choosing an open source license, standardizing build processes, documenting code, ensuring quality through testing and CI/CD, and making the project visible to gain contributors. The overall message is that going open source allows for improved quality and quantity of code through community involvement, but it shouldn't be forced if it isn't a good fit.