2. Onboarding
Hey, welcome! We are so so happy you are here with us :)
CodeDoesGood is a big family where everyone is expected to help each other and treat each other well. If you are lost reach out to someone with your question, either staff or volunteer, and we will get you sorted out quickly.
Before you get started there are some things you will need to do.
Volunteer training will take you 2-3 hours depending on how fast a reader you are. It is a lot to get through and it is important that you remember the information contained in the training. For that reason it is recommended that you DO NOT do all the training in one sitting. Instead plan to spend 2 or 3 sessions on your training.
When you register for slack please add your skills / platform to your bio so that others know if they can ask you for help. This is a requirement. If we notice you have not added this information to your bio it is a sign to us that you have not read this Onboarding page. That's a no-no.
You may also wish to use the "status" setting to set your "work hours". A lot of our volunteers are using status to indicate to their teammates when they will be available.
There are some channels you are required to be a part of, this is to make communicating important information to you easier. Most business team channels are private. If you are added to a private channel please ensure you pay attention to the channel.
- Everyone: Please join #business-projectideas
- Designers: Please join #general-design
- Hatchlings: Please join #general-devhatchery as well as your platform channel (#dev-android, #dev-ios, or #dev-web)
- Mentors: Please join #general-devhatchery, and your platform channel. You are not required to answer questions in these channels but your presence is requested and answering questions is encouraged.
- Developers: You are not required to join any channels but it would be nice to see you at least in your platform channel
There are a lot of other channels you can join, explore! Don't forget to introduce yourself, a great place to do that is the #general channel :)
Please take a wander over to our organizational wiki. This wiki outlines all of our processes and procedures and should answer any questions you may have.
-
CodeDoesGood's Mission and Guiding Principles, Related articles:
-
CodeDoesGood Rules, Related article:
-
Project Boards Management Strategy, Related articles:
You may find these videos helpful also
- Using Freetio (not a required tool but one some people like to use)
- Using Slack
- Using Sourcetree
- Code of Conduct
- Organizational Structure
- Promotional Guidelines
- Communication
- Google Drive
- Dev Hatchery
- Qualifying Projects
You should become familiar with the other pages that are available so that you are not asking staff and volunteers questions which are answered in the wiki. You don't need to know the content by heart, but instead know where to find the answers to your questions. If you have questions which are not answered in the wiki reach out to staff on Slack (look at the Contact page if you do not know who to talk to).
- Read the "User Groups / Access Control / Shared Resources" document in Google Drive, it is located at CodeDoesGood > Org
- Ask your director or team lead what other documents you should be familiar with but in general please become familiar with all the documents in the CodeDoesGood>Org Google Drive folder so you are aware of what is in there.
Development and Design volunteers, when you start a project you are also required to read the following pages:
- Project Team Structure
- Git Procedures
- Google Drive
- Project Boards
- Making Estimates
- Managing Your Work
- Project Assignment
- Project Guidelines
- Project Wikis
- Pull Requests & Code Review
- Writing Tickets & User Stories
Developers only:
If you are a Lead Mentor or a mentor who plans to be a lead mentor please ensure you are familiar with the content of everything in Chapter 3 and Chapter 4.
The Dev Hatchery has its own wiki which you may find helpful. Included are articles about managing your time, dealing with imposters syndrome, what distributed authority means, and much much more. If you think of a topic that would be helpful to include in this wiki reach out to staff so that you can be added to the writing team! We would like the Dev Hatchery wiki to be written mostly by Hatchlings. This is because we recognize that new learners often learn best from others who are at a similar level as they are. Sometimes it can be hard to follow the language that a more experienced person might use. If you are a mentor or otherwise experienced developer and you want to add an article though you are more than welcome! Please contact the Dev Hatchery team lead.
Once you've gotten on Slack and become comfortable with the wikis it's time to get yourself on a project. Open projects will appear on your home page in the volunteer software when it is built. In the meantime while we are waiting for it to be built keep your eyes open on Slack for announcements as this is where you will find out about new projects.
The volunteer software is currently in development and it will be where all of our project and where volunteer profiles are kept.