Earlier quoted context omitted.
This makes me think, it is opposite to what mostly is used in open source projects that have bugtrackers. Github is filled with countless 'mistakes' (issues/pr's) people made in the code they published. Should there be some kind of way to make issues private? Before I was into open source I was always afraid to show my code to anyone because of the critique I could expect. But some coworkers helped me get the confide…
Bugs are not critiques. Working in software development, you learn extremely quickly that everyone writes bugs, and there is nothing to be embarrassed about. The openness of issue trackers even helps elevate that. On the other hand, it's not normal and not often practiced to go digging to see whose mistake introduced a bug and call them out in public on it - that would be what shouldn't be done at all.
Not only (technical) bugs are reported, but also design decisions and such. A lot of those things often come down to difference in opinion. I've seen some developers be really adamant about how a bug was actually a feature.
> The openness of issue trackers even helps elevate that.
I agree partly. For me it helped see things different and make a positive growth. But I can image some staying afraid to enter or be deterred really quick never coming back.
>> This follows the "praise in public, punish in private" maxim.
So like the previous poster said. I am wondering if Github et al. should not contain a private channel.
I have a email on my Github page. And besides spammers I sometimes get questions regarding my projects. I don't know if it is due to people not understanding Github that well[0] or wanting to contact privately[1]. But for some reason they didn't open a public issue[2].
[0] I've met a lot of technical people that just are afraid of Github because it is complex. Electrical engineers, mechanics, embedded engineers. People I figure would understand software development concepts.
[1] Asking a stupid question publicly could also count toward making a public mistake depending on how secure someone feels about themselves.
[2] There is of course also the discussion if issues should be your projects helpdesk next to being an bug tracker. And raising an 'issue' for something that might just be a question might feel strange for some.