2 ms·
I'm unsure what the etiquette is with with email addresses in commits–if someone doesn't list it on their profile, but they use it in their commits, should you
by saagarjha 6y ago
I'm unsure what the etiquette is with with email addresses in commits–if someone doesn't list it on their profile, but they use it in their commits, should you really be using it to contact them? Does using an automated tool that finds the one time they forgot to use a noreply address make it any worse?
(Notably, the author of this leaves their address off their profile, but leaves it in their commits. Would emailing them be reasonable?)
- pmiller2 6y agoI assume the author of this tool could have no reasonable objection to being contacted this way. They created it, so they should expect people are going to use it, and, if someone contacts them this way, I don't see where they have any standing to complain. The other question is tougher, because I don't think people put their email addresses in their git identities for this purpose. Yet, it's still technically public information. I am not sure what the right answer is here.
- Symbiote 6y agoThe purpose of email addresses in Git commits is certainly to allow contact from others looking at the code — but that is more relevant for a distributed project like the Linux kernel (coordinated with mailing lists) than a single-committer project on Github. Occasionally, those email addresses are used to try and contact contributers to an open source project to check copyright, licenses etc. Sometimes many years later.
- ssivark 6y agoI’ve used that in the past to reach out to developers, and had fruitful discussions. (And they didn’t seem to mind; it’s great to find fellows interested in the same niche/obscure topic!) I was under the impression that it was a very deliberate choice for git to store/show email, and part of participating publicly in a software project involves attaching a name/email to commits. If one doesn’t want that exposed, then it’s okay to have some junk/null value. The worst thing would be for some automated software to weaponize this by mining email addresses from git repos and spamming them or selling them to marketers. <this is why we can’t have nice things>
- anitil 6y agoRegardless of the motivation of the creator, I'm sure the next person to pick up this tool won't have any qualms about sending spam.
- MaulingMonkey 6y agoRoughly summarizing my personal take on this: "Am I the indended audience for this instance of the email address being public?" - If there's an "obviously" better forum, prefer that (e.g. a public issue tracker for non-security bugs) - If I'm likely to have my own git clone (e.g. I'm another developer or security researcher actively interested in the project), go for it! I tend to be fine with inqueries from this audience even if it's not necessairly project related, although bonus points if they are. - If you were specifically trying to hunt down a point of contact for me and me alone, that's probably fine too. No untargeted and untailored recruiter spam! And likely not as part of a wider recruitment drive, even if you're "tailoring" your recruitment pitches. ...if you're offering me a job specifically to continue working on one of my many abandoned FOSS side projects that you, personally, as another developer have been using - or because we've worked together in the past and want to again - that might be OK ;) - The recipient might redirect you to other channels they see as better fitting - obviously, respect that if they do.
- detaro 6y agoThe readme & blog posts usage of "cold mail" screams "spamming" to me, which is not okay. I could see using the address in a commit for a purely technical contact relating to that software.