[EDIT: This idea is temporarily code-named D.I.A.S., the Duplicate Issue Alert System]
So, @sdboyer and I were sitting around talking Git pair-o-dimes and possibilities, and he spouts off with the idea that if a repo were to fork core in order to develop a new initiative, and that forked repo has commits to a certain file at a certain line number, shouldn't it be possible to programmatically find all the other instances of core forks that also touch(ed) or changed that same code? This would keep developers from stepping on each other's toes during reintegration of their initiative back into the main core code.
That idea, while cool in it's own right, sprung forth yet another concept. What if developers who are working in an issue queue could be made aware of all the other projects which might also be working on their "stuff"? Could instant collaboration occur without human intervention, i.e., manually pasting links from other issue(s) into an issue comment?
I'm drawing up a couple of wireframe diagrams to illustrate this concept so that we don't loose it, and so that it can be properly programmed, but in the meantime, I'm sticking this idea into ascii and I'll come back and edit it later.