This is the process for starting new developers on the project.
Checklist - team lead
- Team member is added to the Input Output organization on GitHub (you need to open an IT Change Request for this).
- Team member is added to the Adrestia group on GitHub (you need Maintainer permissions on the team to do this).
- Team member is added to the Adrestia space on Matrix and #dev channel.
- Team member is added to important Chat Rooms.
- Team member is added to Vaultwarden shared folder.
- Team member is invited to weekly meetings and daily Hello call.
Checklist - new team member
- Provide GitHub user name to team lead.
- Provide PGP key ID to team, and ensure that your public key is published on multiple keyservers.
- Follow the Jira Orientation Checklist
- Skim the ramp-up docs.
- Ensure that you are able to edit the Adrestia Website. If you discover something that needs documentation, update the Documentation Guidelines.
Ensure that you have a Vaultwarden account associated with your
Essential reading list for new team members.
- Building A quick guide to building the wallet from source.
- Testing An introduction on how to run tests for the wallet, once you’ve built it.
- Development Process Our team’s development process and methodology.
- Coding Standards We strive to follow these shared standards for all newly-written code.
- Code Review Guidelines We’re always trying to improve our code review process. This document contains a few of the principles we’ve collected along the way. It’s not complete, and we hope you can help to make it even better!
- Adrestia Project General documentation about the Adrestia umbrella project, and what it is.