Read

An introduction written by Brad Frost, author of Atomic Design. Brad associates open source and the web as foundational collaborative works of people. Regular people. He highlights part of Brian's journey where they met on the Pattern Lab open source project, and what we can learn from that brief period of time, still resonant today.

A conceptual understanding of open source's origins and strictest definitions. Can it be more? We glance at the interconnectedness of our communities, and hint at the parts we can play in them.

An exploration of all the ways we can engage with open source projects. This ain't a mountain to climb though, we can each bring our unique skillsets and interests to any project. I promise, you have something unique to offer.

A deeper dive into dependencies as a double-edged sword. We cannot help but use them, and therefore they must be wielded with care. How can we evaluate the need for a dependency beyond GitHub stars and download counts. And what if we don't need a dependency at all?

We frame every open source project against four files. I won't keep you in suspense. I prioritize the README, LICENSE, CHANGELOG, and CODE_OF_CONDUCT files. We cover an array of conceptual and technical topics, and get real real when talking about licenses.

Overwhelmed yet? That's how it can be. This chapter highlights ways you can invest further in your project as an investment in yourself and others. Time is our critical resource, so we cover impactful decisions and automation. Be wary to steer your community where you want it to go.

You don't need permission to do your job. Engaging with open source is already the norm, because you consume it. This chapter highlights ways you can energize yourself, your team, and your company to give more of a damn. I am not kidding, and I offer practical advice to make it happen. Open source is the tangible manifestation of larger craftsmanship and community values.

You cannot take care of someone else if you aren't taking care of yourself. This is sustainability on a personal and systemic level. How do we deal with disappointment, burnout, and the inevitable desire to walk away? Let's frame our work against broader timescales, and remember why this matters.

If you made it this far, you have my thanks and now my challenge.

Tools mentioned in the book or otherwise hinted at.

A small thanks.

Links and references for further reading and exploration.