[Sir_Cmpwn]

>Because those are two unrelated fields, and one is distinctly not productive.

Each of your examples is something like "I've been writing go for x years". Using a programming langauge does not make you a compiler hacker. Countless people have been using Linux for years but wouldn't be able to make a meaningful contribution to the kernel.

I'm firmly convinced that having to learn something as straightforward and well documented as golang's contributor flow is a pretty good litmus test for potential contributors.

>Didn't they move to Google Code to GitHub, which is the live repo, Gerrit being used for code review only? If so, the dependency is already there. If not, why is it on GitHub at all?

Git repositories are distributed. It doesn't really matter where the upstream is, that has little bearing on project governance.

[coldtea]

>Each of your examples is something like "I've been writing go for x years". Using a programming langauge does not make you a compiler hacker.

Becoming an expert on whatever custom commit process a project has does even less to make you a compiler hacker.

[Sir_Cmpwn]

Correct, but the inverse is typically true - not being willing to learn anything but GitHub is a pretty good indicator for not being able to hack on compilers.

[marssaxman]

I am able to hack on compilers and have spent much of my career doing so. I am also able to learn new development workflows involving idiosyncratic tools which must be installed and configured; I've done it over and over, at many different jobs. You know what? It's a lot of work, and it's all basically a waste of time. I'll do it if I'm paid to, but I'm not interested in spending my free time that way.

[lloeki]

> I'm firmly convinced that having to learn something as straightforward and well documented as golang's contributor flow is a pretty good litmus test for potential contributors.

It's just as much a litmus test of how much time you have in your hands to spend and space in your head to stuff peripheral stuff in. If you did not notice, there was a workshop about how to contribute to Go since, in contrast with its design and philosophy, it has a contribution method as convoluted as for Android/CyanogenMOD/LineageOS, which only makes the ridiculousness of it all the more poignant.

> Using a programming langauge does not make you a compiler hacker

Again, there is much more to Go than just the compiler, which is only a fraction of src. What if I want to contribute a substantial fix or improvement to say net/mail[0]? Or the documentation? Besides, how ludicrous is that a contributor wannabe should have to prove {him,her}self worthy of contributing by passing a supposed test entirely unrelated to the contribution {s,}he's intending to make?

Trivial fixes should be trivial to submit just as well as complex ones to review, and not require anyone to bang its head against an artificial wall.

[0]: https://golang.org/src/net/mail/message.go

[Sir_Cmpwn]

>It's just as much a litmus test of how much time you have in your hands to spend and space in your head to stuff peripheral stuff in.

If you don't have time to learn Gerrit (which is not a difficult tool to learn), then you probably don't have time to be a good contributor - responding to patch feedback, engaging in discussion, and maintaining your changes in the future should issues arise.

>there was a workshop about how to contribute to Go since

Just going to append my own conclusion to this sentence:

>since the entitled GitHub generation of programmers can't be arsed to spend 10 minutes learning any proper tooling