Changes for page Collective Ownership

Last modified by chrisby on 2024/02/27 16:05

From version 1.13

edited by chrisby
on 2023/12/28 12:20

Change comment: There is no comment for this version

To version 1.14

edited by chrisby
on 2024/01/13 17:46

Change comment: There is no comment for this version

Summary

Page properties

Content

@@ -4,7 +4,9 @@
  * **Improved Team Unity**: Collective ownership eliminates factions and hierarchy through equal access rights to the code.
  * **Reduces Duplication**: Shared logic between different modules in the project through shared access.
--* **No Bureaucratic Hurdles**: Not having to ask and wait for permission to apply constructive code changes saves time.
++* **No Bureaucratic Hurdles**: Not having to ask and wait for permission to apply constructive code changes saves time. In teams where there is no collective ownership, it is not uncommon for reasonable improvements to even be blocked.
++* **Module Responsibility**: If may make sense to have people responsible for specific modules, but they should only monitor changes, not block them.
++* **For big code bases, collective ownership may go across teams** like in an open source project, but company internal. Other teams create MR's and the team responsible has to approve it.
  ### Specialization vs Generalization