|
| 1 | +## Title |
| 2 | + |
| 3 | +Code of Conduct |
| 4 | + |
| 5 | +## Patlet |
| 6 | + |
| 7 | +A healthy and inclusive InnerSource community requires strong levels of communications and interactions. |
| 8 | +Establishing a Code of Conduct provides guidelines for establishing rules and expectations regarding |
| 9 | +behavior and interactions within the community. |
| 10 | + |
| 11 | +## Problem |
| 12 | + |
| 13 | +InnerSource initiatives often involve collaboration among individuals and teams from diverse backgrounds |
| 14 | +and perspectives. The absence of clear rules of communication and interaction leaves room for ambiguity and |
| 15 | +potential conflicts within the InnerSource community. Without established guidelines, members may engage |
| 16 | +in behavior that is harmful, discriminatory, or counterproductive, leading to a breakdown in collaboration and trust. |
| 17 | + |
| 18 | +## Context |
| 19 | + |
| 20 | +Different individuals and teams within the organization collaborate in a healthy and inclusive community |
| 21 | +without conflicts. This welcoming, respectful and inclusive environment fosters more collaboration and |
| 22 | +creates trusted relationships across the organization where all community members feel safe and valued. |
| 23 | + |
| 24 | +## Forces |
| 25 | + |
| 26 | +A well-crafted Code of Conduct helps prevent and address issues such as harassment, discrimination, and |
| 27 | +other harmful behavior, ensuring that everyone feels safe and valued within the project. By providing the |
| 28 | +framework for positive and inclusive participation, the Code of Conduct encourages diverse perspectives, |
| 29 | +enhances collaboration, and ultimately leads to the development of higher-quality open-source software. |
| 30 | + |
| 31 | +## Solution |
| 32 | + |
| 33 | +Develop a Code of Conduct that outlines expected behavior, including guidelines for communication, collaboration, |
| 34 | +and conflict resolution. The Code of Conduct will articulate the shared values and principles of the |
| 35 | +InnerSource community, fostering a sense of belonging and common purpose, such as: |
| 36 | + |
| 37 | +- **Diversity**: InnerSource communities may consist of individuals with varying cultural backgrounds, beliefs, and communication styles. |
| 38 | +- **Trust**: Building trust among community members is essential for effective collaboration and knowledge sharing. |
| 39 | +- **Inclusivity**: A Code of Conduct and Social Contract can promote inclusivity by setting expectations for respectful behavior and interactions. |
| 40 | +- **Accountability**: Clear guidelines help hold community members accountable for their actions and contributions. |
| 41 | + |
| 42 | +## Implementation |
| 43 | + |
| 44 | +The adoption of well-known covenants, such as the [Contributor Covenant](https://www.contributor-covenant.org/), or |
| 45 | +the adaptation of some internal covenant for members of the organization are good starting points for |
| 46 | +implementation of this pattern. However, adopt the following life cycle can improve the implementation and |
| 47 | +adoption of the Code of Conduct in a InnerSource community: |
| 48 | + |
| 49 | +1. Collaboratively draft the Code of Conduct, involving input from community members representing diverse perspectives. |
| 50 | +2. Seek feedback and consensus from the community to ensure buy-in and ownership of the guidelines. |
| 51 | +3. Publish the finalized documents in a prominent location accessible to all community members, such as the InnerSource platform or collaboration tools. |
| 52 | +4. Regularly review and update the Code of Conduct as needed to reflect evolving community norms and values. |
| 53 | + |
| 54 | +A good practice for the third point is to share the Code of Conduct in each InnerSource community repository as a file |
| 55 | +named `CODE_OF_CONDUCT.md`. This file can be part of the [Standard Base Documentation](https://patterns.innersourcecommons.org/p/base-documentation) |
| 56 | +of any InnerSource project repository. |
| 57 | + |
| 58 | + |
| 59 | + |
| 60 | +## Resulting Context |
| 61 | + |
| 62 | +With a well-defined Code of Conduct in place, the InnerSource community can cultivate a culture of respect, trust, |
| 63 | +and collaboration. Community members feel empowered to contribute openly and engage in meaningful dialogue, |
| 64 | +leading to enhanced innovation and problem-solving. |
| 65 | + |
| 66 | +## Known Instances |
| 67 | + |
| 68 | +- Red Hat - Many of the internal communities |
| 69 | +- National Australia Bank - |
| 70 | + |
| 71 | +## Authors |
| 72 | + |
| 73 | +- Roman Martin Gil |
| 74 | + |
| 75 | +## Acknowledgments |
| 76 | + |
| 77 | +- Matt Cobby - Adding the National Australia Bank reference |
| 78 | + |
| 79 | +## Related Patterns |
| 80 | + |
| 81 | +- [InnerSource Commons Pattern - Standard Base Documentation](https://patterns.innersourcecommons.org/p/base-documentation) |
| 82 | +- [Open Practice Library - Social Contract](https://openpracticelibrary.com/practice/social-contract/) |
| 83 | +- [Contributor Covenant](https://www.contributor-covenant.org/) |
| 84 | + |
| 85 | +## Status |
| 86 | + |
| 87 | +- Initial |
0 commit comments