https://bugs.kde.org/show_bug.cgi?id=321190

--- Comment #85 from André Martins <aan...@gmail.com> ---
The Free Software Movement depends on collaboration: it helps limit duplication
of effort while improving the quality of the software produced. In order to
avoid misunderstanding, try to be clear and concise when requesting help or
giving it. Remember it is easy to misunderstand emails (especially when they
are not written in your mother tongue). Ask for clarifications if unsure how
something is meant; remember the first rule — assume in the first instance that
people mean well.

As a contributor, you should aim to collaborate with other community members,
as well as with other communities that are interested in or depend on the work
you do. Your work should be transparent and be fed back into the community when
available, not just when KDE releases. If you wish to work on something new in
existing projects, keep those projects informed of your ideas and progress.

It may not always be possible to reach consensus on the implementation of an
idea, so don't feel obliged to achieve this before you begin. However, always
ensure that you keep the outside world informed of your work, and publish it in
a way that allows outsiders to test, discuss and contribute to your efforts.

Contributors on every project come and go. When you leave or disengage from the
project, in whole or in part, you should do so with pride about what you have
achieved and by acting responsibly towards others who come after you to
continue the project.

As a user, your feedback is important, as is its form. Poorly thought out
comments can cause pain and the demotivation of other community members, but
considerate discussion of problems can bring positive results. An encouraging
word works wonders.

[https://www.kde.org/code-of-conduct]

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to