openrelationship.io github.com/OpenRelationship

This is Open Relationship __01 a podcast by Shane and Kelly, engaged and building things together.

read the README

OpenRelationship / README.mdShane & Kelly
fig. 1, the kitchen table

The arrangement

We're engaged, and we build products together. Most weeks those turn out to be the same conversation, so we started recording it. 🎙️

Every episode covers three things: how the two of us are doing, how the work is going, and what we shipped since the last one. Some weeks the third part is short. We'll say so.

It's a show for people who are building something with someone they love, or thinking about it, or just curious how that goes when you do it with the mics on.

1Two voices, one table, no guests for now. Episodes land here and wherever you get podcasts.

fig. 2, door left open

The terms

The name is a joke, and also the whole policy. Here is what open means for us:

  1. Anything we build for ourselves gets a public repo. 🔓
  2. Small things ship first: templates, tools, the agent skills we use every day. Bigger products follow when they're ready to be seen.
  3. We share the numbers, including the ones that don't flatter us. 📉
  4. You can fork any of it. Each repo carries its own license.
That's the arrangement. Nobody is signing anything.

2This page counts too. It's one HTML file in a public repo, so view source if you're curious how the drawings work.

fig. 3, carrying the load

Repos

Everything lives under github.com/OpenRelationship, one repo per project.

  • 📦 monomono
    A template for starting monorepos. You get the folder layout, the build graph, and the development process (how work goes from ticket to release) already wired up, so a new project starts with structure instead of a blank folder.
  • 🧅 yumonion
    A grocery app. Scan what's in your cart, see what it costs at the stores near you, and see how it rates against published nutrition standards.
  • 🧰 skills
    The agent skills we lean on day to day, collected in one place so you can install them yourself.

3Why not one big monorepo? These projects don't share code. Separate repos are easier to fork, easier to star, and easier to hand to someone else.

4If one of these is useful to you, a star is the cheapest way to tell us. We read every issue.

fig. 4, hello

Follow along

Episode 001 is being recorded. Until it's out, the repos are the best place to watch. 👀

$ git clone https://github.com/OpenRelationship/monomono
$ open https://openrelationship.io

Episode 001 🎙️ is cominnnng sooon follow along github