[couchand]

> Making it convenient for you to communicate with other varied humans contributing to, or otherwise interested in the code, is the key differentiator. And apparently this is not the part SourceHut prioritizes. No wonder, because it's the hardest part.

Just because you don't seem to understand or agree with another person's priorities doesn't mean that they don't have them. By my reading, contributors to SourceHut absolutely do prioritize tools that humans use to communicate, and in particular ones that have been demonstrated to support complex and nuanced technical discussions.

[nine_k]

This is great to know!

SourceHut is new, and likely has a ton of competing priorities.

Also, different groups have different preferred styles of communication. (E.g. chat vs email vs forums is a typical divide.) Different places offer different styles, and this is great, because one size often does not fit all.

That said, most people are conditioned by using GitHub, and this sets their default expectations. Then the network effect kicks in.

[couchand]

I'm not sure we have full data on the question, but by my own experiences the default expectation for most people regarding version control is copy the file and rename it. The default expectation for most people on collaboration tooling is sending an email. If they consider such things at all.

We can easily define a niche within which GitHub-awareness can be presumed but it's certainly not "most people".

[nine_k]

I suspect the majority of people who come to GitHub with intentions other than contributing come either to skim the README for installation instructions, or to complain about a problem. They may not even know about git. This is the wide kind of GitHub-awareness, which still assumes a level of computer literacy above that of most people.