Code ownership
 | This article is actively undergoing a major edit for a little while. To help avoid edit conflicts, please do not edit this page while this message is displayed. This page was last edited at 00:06, 5 November 2024 (UTC) (7 months ago) – this estimate is cached, . Please remove this template if this page hasn't been edited for a significant time. If you are the editor who added this template, please be sure to remove it or replace it with {{Under construction}} between editing sessions. |
In software engineering, code ownership is a term used to describe control of an individual software developer or a development team over source code modifications of a module or a product.[1]
Definitions
Authorship
Some researchers also use the term to describe the authorship of software (identifying who wrote a particular line of software). Koana et al. (2024) state that this is a different, although related, meaning, as the code owner might not be original author of the software piece.[2]
References
- ^ Metiu 2006, p. 424.
- ^ Koana et al. 2024, p. 8.
Sources
- Koana, Umme Ayman; Le, Quang Hy; Rahman, Shadikur; Carlson, Chris; Chew, Francis; Nayebi, Maleknaz (2024-09-27). "Examining ownership models in software teams". Empirical Software Engineering. 29 (6). Springer Science and Business Media LLC. arXiv:2405.15665. doi:10.1007/s10664-024-10538-5. ISSN 1382-3256.
- Metiu, Anca (2006). "Owning the Code: Status Closure in Distributed Groups". Organization Science. 17 (4). INFORMS: 418–435. ISSN 1047-7039. JSTOR 25146047. Retrieved 2024-11-04.
 | This software-engineering-related article is a stub. You can help Wikipedia by expanding it. |