Onboarding Team Member Guide

Granting Access

Before granting any access, we need to identity our new team member's role (E.g. developer, ops access).

GitHub repository:

Grant necessary access to: https://github.com/bcgov/nr-spar

When granting access, follow the GitHub Access Control Policy to understand which level of the access to grant. Grant access only to the application the new member will work on immediately. Access to other repositories can be added later when the work starts.

Github Project:

Invite to nr-spar project page.<(https://github.com/orgs/bcgov/projects/35)>

Confluence:

Add the new team member's contact information to the Team Evergreen confluence page

Give our new team member access to edit needed confluence pages

AWS:

Grant necessary access to our AWS workspace only if the new member will work with it. Need to follow the AWS Access Control Policy to understand which level of the access to grant. Openshift: Depends on which project our new team member will work on, if need, grant necessary access (default edit access) to our Meeting Invite Forward the meeting invitation to our new team member:

Daily Scrum

[]Sprint planning, review, retrospective []Backlog refinement []Meetings for other services we use: Platform Community Meetup, Common Services Showcase Sprint Review, API Gateway Program Services Sprint Review

Team support: []FDS regular meetup, service designer meetup, product owner meetup, etc.

Project and Resource Links: GitHub repositories: Figma Design: <link to your Figma Design> AWS workspace login console: https://login.nimbus.cloud.gov.bc.ca/api <Zenhub board/Jira board/Github project board link> Openshift login console: https://console.apps.silver.devops.gov.bc.ca/ Rocket chat support channel: https://chat.developer.gov.bc.ca/, #developers-how-to, #aws-how-to, more channel please see the image

Technical Walkthrough: Local development environment setup: follow the readme in each project, if have any questions, could reach out to our team members