Support Ukraine Black Lives Matter

Ember Community Guidelines

Our Community Guidelines / Code of Conduct is designed to make it clear that we believe in tolerance, respect, inclusion and hard work. We’ve built a tremendously impressive community of good people, and our goal is to continue growing along the same trajectory.

The internet is full of codes of conduct, employee guidelines, community charters and then some. We’ve custom-written some bits of ours, but for a lot of this, borrowed from people, companies and projects that have already done solid jobs at this very task (see our reference list below). No part of this is an endorsement of any of these people, companies or projects—simply us acknowledging that the specific language we’re referencing seems to mirror our own ideals and intentions.

General Goals

We strive to:

  1. Be open: We invite anybody, from any company or from no company, to participate 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.
  2. Be empathetic and respectful: We work together to resolve conflict, assume good intentions and do our best to act in an empathetic fashion. We don’t allow frustration to turn into a personal attack. A community where people feel uncomfortable or threatened is not a productive one. We expect community members to resolve disagreements constructively.
  3. Be collaborative: Collaboration reduces redundancy and improves the quality of our work. We prefer to work transparently and involve interested parties as early as possible. Wherever possible, we work closely with other projects to coordinate our efforts.
  4. Be pragmatic: Nobody knows everything! Asking questions early avoids problems later, so questions are encouraged, though they may be directed to the appropriate forum. Those who are asked should be responsive and helpful.
  5. Step down considerately: Members of every project come and go. When somebody leaves or disengages from the project or community, we ask that they do so in a way that minimizes disruption to the rest. They should tell people they are leaving and take the proper steps to ensure that others can pick up where they left off.
  6. Take responsibility for our words and our actions: We can all make mistakes; when we do, we take responsibility for them. If someone has been harmed or offended, we listen carefully and respectfully, and work to right the wrong.

Diversity: Everyone is Welcome

We are committed to being a community that everyone feels good about joining. Although we may not be able to satisfy everyone, we will always work to treat everyone well.

We’ll avoid a laundry list of all the things you may and may not be, what classes are legally protected, etc. Whoever you are, wherever you’re from, whatever you look like or identify as, believe in or don’t believe in, know that you’re welcome.

Leadership, Authority and Responsibility

The following list expresses some of our many intentions on these topics:

  1. Setting the direction: The ultimate direction of Ember comes from our "benevolent dictators," who delegate specific responsibilities and the corresponding authority to a series of teams and individuals. Currently, the primary group of people directing the project (and with the ability to approve and make substantial changes) is known as the Ember Core Team. The Ember Core Team is a living body, with members added and removed as project and personal priorities shift. Leadership is not an award, right, or title; it is a privilege, a responsibility and a mandate, and one the Ember Core Team takes seriously.
  2. We delegate: Good leaders know when to delegate. The best leaders balance delegation with hard work of their own. Of course, leadership doesn’t mean that leaders delegate unpleasant work to others. Instead, leaders balance hard work on their own—leadership by example—with delegation to others. A leader's foremost goal is ensuring that their team members and team succeed.
  3. We lead by example: The Code of Conduct does not only apply to leaders; it applies to leaders more. Leaders do their very best to show more patience, more respect, and more civility than other members of the Ember community.
  4. We value discussion, data and decisiveness: We gather opinions, data and commitments from concerned parties before making decisions. Once a reasonable amount of research is performed and data collected, we do our best to move decisively and efficiently. If we make a mistake, we’ll go back and fix it.
  5. We give credit where it’s due: A good leader does not seek the limelight but aims to congratulate their team for the work they do. While leaders are frequently more visible than their team, leaders in the Ember Community use their visibility to highlight the great work of their team members and others.
  6. We’ll help however we can: If a community member has a concern, it should be brought to the Core Team. Know that we’ll do our best to help you out of any precarious of uncomfortable positions. Your happiness, productivity and peace of mind is a priority for us.

Conflicts of Interest

We expect leaders and community members to be aware when they are conflicted due to employment or other projects they are involved in, and abstain from or delegate decisions that may be perceived as self-interested.

When in doubt, ask for a second opinion. Perceived conflicts of interest are important to address; as a leader, act to ensure that decisions are credible even if they must occasionally be unpopular, difficult or favorable to the interests of one group over another.

This Code is not exhaustive or complete, nor is it a rulebook; it serves to express our common goals and sentiments about our community. We expect it to be followed in spirit as much as in the letter.

Source Materials

  1. Mozilla Code of Conduct
  2. Ubuntu Code of Conduct
  3. Twitter Code of Conduct

You’ll note a lot of language that appears in all three.


If you’d like to suggest tweaks to this page, submit a pull request. If you’d like to get in touch with someone on the Core Team with a question or concern related to our community guidelines or other larger concerns, email

As always, for issues, bug reports, pull requests, docs, etc., GitHub is still the right place to go.