Don't expose email addresses to the public as committer name

[GoogleCodeExporter]

People value their privacy. Many people never opted in to a scheme where the 
full email address is exposed. Your migration to GitHub simply exposes all of 
this email address.

Where can anyone have their email address REMOVED and replaced with some text?

Original issue reported on code.google.com by googleco...@yahoo.co.uk on 30 Mar 2015 at 1:56

[GoogleCodeExporter]

Depending on which version control system you use, your email address is 
actually embedded in the repository itself. We don't do any extra logic to 
expose your email address as part of the export. In fact, when we export issues 
we intentionally _don't_ unobfuscate email addresses.

To purge the email address from your exported GitHub repo:
(1) Update your git settings to ensure you aren't setting an email address. (I 
do not know for sure, but it might be possible to commit to GitHub using GitHub 
account X, but have your local git settings use email address Y, where Y is 
not-an-address@email.c.) See 
[http://git-scm.com/book/en/v2/Customizing-Git-Git-Configuration this doc].
(2) It is possible in Git to "rewrite history" so you can remap all of those 
commits to having occurred from a different committer. I don't know how to do 
this for replacing author information, but it should be doable. I'd recommend 
you [https://help.github.com/articles/remove-sensitive-data/ start here].

Sorry that this seemed like a surprise to you.

Original comment by chrsm...@google.com on 30 Mar 2015 at 3:38

[GoogleCodeExporter]

I don't have control of any repo in GitHub. I refer to YOUR "auto-export"
https://github.com/google-code-export/datanucleus-appengine

I do not want my email address exposing there (see the most recent "commit") 
which is basically a copy from Google Code naffness.

Please update your repo to remove this.

Original comment by googleco...@yahoo.co.uk on 1 Apr 2015 at 7:35

[GoogleCodeExporter]

I did email Chris DiBona direct about this and got zero reply

Original comment by googleco...@yahoo.co.uk on 1 Apr 2015 at 7:36

[GoogleCodeExporter]

The user or organization named "google-code-export" will have permission to 
amend the repo's history as described in comment #1.

"google-code-export" seems to be a user who is exporting many public repos from 
Google Code, which may be against GitHub's policies, it's a bad/misleading name 
anyway as the user has no affiliation with Google AFAIK.

Finally, please report bugs here. Contacting cdibona directly is unlikely to 
expedite a resolution to your problem, reporting bugs here will.

Original comment by jasonhall@google.com on 1 Apr 2015 at 1:47

[GoogleCodeExporter]

Will contact GitHub since I have no way of contacting this "user" / 
"organisation". 

The fact remains though that Google Code project at 
https://code.google.com/p/datanucleus-appengine/

exposes such email addresses, via the Source -> Changes page. Presumably this 
"user" simply hit code export on it (hence they used your exposed data). Hence 
it originates with your code hosting.

And I contacted CDiBona originally since his blog said to do so OR raise an 
issue here.

Original comment by googleco...@yahoo.co.uk on 1 Apr 2015 at 2:01

[GoogleCodeExporter]

If your issue is that our Source tab exposes your email address, this problem 
originates with the source control system as designed in the first place, in 
this case Subversion. It's been this way for the entire existence of Google 
Code as far as I know, possibly the entire existence of Subversion. This is 
"Working as Intended", and as chrsmith@ said in #1, sorry if this caught you by 
surprise.

If cdibona@ asked for people to reach out to him, then I suppose he asked for 
it. Reporting a bug here is still more likely to result in a useful resolution 
to your problem, as that's the purpose of this issue tracker.

Original comment by jasonhall@google.com on 1 Apr 2015 at 2:11

• Changed state: WontFix