You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Building an Inner Source community requires create a safe space of collaboration, communication and work. This space should be bounded with a set of rules, standards, and responsabilities. This kind of things are usually defined in a Code of Conduct.
Defining a Code of Conduct within an InnerSource project is essential for fostering a welcoming and inclusive community environment. It sets clear expectations for behavior and establishes guidelines that promote respectful and collaborative interactions among project contributors. A well-crafted Code of Conduct helps prevent and address issues such as harassment, discrimination, and toxic behavior, ensuring that everyone feels safe and valued within the project. By providing a framework for positive and inclusive participation, a Code of Conduct encourages diverse perspectives, enhances collaboration, and ultimately leads to the development of higher-quality open-source software.
It is very common to have a CODE_OF_CONDUCT.md file as part of the repository of an InnerSource project, so it could be usefull to extend the Standar Base Documentation pattern including a reference about this file, its goals, and adding a template.
A good template can be an adapted version of the Code of Conduct provided by the Contributor Covenant, a very extended used by many communities and projects.
This issue is opened with the goal to extend the Standar Base Documentation pattern adding some references, and a template of a Code of Conduct. That it will help new InnerSource projects to accelerate the adoption, and promoting the collaboration with their communities.
The text was updated successfully, but these errors were encountered:
Building an Inner Source community requires create a safe space of collaboration, communication and work. This space should be bounded with a set of rules, standards, and responsabilities. This kind of things are usually defined in a Code of Conduct.
Defining a Code of Conduct within an InnerSource project is essential for fostering a welcoming and inclusive community environment. It sets clear expectations for behavior and establishes guidelines that promote respectful and collaborative interactions among project contributors. A well-crafted Code of Conduct helps prevent and address issues such as harassment, discrimination, and toxic behavior, ensuring that everyone feels safe and valued within the project. By providing a framework for positive and inclusive participation, a Code of Conduct encourages diverse perspectives, enhances collaboration, and ultimately leads to the development of higher-quality open-source software.
It is very common to have a
CODE_OF_CONDUCT.md
file as part of the repository of an InnerSource project, so it could be usefull to extend the Standar Base Documentation pattern including a reference about this file, its goals, and adding a template.A good template can be an adapted version of the Code of Conduct provided by the Contributor Covenant, a very extended used by many communities and projects.
This issue is opened with the goal to extend the Standar Base Documentation pattern adding some references, and a template of a Code of Conduct. That it will help new InnerSource projects to accelerate the adoption, and promoting the collaboration with their communities.
The text was updated successfully, but these errors were encountered: