Onboarding [Vivian]

[christinach]

Everybody

• [x] Set up your work computer
  • [x] tips for setting up a new mac
  • [x] tools that we use on our team
• [x] Add your SSH key to Princeton Ansible for server access. The key should be an ed25519 key. All team members should be added to both the deploy_user_github_keys and library_github_keys lists.
• [ ] Get all needed accounts
• [x] PUL IT handbook
  • [x] Read our norms around inclusive language
  • [x] The services directory is where we keep cross-team technical documentation that doesn't live anywhere else. You don't have to read these all now, just get a sense for what/where this documentation is.
• [x] DACS work cycles
  • [x] Github issues and how we label them
  • [x] Our board
• [x] Discovery and Access Services google drive
• [x] Become familiar with confluence
• [ ] Accessibility syllabus
• [ ] Deploying code with Ansible Tower
  • [x] Procedure in PUL IT handbook
  • [x] Team-specific instructions in our handbook
• [x] Add your name and github email to the shared .gitmessage
• [ ] Test-driven development is a popular approach on our team. The basics of RSpec and TDD are covered in the PUL IT Handbook.
• [ ] The security repo
• [x] Learn how to handle incidents
• [x] Team meeting structure
• [x] Make sure you have invitations to all the following meeting:
  • [x] Team standups, retrospectives, and wrap-up meetings (ask @kevinreiss)
  • [x] Ansible open house (ask @acozine)
  • [x] Cross-ITIMS (ask @tpendragon)
  • [x] Orangelight/Bibdata (ask @christinach)
  • [x] Orangelight issues - Cleanup (ask @christinach)
• [x] Browse the DACS handbook. You don't need to read it all now, just get a sense for what documentation it contains.
• [x] Remember to ask questions 😀

Monitoring

• [x] Honeybadger
• [ ] Datadog
• [ ] In progress: Sensu

Non students

• [ ] Princeton University Human Resources
• [ ] Runner role

Student developers

• [x] Student Employment office
• [x] Look for issues with the "newdev" label

[sandbergja]

@vh8154 is onboarded 🎉🍿