Skip to content

2. Rules

Jump to bottom
Abbey Jackson edited this page Jun 9, 2017 · 13 revisions

At CodeDoesGood we have policies and procedures but not many strict rules. The rules that are below are all things that are very important. So important in fact that if you do not follow them you could be removed from your project or team, or in exceptional circumstances you could be removed from CodeDoesGood as a whole.

It is important that our volunteers are responsible for themselves and are team players. There are certain things that we need in order to be able to operate successfully as a volunteer run organization and that is why these rules exist. If volunteers do not follow these rules they affect other people and will make it difficult for their teammates to be successful.

Slack

  • Crossposting: Cross-posting is considered as spam and discouraged. Please help to keep the channels clean and consistent with their intended purpose.
  • You must respond to messages and mentions on Slack. Slack is our communication tool.
  • 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.

Team Conduct

  • Leads are expected to be leaders, not managers. They should encourage and support their teammates, not manage them. No lead should ever discipline a volunteer, any disputes and issues should be referred to a director. Leads should aim to help their teammates work through issues together, as a team.

Media Engagement

  • Please do not approach media on your own without first speaking with a director.
  • Do not enter into arguments with any person, media outlet, or organization on behalf of CodeDoesGood. This is grounds for removal from CDG.

Google Drive

  • Do NOT create files when you are logged in with your own email address (this includes uploading files under your own email address). Please ask someone on the business team to create the file for you. Lead Mentors know how to create files properly so if you are on a project you can ask your Lead Mentor to do it. The reason for this rule is because all files on CodeDoesGood's Google Drive must be owned by CodeDoesGood. If you create a file when you are logged in under your own account you will be the owner, not CodeDoesGood.
  • Absolutely DO NOT give access to anyone's email address directly to any file.

Project Boards & Your Tickets/Tasks

  • In Progress Tickets must be updated WEEKLY. Even if the update is "no progress made this week". This is very very very important. The reason this is important is because if you do not update the ticket we do not know if you have worked on it, if you have forgotten it, if you are busy, or if you have gone MIA. We do not have time to track people down asking them to update their tickets. We will not remove you for missing a week, do not panic. But if you continue to skip weeks, and we have to talk to you about it many times, you will be removed from the project.

  • Do not use the "Issues" tab on Github. Instead use the "Projects" tab which will show you the Project board. If you use the Issues tab you will not be able to put the tickets into the correct column.

  • Please review https://github.com/CodeDoesGood/org/wiki/3.-Project-Boards

  • Include an estimate on your ticket whenever possible. Do not stress about this estimate. It is not important that you hit the estimate because it is an estimate not a deadline. What is important is that you update your ticket as soon as you know that you will not hit it so that other people on your team and other team leads and directors know when to expect the completed work.

General Conduct

Clone this wiki locally