[Onboard] [email protected]

[BFrost313]

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

• [ [email protected]] Review the rest of the checklist below before starting to work through it. Any step that does not seem relevant or necessary for the kind of work that the person onboarding will be doing should have a - in the checkbox and ~ around the line so it's clear that we will not be granting that particular kind of access for this person.

• [ [email protected]] Add team member to TTS Slack

  • #datagov-alerts
  • #datagov-devsecops
  • #datagov-notifications

• Invite team member to Data.gov calendar and events

  • Daily sync
  • Sprint planning
  • Retro

• [[email protected] ] Add team member to Google Drive

  • Data.gov
  • DevSecOps

• Add team member to email lists

  • Data.gov team list
  • Inventory help list

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

• [ [email protected]] Add team member to a Data.gov GitHub team:

  • [[email protected] ] for non-development roles: data-gov-team
  • [[email protected] ] for development roles: data-gov-dev-team

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

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

• [ [email protected]] Add team member to Snyk

• [ [email protected]] Add team member to Data.gov Google Analytics account

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

  • $ cf set-space-role <email> gsa-datagov <space> SpaceDeveloper

• [[email protected] ] Add team member to the SSB AWS accounts
  Make a PR on the Terraform file controlling access to add the new person and include them in the appropriate user_groups.

  • See here for AWS Account ID and access instructions

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

• [ [email protected]] Once member had logged into Login.gov, add them to the data.gov team.

• [ [email protected]] Add team member as form manager to any Data.gov Touchpoints

For new Project Management Office team members, follow these additional steps:

• [[email protected] ] Add team member to Google Drive
  • CKAN Mutli
• [[email protected] ] Add team member to email lists
  • Data.gov support list
• [[email protected] ] Add team member to #datagov-pmo-private
• [[email protected] ] Add team member to additional slack channels
  • #bug-bounty-partners
  • #datagov-comms
  • #sol-data-analytics
• [ [email protected]] Add team member to the GCP project
• [ [email protected]] Add team member with OrgManager permissions in the gsa-datagov organization on cloud.gov
• [[email protected] ] Add team member to data-gov-admins GitHub team
• [[email protected] ] Invite team member to calendar events
• [ [email protected]] Promote team member to Admin in New Relic
• [ [email protected]] Add team member as an Owner to PyPI packages:
  • ckanext-geodatagov
  • ckanext-datagovtheme
  • ckanext-datajson
  • ckanext-dcat-usmetadata
  • ckanext-usmetadata
  • ckanext-metrics-dashboard
  • ckanext-datagovcatalog

Tasks for new team member

• [[email protected] ] Log into Login.gov dashboard
• [ [email protected]] Ensure your GitHub account meets the criteria for GSA GitHub org (setup 2FA)
• [ [email protected]] Read through the required reading list
  • [[email protected] ] Once you have access to cloud.gov, run through training
• [ [email protected]] Request access to Data.gov systems; select “Catalog Admin” for the system, and “Data.gov team member” for justification
• [ [email protected]] Join Open Data community list
• [[email protected] ] Request access to the Digital Analytics Program