Code of Conduct

Our Code of Conduct collects our expectations of good behavior as members of our Community, in any forum, website content, review, comment, public meeting or private correspondence. Darhon Software's moderators are ultimately accountable to the Community and will arbitrate in any dispute over the conduct of a member.

When we refer to collaboration, it includes submission of source code and patches for our open source software and any feedback about bugs, suggestions and observations related to our applications that can improve in some way the current and future releases. It also implies submission of translations, manuals, art works or any kind of documentation supporting our applications.

Be considerate

Our work, posts, comments and reviews will be used by other people, and we in turn will depend on the work of others. Any decision or action we take will affect users and colleagues, and we should take those consequences into account when making decisions and actions.

Be respectful

The Darhon community and its members treat one another with respect. Everyone can make a valuable contribution to Darhon. We may not always agree, but disagreement is no excuse for poor behaviour and poor manners. We might all experience some frustration now and then, but we cannot allow that frustration to turn into a personal attack. It's important to remember that a community where people feel uncomfortable or threatened is not a productive one. We expect members of the Darhon community to be respectful when dealing with other contributors as well as with people outside the Darhon project and with users of Darhon.

Be collaborative

Collaboration is important to Darhon. This collaboration reduces redundancy, and improves the quality of our work. Internally and externally, we should always be open to collaboration by testing beta applications, report bugs, provide feedbacks and submit code and documentation. Wherever possible, work closely with upstream projects to coordinate our efforts in all areas whether they be technical, advocacy or documentation. Our work should be done transparently and we should involve as many interested parties as early as possible. If we decide to take a different approach than others, we will let them know early, document our work and inform others regularly of our progress.


Disagreements, both social and technical, happen all the time and the Darhon community is no exception. It is important that we resolve disagreements and differing views constructively and with the help of the community and community processes. Consult others to discuss your ideas and clarify your doubts.

Look for help if you have doubts

Nobody knows everything, and nobody is expected to be perfect in the Darhon community. Asking questions avoids many problems down the road, and so questions are encouraged. Those who are asked questions should be responsive and helpful. However, when asking a question, care must be taken to do so in an appropriate forum.

Step down considerately

Members of every project come and go and Darhon is no different. When somebody leaves or disengages from the project, in whole or in part, we ask that they do so in a way that minimises disruption to the project. This means they should tell people they are leaving and take the proper steps to ensure that others can pick up where they left off.