alanswx
commented
9 years ago Approval 2: "Login to the DOC Social Media Application Tracking System and apply for permission to create a Github account. You must register with your work email, which should be independent from any personal account you may have on Github."
The github organizations should have social media approval.
Developers already have a "github" account, but they should add their work email to the account, and any source code they check in should be checked in using their work email. This is usually set in the git client.
Does each programmer need to get DOC Social media approval for their combined github identity? or is their Organization enough?
This issue is being copied from from a previous e-mail exchange:
"Thanks for your patience! In short, there should be a one-to-one relationship between each Github user account (a login) with one real-world person ("a human"). Just like each human at your agency has an e-mail address and a computer login, each individual should have their own GitHub login. Users can then join one or more Organizations, again just like in the real world. I can be a NOAA employee, for example, (and thus a member of the NOAA organization), and also participate in projects unrelated to my NOAA work. GitHub will can automatically disambiguate the context of my actions, and reflects that context in all URLs.
If an NOAA employee already has a GitHub account, they should add their government email address to their account (by design, users can have multiple email address per account), and if they're already using Git, configure Git on their work computer to use that email for those repositories. If they're a new user, they should create a new account using their (individual) government email address. Please let me know if this triggers additional questions. We are happy to help."