How GitHub gave every repository a durable owner

How GitHub gave every repository a durable owner(github.blog)

18 points by ascertain 4 hours ago | 5 comments

simonw 3 hours ago |

A previous employer hit the problem where there were a ton of legacy features that didn't have clear owners and so it wasn't clear where to route bug reports.

Their solution was to build a catalog of every feature and then assign EVERY one of them to an existing team.

Teams might end up responsible for features that they had never seen before and had no knowledge of... but that was fine, because every other team was in the same situation.

It worked great. Bugs got fixed. Teams figured it out.

hilariously 3 hours ago | |

The truth is that accountability isn't the problem, its the lack of resources, prioritization, and ability to change things that make them burdensome. After a certain point you're just trying to solve the problem in the least annoying way possible.

MeetingsBrowser 3 hours ago | |

It’s like the bystander effect but for code, lol.

Just pick someone and give them the task.