You've got a useful project you'd like to open source, but you're not sure all the steps you should take. What if someone wants to report a bug? Send a code change? Report a security issue? So many processes to set up! This session will walk you through the key behaviors, documentation, and tooling you'll want to set up to make that project shine:

* Documentation: prioritizing the key getting-started and how-does-this-work areas within your always-limited docs time budget
* Issue and pull request templates: helping users provide reports and in ways you can actually work with
* Tooling: setting up a formatter, linter, test harness, and other nifty tools to ease the costs of both contributing and reviewing code and docs changes
* Paperwork: finding the right CLA, licensing, and security terms for your company/individual and project types
* Politics: explaining why open source is worth it to internal stakeholders

By the end of this session, you'll be ready to confidently dip your toes into open source. Or dive right in.