Onboarding Template - JR Reed

[michelle-dooley]

Welcome to the VA-CMS Team!

This ticket contains all of the onboarding activities for a new member joining the VA-CMS Team.

VFS-CMS Start Date: 4/15/24

Team info:

• Product Owner: Erika Washburn
• Program Manager: Michelle Dooley
• Product Manager: Grace Kretschmer

• [x] Meet with your Program Manager for a brief orientation to the CMS Team.
• [x] Read about the CMS Team and see full team roster (link)
• [x] Read the VA.gov platform crew principals.
• [x] Review relevant Platform orientation recorded sessions.
• [x] Review Platform website to understand services and process.
• [x] Explore VA.gov

VA security clearance / VA onboarding paperwork

Getting onboarded to the VA can take a few weeks to a few months. We encourage you to prioritize these tasks before any team tasks.

• [x] Wait to receive an email directing you to the paperwork you should fill out for secure access to relevant VA systems. Federal contractors are required to complete many of the same forms as federal employees. If you're not sure which you contract you are on, ask your Delivery Manager.
• [x] Complete and submit your initial paperwork per contract instructions, including setting up your fingerprinting appointment.
• [x] When you are notified to complete your e-QIP (the online version of the federal standard investigation form, SF 86), it will require a lot of background information. Review page 7 of the SF 86 guide in advance for the list of information you'll need to collect to complete e-QIP

Drupal Content Management System

Gaining product knowledge about the CMS can take some time. These activities can be completed in any order and are secondary to your VA security clearance onboarding tasks above.

• [x] Watch the 2021 Drupal GovCon presentation about the project.
• [x] Why are VA Medical Centers changing their websites? Watch the 2-minute YouTube video.
• [x] Why are Vet Centers important to Veterans? Watch the 2-minute YouTube video.

What products do we support?

• [x] Read the product outlines in the repository for a non-inclusive view of the platform. Be mindful of the dates, as some of these products have not been shipped but may still live in our backlog.

Access

Regardless of your role, please review these access notes. Your Program Manager will have set up most of the tools for you (with the exception of SOCKS). This list is for you to verify along the way:

SOCKS - VA network proxy

The VA network is required for Drupal CMS and other VA tools and usually requires a VA ID card (PIV or Smartcard). Until you get your paperwork approved and ID card, SOCKS proxy is a back door to some of these tools. This is the first priority for week two.

• [x] File a SOCKS proxy request and select the label for your team. See https://github.com/department-of-veterans-affairs/va.gov-team/issues/68549

• [x] Provide a screenshot of the email that confirms your eQip transmittal date. This is an acknowledgement that your paperwork is being processed from a security standpoint. You cannot receive SOCKS access prior to this point in your onboarding.

• [x] Request a Github personal access token first. You only need to do the "repo" panel in that form and leave the other panels as is. It may take a day or two for the SOCKS proxy request to be fulfilled before you can complete the rest of the SOCKS process. This can be a complex process. Post in #sitewide-program Slack channel if you need help from a current member - we're happy to help.

Github - for issue tracking and document sharing

• [x] VA.gov request instructions - Your Program Manager should have already requested this for you so double check with them before submitting a new request.
• [x] Intro to CMS Team Github
• [x] CMS team list - Same as above. You must be added to this team to contribute in Github.
  • [x] Optional: New to Github and markdown? Learn about writing on Github or watch a tutorial video

Slack - for instant messaging

Your Program Manager should have already requested this for you, but if not, view the request instructions

• [x] Review Slack etiquette.
• [x] Update your profiles in Slack (in the Oddball and DSVA workspaces), add a calendar link
• [x] This is a description of other channels to put on your radar. Note that many are going to be dependent on which workstream you're in.

Drupal - for logging into the CMS (SOCKS or VA access with PIV card required)

Drupal is the VA's content management system of choice. For anyone on our team, it's beneficial to have a CMS user account so you can login, look at settings, and understand how the CMS works at a high level. If you need help completing the technical steps here, schedule 30 mins with your Delivery Manager.

• [x] Learn about the different Drupal environments
• [x] Drupal production environment access (SOCKS or VA network required) - in DSVA #cms-support channel, use the Slack workflow to file a helpdesk support request. Ask the helpdesk to create a Drupal user for you in prod.cms.va.gov.
  • Product Managers should request an Administrator account.
  • DevOps team members require an administrator account. (SOCKS or VA access with PIV card required)
  • Standard practice for other roles is to have minimal access in prod (content editor or even a blocked account) and full admin access in lower environments.

Tugboat - for previewing in demo environments (SOCKS or VA access with PIV card required)

Tugboat is a development server platform where you can preview CMS code changes pre-production.

• [x] Tugboat for non-engineers
• [x] Tugboat for engineers

Other tools

• [x] Confluence (your Program Manager will get you added)
  • [ ] Datadog to access monitoring metrics (your Delivery Manager will get you added)

For DevOps members

• [x] VA.gov tools overview
• [x] IAM/SSO lower environment access
• [x] Jenkins (SOCKS required)
• [x] Grafana (SOCKS required)
• [x] Sentry (SOCKS required)
• [ ] AWS (SOCKS required)
  • [ ] And request to be added to the adhoc-vetsgov-devops group.
• [ ] sshuttle
  • [ ] Access to dev & staging to be able to replicate the SSO piece of the login experience (SOCKS or VA access required)
  • [ ] Venafi access
  • [ ] SSH access to CMS servers
  • [ ] Okta access for Datadog
  • [ ] Secure Access to GitHub Bot Account
  • [ ] Access to dev & staging to be able to replicate the SSO piece of the login experience (SOCKS or VA access required)
  • [ ] PagerDuty access

For Developers

• [x] VA.gov tools overview
• [x] Access to dev & staging to be able to replicate the SSO piece of the login experience (SOCKS or VA access with PIV card required)

• [x] Review the VA.gov Design System which includes how to provide feedback

  VA Platform documentation

• [x] VA Technical Architecture Overview - describes technical architecture of va.gov (+ api.va.gov)
• [x] Deployments: https://depo-platform-documentation.scrollhelp.site/developer-docs/deployments
  • [x] Deployment crib notes with detail re: various repos, timings, & support
• [x] Front-end workflow: https://depo-platform-documentation.scrollhelp.site/developer-docs/frontend-workflow
• [x] Front-end steps to run & build VA.gov locally

[gracekretschmer-metrostar]

@mreed101 have you scheduled your PIV card appointment and/or picked up your PIV card yet?

[gracekretschmer-metrostar]

Per JR: I have an appointment for 5/20 but I received an email the other day saying I needed to go to a specific center to pick up my card… Scheduled another appointment at a different location for (deep breath) June 17th because the earliest that location had appointments was starting on 6/11 which is when we would be in DC. So hopefully I get the card Monday otherwise I’m stuck until June.

[mreed101]

Follow up, attended the appointment, card was sent to a different location after I had already scheduled my appointment. The other location would not let me pick up my card although it is ready without an appointment. Appointment is scheduled for June 17th, reaching out to Amber to see if there is anything that can be done

[gracekretschmer-metrostar]

JR got his PIV card on 6/17.