Code of conduct

This Code of Conduct covers our behavior as members of the FINkers United Community, in any forum, mailing list, wiki, website, bug, event, public meeting or private correspondence. The FINkers United Community Steering Committee will arbitrate any dispute over the conduct of a member of the community.
Be considerate.

Our work is used by other people, and we in turn depend on the work of others. Any decision we take affects others, so we take these consequences into account when making decisions. Even if it’s not obvious, contributions to FINkers United impact the work of others. For example, changes to code, infrastructure, policy, documentation, and translations during a release may negatively impact others’ work. Be considerate to others.

Be respectful.

The FINkers United community and its members treat one another with respect. Everyone can make a valuable contribution. We may not always agree, but disagreement is no excuse for poor behavior. We cannot allow frustration to turn into more than that. Remember that a community where people feel uncomfortable or threatened is not a productive one. Be respectful when dealing with other contributors as well as with people outside the community.

Be collaborative.

Collaboration is central to FINkers United and to the larger free software community. Collaboration reduces redundancy, and improves the quality of work. Internally and externally, we are always open to collaboration. Wherever possible, we work closely with upstream projects and others in the free software community to coordinate technical, advocacy, documentation, and other work. Any work is done transparently and should involve as many interested parties as early as possible. Be collaborative.

Cross-check with others when you disagree.

Disagreements, both social and technical, happen all the time. It is important we solve disagreements and differing views constructively and with the help of the community. We have the Steering Committee, project maintainers and a series of other governance bodies which help to decide the right course of action. When goals differ, we encourage people to fork the relevant code, so that the community can test new ideas and contribute to the discussion. Cross-check with others when you disagree.

Ask for help if unsure.

Nobody knows everything, and nobody is expected to be perfect. Asking questions avoids many problems down the road, and so questions are encouraged. Use the forum to find the desired responses. Ask for help if unsure.

Step down considerately.

Members can come and leave at any point in time. When somebody leaves or disengages, in whole or in part, we ask that they do so in a way that minimizes disruption to the project. Tell people you are leaving and take the proper steps to ensure that others pick up where you left off. Step down considerately.

Mailing lists and web forums.

Mailing lists and the forum are essential for the community. So:

1. Please use a valid email address where you can be reached.
2. Please avoid flamewars, trolling, personal attacks, and repetitive arguments. On technical matters, the project maintainers can make a final decision. On matters of community conduct, the Steering Committee can make a final decision.

We use cookies to deliver a cosy experience on our website.

 

The website is built over Wordpress and it uses plugins to display content as intended.

 

By accepting this notice, you consent to cookies on this device as per our Cookie Policy.

Some contents or functionalities here are not available due to your cookie preferences!

This happens because the functionality/content marked as “%SERVICE_NAME%” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.