Onboarding checklist for @rocheller123

[jadudm]

Instructions for the issue creator:

1. Fill in the GitHub username of the new person (if known) and the name of the onboarding buddy.
2. Remove irrelevant checklists (eg designers should never see the engineer checklist.]
3. Remove the horizontal line below and everything above it (these instructions).

---

Welcome to the team @rocheller123!

@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 you

Here's a checklist to get you started and to make sure you've got access to :all-the-things:!

• [x] Review the project README in Google Drive
• [x] Join the Slack channels in the project README
• [ ] Review our process documentation

• [x] Get access to our GitHub repositories

  • [x] 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 product 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 FAC project:
  - https://github.com/GSA-TTS/FAC
  
  I have cc'd the FAC Product Lead for awareness.
  
  Thank you!

  • (Note this step could take a few days; humans handle these requests.)
  • [x] Once you are added to the GSA-TTS org, ask the person(s) with the "Maintainer" role to add you to the FAC-team team. This will grant you read/write access to our repositories.

For engineers, also...

• [ ] Familiarize yourself with Python, Django, and Cloud.gov—all tools used in this project.
  • [ ] If you need to catch up on the latest in Python development, check out the Python developer's guide.
  • [ ] Work through the Django Tutorial and writing your first Django app.
  • [ ] 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/.
  • [ ] Survey existing TTS projects which use Django+Cloud.gov like: Tock and the DOJ CRT Portal.
• [ ] Get set up for local development so you can start contributing

For your onboarding buddy

Note: If you're not able to do any of these yourself, you're still responsible for making sure that the right person makes them happen!

• [x] Add to the FAC-team@GSA.gov Google Group
• [x] Add to standing meeting invites (should happen automatically via addition to the Google Group membership)

For designers, also...

• [ ] Add as an editor on active Figma projects
• [ ] Add as a form manager to the touchpoints recruitment intercept

For engineers, also...

• [ ] Add as a member of the FAC group in New Relic (@GSA-TTS/fac-admins can do this)

For product leads/owners, also...

• [ ] Make them Owner of the various Google Groups in the project README
• [ ] Add them to the FAC-admins team in GitHub and make them a Maintainer.
• [ ] Also give them the Maintainer role in the FAC-team team in GitHub.