Skip to content

Onboarding and offboarding

Jump to bottom
andrea rota edited this page Mar 9, 2023 · 6 revisions

Onboarding

Intro to project

  • onboarding meeting(s)

    • project aims, goals and scope (Clara)
    • walkthrough/demo of the platform (Clara)
    • where to find resources and documentation (Clara)
    • who is who (client side) (Clara)
    • science behind the project (Alicia)
    • data models, data pipelines, geoprocessing (Alicia)
    • getting started (Andrea)
    • (backend devs) backend architecture (Andrea)
    • (backend devs) backend codebase walkthrough (Andrea)
    • (backend devs) development process: requirements -> HLD -> LLD -> abstractions -> tasks (Andrea)

  • point to relevant resources

    • google drive project folder
    • GH repo
    • this wiki

Access to resources

  • grant access to the marxan-dev GitHub group (Vizz devs only; members of this groupu will be admins of the main Marxan Cloud repo)
  • grant access to the Marxan Cloud repo (freelancers only)
  • grant access to Shared-Marxan Cloud LastPass folder (check if we need to restrict sharing to a subset of secrets for external devs)
  • invite to #marxan channel
  • invite to #marxan-dev channel
  • (backend devs) invite to #marxan-dev-backend channel
  • add to shared calendar
  • invite to ritual meetings
  • (if relevant) invite to stand ups/regular meetings with client
  • invite to Jira project
  • invite to Basecamp project
  • (tbd) grant access to cloud resources; try to stick to the principle of least privilege and to keep good secret rotation practices
    • Vercel (frontend)
    • Resources on Azure (as needed)
    • SSH with shell access to test VMs
    • SSH without shell access (to tunnel VM ports locally) to test VMs
    • etc.

Offboarding

Personal retrospective

A short personal retrospective may be useful to understand how working on this project felt (maybe a quick chat with a couple of team members), besides any ongoing feedback we may give to each other while we are active on the project.

Access to resources

Revoke access to all the resources listed in the onboarding section above.

If a project member is leaving Vizzuality altogether, some of the tasks may be done by removing them from the Vizzuality GH organization and by disabling their Vizzuality Google account.

Clone this wiki locally