Who owns this code? Examining Ownership Concepts in InnerSource Practices

Clare Dillon
{"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}
引用次数: 0

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.
谁拥有这些代码?检查内部源实践中的所有权概念
代码所有权是软件开发实践中的一个重要概念,现在许多开发人员门户都有一个领域,要求每个项目都有一个“代码所有者”。但是,当每个人对代码所有者的含义有不同的定义时,问题就出现了。不知道所有者是谁可能会在InnerSource项目中造成混乱和摩擦。需要回答的问题是:谁在为这个项目做架构决策?谁的预算为这个功能增强买单?如果项目在凌晨2点停止,我该给谁打电话?谁应该获得通过InnerSource贡献实现的惊人功能增强的荣誉?每种情况都可以用不同的方式来看待代码所有权。这个简短的演讲将检查我们所说的“代码所有者”是什么意思,并将涵盖组织中不一致的定义可能导致的InnerSource实践中的一些问题。
本文章由计算机程序翻译,如有差异,请以英文原文为准。
求助全文
约1分钟内获得全文 求助全文
来源期刊
自引率
0.00%
发文量
0
×
引用
GB/T 7714-2015
复制
MLA
复制
APA
复制
导出至
BibTeX EndNote RefMan NoteFirst NoteExpress
×
提示
您的信息不完整,为了账户安全,请先补充。
现在去补充
×
提示
您因"违规操作"
具体请查看互助需知
我知道了
×
提示
确定
请完成安全验证×
copy
已复制链接
快去分享给好友吧!
我知道了
右上角分享
点击右上角分享
0
联系我们:info@booksci.cn Book学术提供免费学术资源搜索服务,方便国内外学者检索中英文文献。致力于提供最便捷和优质的服务体验。 Copyright © 2023 布克学术 All rights reserved.
京ICP备2023020795号-1
ghs 京公网安备 11010802042870号
Book学术文献互助
Book学术文献互助群
群 号:604180095
Book学术官方微信