Onboarding checklist for Igor

[jadudm]

Welcome to the team Igor

@jadudm will be your onboarding buddy and can help you if you get stuck on any of the steps in the checklist below. There's also a separate checklist that your onboarding buddy will tackle!

For all team members

All team members will want to take the following steps:

• Review the project README
• Ask in #search-general for team members to reach out and setup an intro coffee
• Complete OLU trainings
• Review the TTS handbook
  • https://handbook.tts.gsa.gov/getting-started/
  • https://handbook.tts.gsa.gov/about-us/tts-history/
  • Skim through: https://handbook.tts.gsa.gov/
• Review our agile processes
  • If you are unfamiliar with agile, this is a good overview
• Familiarized yourself with the Jemison architecture

Systems access

• Join/get added to the team Slack channels
• Get added to the team shared drive
• (Feds) get added to the Federal shared drive
• Have the team calendar owner share the calendar invite link to our new team member
• Get added to our ZD helpdesk instance
• Get access to our GitHub repositories

  • If you're not already a member of BOTH the GSA and GSA-TTS GitHub organizations, follow the process outlined here, requesting access to the appropriate org(s). When it's time to send the mail, look up the Product Lead (see the staffing list) then start with this template, mailing from your GSA email address:

    To: gsa-github.support@gsa.gov
    Cc: [the search lead]
    Subject: GSA and GSA-TTS GitHub organization membership
    Body:
    [Edit the following text to put in your GitHub username and your GSA email address, then remove this instruction text.]
    Please add my GitHub account (https://github.com/myusername) to the following GitHub organizations:
    - https://github.com/GSA
    - https://github.com/GSA-TTS
    
    I will be working on the Search.gov project:
    - https://github.com/GSA-TTS/jemison
    
    I have cc'd the search.gov lead for awareness.
        
    Thank you!
    

    • (Note this step could take a few days; humans handle these requests.)

  • Once you are added to the GSA-TTS org, ask the person(s) with the "Maintainer" role to add you to the searchgov-team team. This will grant you read/write access to our repositories.

For Engineering

• Familiarize yourself with Go, Jsonnet, and Cloud.gov—tools used in this project.
  • If it's not already set up on your machine & account, enable commit signing. Also see the pinned messages in the Slack development channel.
  • If you're not already, get setup with Cloud.gov
    • Once your account exists, make a PR to add yourself to the list of developers with access to our spaces.
  • Practice deploying a python application to Cloud.gov using the Cloud.gov command line interface (CLI): https://cloud.gov/docs/getting-started/your-first-deploy/.
• Get set up for local development so you can start contributing
• Review the main body (~60p) of NIST SP 800-161 Rev.1 on supply chain risk management. Reply to this onboarding ticket in a comment when you have completed this review.

[jadudm]

Igor is being onboarded from the existing team.