The challenge with respect to that is that there are pretty notable trade offs with design choices for implementing a bug tracker, wiki, etc at this stage of gi

The challenge with respect to that is that there are pretty notable trade offs with design choices for implementing a bug tracker, wiki, etc at this stage of git's development. Any one choice by the official git project core would be met with serious push back. The best outcome for git in my opinion would be some work put into in-repo issue tracking, but not as a part of git's core distribution. There have been a number of independent efforts to tackle all of these problems but they've lost steam for the past 5 years or so. It's too bad since it's a pretty neat problem space to see solutions built in and to discuss them, but that seems to be the current state of things.