Code of Conduct

Welcome to our project! To ensure a welcoming, stable, and efficient environment for everyone, we ask all contributors and community members to adhere to the following guidelines.

1. Respectful and Guiding Communication

Our community thrives on collaboration and mutual support. When interacting with others, please keep the following in mind:

  • Use Neutral Language: Focus discussions on the project, the code, and the community as a whole, rather than on individuals.
  • Guide, Don't Blame: Comments and code reviews should be formulated to guide people or suggest constructive changes. Avoid language that blames, devaluates, or discourages others. Our goal is to uplift and improve together.
  • Seek Clarification: If a message or request is unclear due to language or cultural barriers, ask for clarification. It is better to seek understanding than to let frustration or misunderstandings hinder progress.

2. Beneficial and Stable Contributions

We strive to move the project forward while maintaining a reliable foundation for all users.

  • Benefit the Community: Changes must be beneficial to everyone using the project and improve the overall ecosystem.
  • Minimize Breakages: Avoid introducing changes that break existing projects unless absolutely necessary. If a breaking change is required, it must be thoroughly justified and discussed beforehand.
  • Communicate Early and Often: Inform the community before starting work on a new feature or significant change. Maintain open communication throughout the implementation process to ensure alignment and prevent unexpected surprises.

3. Efficient Use of Resources

This project is maintained by volunteers. To respect our maintainers' time and make the best use of our automated resources (such as limited CI credits), please ensure the following before submitting a Merge Request (MR):

  • Test Your Changes: All code must be locally tested to ensure it behaves as expected.
  • Final and Working: Only open an MR when your changes are in a final, working state and ready for review.
  • Resolve Linting Issues: Ensure your code passes all linting checks to maintain code quality standards and prevent unnecessary CI failures.