我们是否应该让客户的管理团队直接访问我们的 git hub 存储库，以便他们可以实时查看我们的动态？
我们目前正在为一位刚开始与分布式团队合作的客户工作。我们的团队遍布印度和英国。
虽然我们有不错的项目跟踪工具 (Mingle)，但让客户端的 PM 访问我们的 git hub 存储库是个好主意吗？这会让他们更容易吗（看看开发人员正在做什么，并深入了解团队一直在开发什么）。
我同意并非所有提交消息都对他们有意义，但这是否是增强他们对我们正在做的事情的信心的好方法？ 他们已经可以在我们的 QA 和 UA 环境中查看我们每两周发布的版本，但这仍然落后于开发 5-6 天。
另外，是否有任何关于 git hub 的报告可以让 PM 类型更容易理解这一切？
谢谢
We are presently working for a client who is new to working with distributed teams. We have teams spread across India and the UK.
Although we have decent project tracking tools (Mingle), would it be a good idea to the give the PM at the client access to our git hub repo. Would this be make it easier for them (see what the devs are working on and an insight into what the team has been developing).
I agree that noot all commit messages would make sense to them but would this be a good way to boost their confidence in what we are doing?
They already can check out our fortnightly releases on our QA and UA environments, but this still is behind dev by 5-6 days.
Also, is there any reporting for git hub which makes it easier for PM types to make sense of it all?
Thanks
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
我认为没有任何自动报告可以很好地替代团队在给定时间段（天、周等）内完成的工作的书面或口头总结。如果您想提供提交消息以及专门用于佐证的书面或口头报告，那就更有意义了。不过，解决这个问题并不容易，有时你不得不花比你想要的更多的时间来沟通，但正确地做是有回报的。
I don't think there's any automated report that is a good substitute for a written or verbal run-down of what the team accomplished within a given period (day, week, whatever). If you want to provide commit messages along with your written or verbal report exclusively for corroboration, that would make more sense. There's no easy way out of this though, sometimes you have to spend more time than you'd like on communication, but it pays off to do it right.
他们不需要访问存储库本身。除非他们是开发人员，否则他们无法充分理解他们所看到的内容，从而使其变得有价值。
我建议让他们访问自动化构建的结果，如报告中所示，更重要的是，显示测试套件通过/失败结果的报告。
They don't need access to the repository itself. Unless they are developers they wouldn't be able to make enough sense of what they were seeing to make it worthwhile.
I'd suggest giving them access to the results of your automated build, as in a report, and more importantly, a report showing the results of the test suite pass/failures.
作为一般规则，我认为让客户访问源代码控制存储库不会带来任何好处，除非他们以某种方式做出贡献。我的经验是，这样做只会产生问题（由于之前答案中提到的缺乏理解），这些问题会成为开发人员的时间消耗。如果存在双周发布无法缓解的信任问题，那么直接存储库访问可能无法挽救这种关系。
As a general rule, I think that nothing good can come of giving clients access to source control repositories unless they're contributing to it in some way. My experience has been that doing so only generates questions (due to the lack of understanding mentioned in previous answers) that become a time sink for developers. If there are trust issues that biweekly releases can't soothe, then the relationship likely won't be salvaged by direct repository access.