{"title":"谁拥有这些代码?检查内部源实践中的所有权概念","authors":"Clare Dillon","doi":"10.1109/innersoft59330.2023.00009","DOIUrl":null,"url":null,"abstract":"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 InnerSource projects. 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 an InnerSource contribution? Each case can be a different way of looking at code ownership. This lightning 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 for your InnerSource practice.","PeriodicalId":216607,"journal":{"name":"2023 IEEE/ACM 1st International Workshop on InnerSource Software Development (InnerSoft)","volume":"1 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2023-05-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"0","resultStr":"{\"title\":\"Who owns this code? Examining Ownership Concepts in InnerSource Practices\",\"authors\":\"Clare Dillon\",\"doi\":\"10.1109/innersoft59330.2023.00009\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"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 InnerSource projects. 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 an InnerSource contribution? Each case can be a different way of looking at code ownership. This lightning 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 for your InnerSource practice.\",\"PeriodicalId\":216607,\"journal\":{\"name\":\"2023 IEEE/ACM 1st International Workshop on InnerSource Software Development (InnerSoft)\",\"volume\":\"1 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"2023-05-01\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"0\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"2023 IEEE/ACM 1st International Workshop on InnerSource Software Development (InnerSoft)\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1109/innersoft59330.2023.00009\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"2023 IEEE/ACM 1st International Workshop on InnerSource Software Development (InnerSoft)","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/innersoft59330.2023.00009","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
Who owns this code? Examining Ownership Concepts in InnerSource Practices
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 InnerSource projects. 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 an InnerSource contribution? Each case can be a different way of looking at code ownership. This lightning 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 for your InnerSource practice.