I was recently thinking about the following. According to the open / close principle, once a piece of code X has been implemented and tested, it should not be modified any more.
X can still be replaced by another piece of code implementing the same interface (maybe with a better implementation), or new functions and methods can be added to it. But the part that is already implemented and (thoroughly) tested should now work as a black box that can be invoked from the outside but should not be modified any more.
So, if the open / close principle is implemented correctly, shared code ownership should not be so important anymore because no one will need to modify a finished, self-contained piece of code. This seems quite natural to me but I haven't heard of this idea before. Is there any literature or school proposing this thesis: open / close principle makes shared code ownership less important?