Code ownership is an important concept in software development practices, and many developer portals now have a field where they require every project to have a “code owner”. But problems arise when everyone has a different definition of what being a code owner means. Not knowing who the owner is can cause confusion and friction in projects that are being collaboratively developed across organizations. Questions that need answers are: Who is making architecture decisions for this project? Whose budget pays for this feature enhancement? Who do I call at 2am if the project is down? Who should get the credit for that amazing feature enhancement, achieved through a code contribution from another team? Each case can be a different way of looking at code ownership. This talk will examine what we mean when we talk about a “code owner” and will cover some of the many problems that inconsistent definitions within an organization can result in when you are trying to collaborate on code.