- 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.
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>
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.
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.
(Notably, the author of this leaves their address off their profile, but leaves it in their commits. Would emailing them be reasonable?)