[Onboard] dan.mayol@civicactions.com

[adborden]

Welcome! The Onboarding wiki describes the onboarding process for new team members on Data.gov. You’ll learn mostly from pairing and interaction with your teammates but these are some handy resources to get you started.

Below are the tasks that will drive the onboarding process.

Tasks for admin or onboarding buddy

• [x] Add team member to TTS Slack and #datagov-devsecops

• [-] Invite team member to Data.gov calendar and events

  • Daily sync
  • Sprint planning
  • Retro

• [-] Add team member to Google Drive

  • Data.gov
  • DevSecOps

• [-] Add team member to email lists

  • Data.gov team list
  • Inventory help list

• [x] Make sure team member has 2FA enabled for their GitHub account and request membership to GSA GitHub org

• [-] Add team member to data-gov-support GitHub team

• [-] Request TTS Bug Bounty access #bug-bounty-partners

• [-] Add team member to New Relic with permissions:

  • Alerts manager
  • APM manager
  • Infrastructure manager
  • Synthetics manager

• [-] Add team member to Docker Hub

• [-] Add team member to Snyk

• [-] Add team member as a SpaceDeveloper in the development, staging, and management spaces in cloud.gov.

  $ cf set-space-role gsa-datagov SpaceDeveloper

• [-] Request Federalist access by posting in #federalist-support with the new member's GitHub username.

Tasks for new team member

• [x] Ensure your GitHub account meets the criteria for GSA GitHub org (setup 2FA)
• [x] Read through the required reading list
• [-] Request access to Data.gov systems; select “Catalog Admin” for the system, and “Data.gov team member” for justification
• [x] Add yourself for AWS sandbox access
• [-] Request access to AWS OPP account from team member
• [x] Add your public SSH key to the GSA/datagov-deploy
  • Clone the datagov-deploy repo locally
  • Follow the setup instructions for development
  • Add your public SSH key to the datagov_operators_test.
• [-] Enable MFA for HackerOne
• [-] Join Open Data community list

[CodeShtuff]

@adborden I have local branches for both datagov-deploy (for adding SSH key) and datagov-infrastructure-live (for adding user to users.tf) repos, however trying to push my branch up encounters a not surprising permissions rejection. Perhaps I missed a step somewhere (request for access, etc.)?

[CodeShtuff]

Aaron provided guidance on process and verification of correct permissions. Found that it was my email push settings causing the issue with the deploy repo. Created fork of the infrastructure repo for creating the PR. Both PRs have been created to complete those relevant steps. https://github.com/GSA/datagov-deploy/pull/2257 and https://github.com/GSA/datagov-infrastructure-live/pull/113

Assigning back to @adborden to finalize the above reviews/merges.