Open Source

A supplemental goal of this Code of Conduct is to champion open source culture by encouraging team members to use open source and easily accessible tools as much as possible.
It is a matter of professional pride for us that we are open source champions and we would like to encourage all who work with us to pay it forward.


The following behaviors are expected and requested of all team members:

On Work style

Be pro-active, and help your team members out whenever you can. Collaboration reduces redundancy and improves the quality of our work. We like both. We are open to everyone participating in any aspect of our projects. Our community is open, and any responsibility can be carried by any contributor who demonstrates the required capacity and competence.
Be pragmatic: We encourage you to ask questions, and ask early in the process to avoid problems later. Be thoughtful and considerate when seeking out the appropriate channels for your questions - again, the varied team means not everyone may be able to answer your question fully. If you are asked a question be responsive and helpful, and if you can’t help then point them towards whoever you think can.
Ask for help. Your work may involve issues that start to frustrate you. When this happens, ask for help from others on the team. There’s a chance that there’s an easier approach to the problem, or another specialist to split the workload with, or that we can defer that issue temporarily (or even forever). Nobody wins if you spent countless hours battling a task that brings little user benefit.Nobody is expected to be perfect in this community, but you are expected to do all you can to ensure your projects move along smoothly and productively.
Step down considerately. Everything changes. If for any reason you need to leave or disengage from a project, we ask that you do so in a way that minimises disruption to the project and other team members. Please tell people you are leaving and take the proper steps to ensure that others can pick up where you left off.
Conflict of interest. We know you may have other employment, or other projects outside of Deep Blue C. Frankly we encourage it as it gives you the chance to bring new skills to your projects with us. We recognize that you may run into conflicts of interest as a result. We ask that you abstain or delegate decisions that may be seen to be self-interested. We expect that everyone who participates in the project does so with the goal of making life better for its users.When in doubt, ask for a second opinion. Perceived conflicts of interest are just as important to address. Act to ensure that decisions are credible even if they are unpopular, or difficult.

On working together

Be professional and patient with your team members, bearing in mind that many of them may not have the same skills and qualifications as you, or may be from different functional backgrounds altogether. They are part of the team because they’re good at something you're not, and the same applies to you.
Exercise consideration and respect in your speech and actions. Bear in mind, everyone is human, and they all deserve the same dignity.
Try collaboration before conflict. In any disagreement, assume good intentions, and act with empathy. The widely varied nature of our teams means disagreements are inevitable, due to people having different points of view from their different backgrounds. Do not turn disagreements into personal attacks.
Indisagreements, try to understand the reasons. Both social and technical disagreements, happen all the time, and need to be resolved constructively. Remember that the strength of our team comes from its diversity, people from a wide range of backgrounds, each with different perspectives on issues. Being unable to understand why someone holds a viewpoint doesn’t mean that they’re wrong. Don’t forget that it is human to err and blaming each other doesn’t get us anywhere. Instead, focus on helping to resolve issues and learning from mistakes.

On Community

Be mindful of your surroundings and of your fellow team members . Alert community leaders if you notice a dangerous situation, someone in distress, or violations of this Code of Conduct, even if they seem inconsequential.
Remember that our work is shared with a wide variety of people across many organizations. Please be respectful to all patrons of these organizations. As an open source organization, people use our work, and we depend on the work of others. Consider users, colleagues, patrons and collaborators before taking action. For example, changes to code, infrastructure, policy, and documentation may negatively impact others.


The following behaviors are considered harassment and are unacceptable within our community:


Demeaning, discriminatory, or harassing behavior and speech, violence, threats of violence or violent language directed against another person.ces.


Unwelcome sexual attention. This includes, sexualized comments or jokes; inappropriate touching, groping, and unwelcomed sexual advances.


Inappropriate physical contact. You should have someone’s consent before touching them.


Posting or threatening to post other people’s personally identifying information ("doxing").


Personal insults, particularly those related to gender, sexual orientation, race, religion, or disability.


Sexist, racist, homophobic, transphobic, ableist or otherwise discriminatory jokes and language.


Communicating sexually explicit or violent material.


Advocating for, or encouraging, any of the above behavior.


Deliberate intimidation, stalking or following (online or in person).


Inappropriate photography or recording.


Sustained disruption of company events, including talks and presentations.

This code is not exhaustive or complete. It serves to distill our common understanding of a collaborative, shared environment, and goals. We expect it to be followed in spirit as much as in the letter.

Consequences of
Unacceptable Behavior

Unacceptable behavior from any community member, including patrons and those with decision-making authority, will not be tolerated.
Anyone asked to stop unacceptable behavior is expected to comply immediately.
Project managers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
Project managers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to reassign or terminate any employee for other behaviors that they deem are not aligned with this code of conduct.


If you are subject to or witness unacceptable behavior, or have any other concerns, please notify your project manager as soon as possible. All reports will be handled with discretion.

In your report please include:

Your contact information.

Names of any individuals involved. If there are additional witnesses, please include them as well.

Your account of what occurred, and if you believe the incident is ongoing. If there is a publicly available record (e.g. an email archive or a public chat logs), please include details.

Any additional information that may be helpful.

Once you file a report, your project manager will deal with the incident, and/or forward it to Deep Blue C management, so someone higher up can contact you personally to review the incident, follow up with any additional questions, and make a decision as to how to respond.


If you feel you have been falsely or unfairly accused of violating this Code of Conduct, you should notify your project manager with a concise description of your grievance. Your grievance will be handled in the same fashion as the original report.


If there is any confusion regarding this code of conduct or it’s application, please address your questions to:
Ian Mayo,
This code of conduct is based on the Open Code of Conduct from Twitter. We all stand on the shoulders of giants across many open source communities. We are thankful for their work and all the communities who have paved the way with code of conducts.