Darya Akbari wrote:A class usually belongs to one owner, the one who created that class and gave birth to it.
I rarely see that in the workplace. I am more used to an individual writing the class and doing any initial modifications needed with it, after which time it can get worked on by anyone else within the organization (although often it is only those within an individual team who do modifications).
The rare occasions I have seen the code base staying with the original creator is when there are not enough
unit tests and/or the original author has obfuscated the code (whether deliberately or not). In such cases other developers are often afraid of changing code that they don't own as they are afraid of what they might break. That single author can then become a bottleneck for the entire company - a really bad idea.
Personally I cant see why any company would want to have a single person "own" a class: what happens if that person ever leaves that company (as if that would ever happen!)? Or go on vacation or get sick? It just makes sense to have many people capable of adding features and supporting the code base.
Likewise I can see no reason why a developer would want to be in a position where they "own" classes for as long as they work at a company - talk about career limiting! How on earth could I ever move onto new and exciting projects when I must always own any code I have previously written?
Back to the original issue - I believe, as Ernest & Bear have indicated they believe, that meta data belongs in the code repository for any internal projects.