Code of conduct
Our work will be used by other people, and we in turn will depend on the work of others. Any decision we take will affect users and colleagues, and we should take those consequences into account when making decisions. FINkers United has many users and contributors. Even if it’s not obvious at the time, our contributions to FINkers United will impact the work of others. For example, changes to code, infrastructure, policy, documentation, and translations during a release may negatively impact others’ work.
The FINkers United community and its members treat one another with respect. Everyone can make a valuable contribution to the FINkers United project. We may not always agree, but disagreement is no excuse for poor behavior 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 FINkers United community to be respectful when dealing with other contributors as well as with people outside the FINkers United project and with users of FINkers United products.
Collaboration is central to FINkers United and to the larger free software community. This collaboration involves individuals working with others in teams within FINkers United, teams working with each other within FINkers United, and individuals and teams within FINkers United working with other projects outside. This collaboration reduces redundancy, and improves the quality of our work. Internally and externally, we should always be open to collaboration. Wherever possible, we should work closely with upstream projects and others in the free software community to coordinate our technical, advocacy, documentation, and other work. 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 FINkers United 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. We have the Steering Committee, our Project Maintainers and a series of other governance bodies which help to decide the right course for FINkers United. There are also several Project Teams and Team Leaders, who may be able to help us figure out the best direction for FINkers United. When our goals differ dramatically, we encourage people to fork the relevant code, so that the community can test new ideas and contribute to the discussion.
Nobody knows everything, and nobody is expected to be perfect in the FINkers United 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.
Members of every project come and go and FINkers United 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 minimizes 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.
We pride ourselves on building a productive, happy and agile community that can welcome new ideas in a complex field, and foster collaboration between groups with very different needs, interests and goals.
Mailing lists, Newsgroups and our web forums are an important part of the FINkers United community platform. This code of conduct applies to your behavior in those forums too. Please follow these guidelines in addition to the general code of conduct:
1. Please use a valid email address to which direct responses can be made.
2. Please avoid flamewars, trolling, personal attacks, and repetitive arguments. On technical matters, our Project Maintainers can make a final decision. On matters of community conduct, the Community Steering Committee can make a final decision.