[Onboard] Nicholas Kumia

[mogul]

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

• 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.
• Add team member to TTS Slack
  • #datagov-alerts
  • #datagov-ckan-multi
  • #datagov-devsecops
  • #datagov-notifications
• Invite team member to Data.gov calendar and events
  [Bret to add Nick to data.gov group and remove his REI email from the 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
• Make sure team member has 2FA enabled for their GitHub account and request membership to GSA GitHub org
• Add team member to a Data.gov GitHub team (devsecops: data-gov-support or ckan-multi: data-gov-ckan-multi)
• Request TTS Bug Bounty access in #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 [Bret to add nickumia to Data.gov team]
• Add team member to Snyk
• Add team member to Data.gov Google Analytics account
• Add team member as a SpaceDeveloper in the development, staging, and management spaces in cloud.gov.
  $ cf set-space-role gsa-datagov SpaceDeveloper
• Add team member to the SSB staging AWS account
  In the IAM console: Add a user with console access, auto-generating the initial password and requiring change upon first login. Add Administrators group membership.
• Request Federalist access by posting in #federalist-support with the new member's GitHub username.
• Once member had logged into Login.gov, add them to the data.gov team.

Tasks for new team member

• Log into Login.gov dashboard
• Ensure your GitHub account meets the criteria for GSA GitHub org (setup 2FA)
• 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
• Add yourself for AWS sandbox access
• Request access to AWS OPP account from team member
• Add your public SSH key to GSA/datagov-deploy
• [-] Setup the Ansible vault
  • Clone the datagov-deploy repo
    locally
  • Follow the setup instructions for development
  • Follow the ansible-vault instructions
  • Open a vault file pipenv run ansible-vault view ansible/inventories/sandbox/group_vars/all/vault.yml, you should see yaml in clear text.
• Connect to the GSA VPN for access to the staging and production environments.
• Enable MFA for HackerOne
• Join Open Data community list
• Request access to the Digital Analytics Program

[nickumia-reisys]

How can I be added to the issue to check off completed tasks?

[mogul]

Per Slack discussion, we need you in the GSA GitHub org before we add you to teams. In the meantime we'll check off items for you during the daily sync, or you can just note that you completed items in comments here.

[nickumia-reisys]

I subscribed to the Open Data community list with my reisystems email. It says that my "request to join" is pending approval from the list owner. I might re-join with my gsa.gov email once I get it.

[nickumia-reisys]

A decent amount of the reading list (SSP, Data.gov procedures/links, some specific repos) are restricted until I receive access from the GSA email and authorization. I read a lot of the contributing procedures and specific setup procedures for some repos (ckanext-datajson @FuhuXia and datagov-brokerpak @mogul). I'll continue setting up my dev environment working with these two paradigms and going through the additional reading material from Bret.

[nickumia-reisys]

Enable MFA for HackerOne not applicable

[mogul]

Currently blocked on:

• Waiting for guidance on how to add Docker Hub seats
• Bret regaining access to the various AWS accounts
• Nick having access to login.gov via PIV card

[jbrown-xentity]

Remaining items are leaving undone, as not necessary for regular activities. May do if they become necessary in the future.