Skip to content

Latest commit

 

History

History
54 lines (42 loc) · 3.25 KB

developer_onboarding.md

File metadata and controls

54 lines (42 loc) · 3.25 KB

18F Developer Onboarding Checklist

Create a new issue, and copy the raw Markdown from below into it:

Onboarding for @newmember

Tasks for @newmember

Later

  • Set up the Cloud Foundry CLI (which you will need to deploy)
  • Learn more about Cloud Foundry
  • Deploy C2 to c2-dev (or c2-staging)
  • Set up your own development app on Cloud Foundry
  • Get added to the MailChimp account (and thus Mandrill)
  • Access support emails [email protected], [email protected], and gatewaycommunicator
    1. Make sure someone has requested/completed access for you (See tasks for @oldmember)
    2. Go to Gmail and click 'Add Account'. Enter in each of these email addresses. If you are asked for a password, leave it blank. As long as you are already logged into your GSA email, the email addresses should be loaded.
    3. One would expect the newly added email to load automatically, but it doesn't. To load the new email, simply click on your email address at the top right of the page to show all of your loaded email accounts. Click on the newly added email address (capdevs or communicart.sender) to load it.

Tasks for @oldmember

  • Add to Slack channels
  • Add to the kanban board
  • Add to Trello
  • Add to @18F/cap team on GitHub
  • Add to support emails: capdevs, communicart.sender, and gatewaycommunicator through IT Service Desk
  • Send access information for developer test emails: gsa.approver, communicart.budget.approver, and communicart.ofm.approver)
  • Add to New Relic
  • Add to calendar items: standups, IPM, and story grooming sessions
  • Schedule a code walkthrough
  • Set up pairing session
  • Give intro to current stories
  • Give intro to weekly ceremonies and team workflow

Later