[th3iedkid]

>>It absolutely sickens me to encounter users who seem to be incapable of using git without a proprietary communications tool.

What is the proprietary communication tool which seems a must for git to work?Are they referring to SSH?or Something else am not aware?

[warbiscuit]

I think he meant github, and the various features it offers, such as issues, pull requests, and threaded discussions thereof.

I'm also not a fan of github's monoculture (or for that matter, of git's -- i rather like mercurial). I've only got one or two open-source projects out there, but I've encountered the "you are aware of github, right? why are you using <insert anything else>" mindset before.

Ideally, git or mercurial or some dvcs gains the ability to track messages and issue tracking within the repository allowing multiple frontends (such as github) to make use of a common backend model. But until then, while github is nice, I think it shouldn't be a necessary requirement for running a project, merely a sufficient one. Homogeny breeds fragility, and all.

[johnny22]

fossil does this already: http://fossil-scm.org/index.html/doc/tip/www/index.wiki

It's likely not the only one out there though.

[yeukhon]

He's referring to using Github as the communication platform /medium between developers, contributors and users.