Open Source Contributor Covenant Managed by Ethical Source

The Evolution and Future of the Contributor Covenant

Effectively managing the technical aspects of open-source projects presents significant challenges. These difficulties are compounded by potential disagreements among contributors, who often possess strong convictions regarding their work. To establish clear guidelines for these communities, the Contributor Covenant was created by Coraline Ada Ehmke in 2014.

Origins and Adoption

Much like many initiatives within the open-source world, the Contributor Covenant began as a personal endeavor for Ehmke. Over time, its initial two versions have been embraced by prominent organizations. These include the CNCF, Creative Commons, Apple, Google, Microsoft, and the Linux project, alongside numerous other projects.

Transition to the Organization for Ethical Source

Currently, development is underway on version 3.0. The Organization for Ethical Source (OES), where Ehmke serves as a co-founder and executive director, will now assume responsibility for the project’s stewardship.

A Pioneering Document

“The Contributor Covenant was the first document of its kind – a code of conduct specifically for open-source projects – and it sparked considerable debate, a situation that persists even today,” Ehmke stated. “However, the Ruby community readily adopted both the concept and the document itself, and it subsequently spread to many other open-source projects and communities.”

Core Principles

The document’s central tenet is a commitment to ensuring a harassment-free experience for all participants. This inclusivity extends to individuals of any age, body size, disability, ethnicity, sex characteristics, gender identity, experience level, education, socio-economic status, nationality, appearance, race, caste, color, religion, or sexual orientation.

Evolving Enforcement Guidelines

Contributors are also expected to behave in ways that foster a diverse, welcoming, and open community. Over the past few years, enforcement guidelines have been added to assist community leaders in determining appropriate consequences for violations of the code of conduct, as Ehmke explained.

Addressing Criticism and Concerns

“I always attempt to identify constructive feedback, even within criticism, and make it actionable,” Ehmke said. “For years, a common criticism of the Contributor Covenant was the fear of permanent bans for minor infractions. This highlighted a legitimate concern about the potential severity of consequences imposed by project leaders.”

An "Exit to Community"

Ehmke characterizes the transfer of the Covenant to the OES as an “exit to community,” analogous to companies placing mature open-source projects under the guidance of a foundation. The OES boasts members with expertise in community management and project governance, which they will now contribute to the project more formally.

Future Development: A Toolkit Approach

Ehmke will remain involved in the Covenant’s evolution, but development will proceed under the OES’s established working group model. For version 3.0, the goal is to transform the Covenant into a “toolkit.” This will enable different communities to customize it to better align with their specific goals and values, while still adhering to the core ethical principles defined by the OES.

Industry Support

“Microsoft’s adoption of the Contributor Covenant demonstrates our dedication to cultivating healthy, diverse, and inclusive communities, as well as our desire to collaborate and build with others in the ecosystem,” stated Emma Irwin, a program manager within Microsoft’s Open Source Program Office. “I am pleased to contribute my expertise to the OES’s Contributor Covenant 3.0 working group.”