upvote

points

by mschuster919 hours ago |
comments
upvoteby pwdisswordfishs4 hours ago|
next
[-]
> message boards suffer from the SSO friction issue

GitHub is an SSO provider and has been for a long time. This criticism is ignorant.

Aside from that, there's nothing stopping anyone from using GitHub's dedicated message boards for message board stuff, or, before those existed, shunting it all off into the "issues" of a separate "$PROJECT/community-bullshit" "repo" instead of cluttering up the actual bugtracker.

> Social media... yikes. No, no, no.

I'm talking about the appropriate-for-social-media stuff people are already posting on GitHub issues. It's like you started writing your comment and lost the context. People are today already misusing GitHub issues for this. I'm saying keep the stuff best kept to social media and email... on social media and email. Don't clutter the bugtracker with it, and for project managers: don't let other users do it either. (You will lose contributors who know how to use a bugtracker efficaciously and are accustomed to it but have a fixed time budget and don't want to have to sift through junk for the privilege of doing free and thankless QA on your software.)

> You will drown in spam.

The irony. Help. It burns.

For emphasis: Everything that isn't a bug belongs on a message board, mailing list, or social media, and not on the bugtracker. Anyone who can't abide by this simple, totally reasonable request should be booted.

reply
upvoteby mschuster914 hours ago|
parent|
[-]
> GitHub is an SSO provider and has been for a long time. This criticism is ignorant.

The problem is, a "sign up to contribute" is a friction source. It will almost always leak my email. In contrast, I'm already logged in to Github.

reply
upvoteby pwdisswordfishs3 hours ago|
parent|
[-]
What I'm hearing is, "Your Honor, I know that I shouldn't have blown through that stop sign, but hear me out: I wanted to. If I didn't, then I would have had to stop and wait for traffic to pass and respect other people's time. Does that strike you as reasonable? I think we can agree that it does not."
reply
upvoteby tolerance9 hours ago|
prev|
next
[-]
What do you think about Discourse in particular.
reply
upvoteby Pxtl9 hours ago|
prev|
next
[-]
GH has a "Discussions" feature for message-boards attached to your project. Same sign-on as GH. Nobody turns it on.
reply
upvoteby simoncion7 hours ago|
prev|
[-]
> - mailing lists are even worse usability-wise because these by design leak your email address...

So does git and GitHub. Last I checked, authoring a git commit with an email address associated with your GitHub account is what makes GitHub attribute that commit to your account. I assume Gitlab works in a very similar way.

"But 'git clone' is soooo much harder than reading through mailing list archives!" Nah.

reply
upvoteby csense6 hours ago|
parent|
[-]
If you don't want to expose your email address but you still want commits to be associated to your account, Github lets you use a noreply email address [1].

[1] https://docs.github.com/en/account-and-profile/reference/ema...

reply
upvoteby ghostly_s5 hours ago|
parent|
next
[-]
I actually was looking into this recently (exploring how much of a PITA changing my github email would be) and found it interesting that, while in principle your GH email is public to anyone interfacing with your commits via `git`, they have gone to some length to avoid displaying it anywhere in the web interface. The docs actually mention it being shown on your 'profile' page but I don't see it anywhere there.
reply
upvoteby simoncion5 hours ago|
parent|
prev|
[-]
> Github lets you use a noreply email address

Oh, I was unaware of that. I've not seen anyone use it, [0] but I've only paid any attention to the Big Corporate and Traditional Hacker populations.

Thanks much for the information.

[0] I'm certain that folks do use it, so folks shouldn't bother pointing out people that do.

reply
upvoteby pwdisswordfishs4 hours ago|
parent|
[-]
It's the default on new accounts for stuff when people do things through the GitHub interface.

If you set user.email using git-config on your machine to a real email address and decide to author and publish commits with it, then GitHub will, of course, not be able to stop you (aside from maybe rejecting the commits when you tried to push them). It can't just arbitrarily rewrite the email address in the commit. That would break Git's data model.

reply