Add guidance on open sourcing without publishing individual user emails

best-practice-and-impact / qa-of-code-guidance

Guidance for quality assurance of code for civil service researchers and analysts.

https://best-practice-and-impact.github.io/qa-of-code-guidance

Other

74 stars 18 forks source link

Add guidance on open sourcing without publishing individual user emails #189

Open sarahcollyer opened 2 months ago

sarahcollyer commented 2 months ago

Publications are no longer including individual contact details, and we're being advised generally to not share our individual contact details. Open sourcing can mean individual email addresses are shared, so we should add guidance on how to prevent/undo this.

Guidance should at least cover:

Keeping your email address private when committing
Rewriting history to remove emails from old commits
Mirror repos (private for dev and a public one with a generic team contact)