In Linagora, we foster an open and welcoming environment to build Good Tech - ethical and open-source software. We build this Good Tech to have a maximum positive impact on people, society and the planet. We call this #GoodTech4Good. This is made possible by the support, hard work and enthusiasm of thousands of people, including those who create and use Linagora products.
We as contributors and maintainers pledge to making participation in our project and in our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
This code of conduct outlines expectations for participants in Linagora managed open-source communities, as well as for reporting unacceptable behavior.
We are committed to providing a welcoming and inspiring community for all.
Examples of behavior that contributes to creating a positive environment include:
- Using welcoming and inclusive language
- Being respectful of differing viewpoints and experiences
- Gracefully accepting constructive criticism
- Focusing on what is best for the community
- Showing empathy towards other community members
Examples of unacceptable behavior by participants include:
- The use of sexualized language or imagery and unwelcome sexual attention or advances
- Trolling, insulting/derogatory comments, and personal or political attacks
- Public or private harassments
- Publishing others' private information, such as physical or electronic address, without explicit permission
- Other conduct which could reasonably be considered inappropriate in a professional setting.
5 points of caution
- Use welcoming and inclusive languageUsing welcoming and inclusive language
Our communities welcome and support people of all backgrounds and identities. Remember that you may not communicate in someone else's primary spoken or programmed language, and others may not have your level of understanding.
- Respecting different perspectives and experiencesRespecting different perspectives and experiences
For the LINAGORA community to thrive, its members must feel comfortable and accepted. To do this, it is absolutely necessary to treat each other with respect. When disagreements arise, first assume that people have good intentions. By respecting other people, their work, their contributions, and assuming that people are well-intentioned, community members will feel comfortable and safe, which will result in increased motivation and productivity.
- Elegantly accepting constructive criticismElegantly accepting constructive criticism
Disagreements, whether political or technical, are common. The goal is not to avoid disagreements or criticism, but to resolve them constructively. You should look to the community for guidance in resolving disagreements and, if possible, consult with the team most directly involved. Think carefully before you take a criticism personally and turn it into a public argument. If you feel you or your work is under attack, take time to breathe before writing heated responses.
- Focus on what's best for the communityFocus on what's best for the community
The success and quality of open source software depends on collaboration. As a contributor, you should seek to collaborate with other members of the community, as well as with other communities that are interested in or depend on your work. Your work should be transparent and fed back into the community when it is available. Be sure to keep other community members informed of your work and publish it in a way that allows them to test it, discuss it, and contribute to your efforts.
As a user, your comments are important, as is their form. Poorly thought out comments can cause pain and demotivation for other community members, but thoughtful discussion of issues can bring positive results.
- Showing empathy to other community membersShowing empathy to other community members
Our community is made strong by mutual respect, collaboration and empathy. Sometimes there are situations where this principle must be upheld and other community members need help. If you witness others being assaulted, first consider how you can offer personal support.
If you feel the situation is beyond your ability to help individually, go to the victim privately and ask if some form of formal intervention is needed. Similarly, you should support anyone who appears to be in danger of burnout, whether due to work-related stress or personal issues.
Project Leaders are responsible for clarifying standards of acceptable behavior and shall take appropriate and fair corrective action in response to any instances of unacceptable behavior.
Project Leaders have the right and responsibility to remove, edit, or reject comments, code, wiki edits, issues, and other contributions that do not comply with this Code of Conduct, or to temporarily or permanently ban any contributor for other behaviors they deem inappropriate, threatening, offensive, or harmful.
Reporting problems with the code of conduct
We encourage all members of the community to solve problems on their own whenever possible. This helps to develop a broader and deeper understanding and, ultimately, a healthier interaction.
In the event that an issue cannot be resolved locally, please feel free to report your concerns by contacting info@LINAGORA.com. Your report will be handled according to the problem resolution process outlined in the Code of Conduct FAQ.
Reporting How to report
- Why the Code of Conduct is mandatory?
People and communities are the foundation of open source. Communities thrive on diversity of thought and the safety of its members. LINAGORA is committed to diversity and inclusion. All LINAGORA employees enjoy a safe work environment and a culture of mutual respect and accountability..
Our team members and open source partners should enjoy the same environment when collaborating on open source projects.
Although conduct issues are rare, when they do occur they are often very public and very passionate. It is best for the community to be prepared with:
- A clear and accessible code of conduct outlining the standards by which projects operate.
- A problem-solving process to address instances where these standards are not met.
- Why the Code of Conduct?
The LINAGORA Open Source Code of Conduct is adapted from the Contributor's Agreement and the TODO Group model, which embodies LINAGORA's values of equality, respect and inclusion.
- Why is it necessary to have it in all repositories?
Having one code and one process is both efficient and consistent - community members can participate in any LINAGORA-managed open source project and be confident that they know the standards and are supported by a robust process.
- How do I adopt this code into my project?
All LINAGORA projects are automatically covered by this code of conduct and issue resolution process. However, it is essential that all community members are aware of the code and process.
For this reason, all projects should link to this code of conduct in their README and/or CONTRIBUTING files.
- What is the process for addressing concerns raised?
Emails sent to firstname.lastname@example.org trigger the following process:
- Your message will be acknowledged within one business day.
- The next business day, a small team will be assembled to review your issue. This team will be as diverse as possible, given its size, and will call on others as necessary to obtain additional information and provide advice. The team will not include anyone directly involved in the issue raised.
- From there, the team will work with you and others involved to reach a conclusion. While the complexity of the issue will vary, the goal is to resolve it within five business days.
- All communications are confidential and very limited in distribution (within the LINAGORA organization).
- How the resolution committee works
Beyond the standards and values set forth in the Code of Conduct, issue review teams operate under the following principles:
- Wherever possible, let the community work it out. It is best for communities to self-correct.
- Value of contribution or status in the community is not relevant to the review. Key individuals have no more rights (either to abuse or to be protected from abuse) than other community members.
- Reviewers must act and be seen to act independently of the project(s) in question and Microsoft.