“计算”使用 TFS SDK 2010 的代码所有权索引
我最近想到的一个想法需要你的帮助。
用 TFS 术语来说，我试图提出一个公式，可以确定某些源代码控制文件的所有权索引（即谁是对该文件最负责的开发人员）。
这就是为什么我正在寻找可用于计算此所有权指数的标准。到目前为止，我想到的唯一可行的办法就是对签到次数进行求和，但这个标准似乎很可疑。另一个标准是对每个开发人员签入的所有代码行进行求和，但是 1) 我不确定 TFS SDK 2010 和 2) 文档行是否可行应该被跳过。
所以，我想我的问题是：
上述标准（签入数量 + 代码行数）是否足以计算所有权指数，或者我还需要其他条件吗？
I need your help on an idea that came to my mind recently.
Speaking in TFS terms, I am trying to come up with a formula that can determine the ownership index for some source-controlled file (i.e. who is the developer most responsible for that file).
That's why I'm looking for criteria I can use to calculate this ownership index. So far, the only feasible thing that comes to my mind is to sum the number of check ins, but this criterion seems fishy. Another criterion is to sum all the lines of code each developer has checked in, however 1) I am not sure if it is possible with TFS SDK 2010 and 2) Documentation lines should be skipped.
So, my question, I guess, is:
Are the above criteria (number of checkins + lines of code) sufficient to calculate an ownership index or do I need something else?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
我参与过许多软件转让项目，其中一个团队将源代码移交给另一个团队。在这种情况下，识别给定源文件/软件组件的真正专家是至关重要。
因此，我惨痛地认识到，作为看门人的开发人员通常不是流失率最高的人、最多变更集的提交者、顶级错误解决者、顶级功能实现者等。
您必须了解软件模块，识别其核心部分，然后寻找提交它们的人。我相信这些步骤不能自动化 - 不能在 TFS 或任何其他套件中自动化。
一个小小的机会是找出构建该模块的人，并将其插入存储库。如果这个初始提交有肉体&骨头（这不是存根）你肯定有一个对此了解很多的候选人。这可以通过 TFS API 检索。
与团队讨论此事也有帮助。
I 've participated in numerous software transfer projects, where one team handed over the sources to another. Under such circumstances it is vital to recognise who the true expert for a given source file / software component is.
So, I 've learned the hard way that the developer who is the gatekeeper, is frequently not the one with the highest churn, the commiter of the most changesets, the top bug-solver, the top feature-implementer etc.
You would have to get to know the software module, identify it's hardcore parts and then go look for the one(s) committed them. I believe those steps can't be automated - not in TFS, or any other suite.
A slight opportunity is to find out the one who constructed the module, that is inserted it in the repository. If this initial commit has flesh & bones (it's not a stub) you definitely have a candidate that knows a lot about it. This can be retrieved via TFS API.
It also helps to talk to the team about the matter.
你需要别的东西。想象一个库类对给定类型的对象执行某些操作。如果有人要对该对象的方法进行自动重命名，他们就可以声称拥有该库的大部分所有权，而无需故意更改它。
You need something else. Imagine a library class that does something to a given type of object. If someone were to do an automated rename on a method of that object they could claim a large portion of ownership in the library without ever intentionally changing it.