Skip to content

Commit

Permalink
people: provide some text from the other angle
Browse files Browse the repository at this point in the history
Closes #108
  • Loading branch information
bagder committed Jun 17, 2023
1 parent e2bea9f commit a273184
Show file tree
Hide file tree
Showing 3 changed files with 30 additions and 1 deletion.
11 changes: 11 additions & 0 deletions people/ask-unpaid.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,3 +14,14 @@ This is not something that you can easily change. If you are the one asking
the question: be aware and be grateful that people are actually helping you
out. If possible, check if you can pay for support or maybe make your company
a sponsor of the project as a show of your good will.

## When you ask

Remember that when you ask a developer or a team of developers to do something
or to implement a feature in a project, it is a request, a wish, a desire, to
see something change. You must understand that they may not agree that your
idea is good. Their goals may not be aligned with yours. Also, unless you have
a contract or offer to pay for their services, chances are they are spending
spare time on development. If you ask in a professional role or as a
representative of a company, you might be doing this on paid time while they
are not.
11 changes: 11 additions & 0 deletions people/insulting.md
Original file line number Diff line number Diff line change
Expand Up @@ -26,3 +26,14 @@ those who have done nothing to deserve it.
This way of delivering a message is bad and wrong, but you should still be
prepared that it will happen.

## When you provide the feedback

Take a deep breath. Do not write that email if you still feel upset. Consider
that the author of the tool most likely did their best even if you found a
problem. They may have not considered your use case. They spent countless
spare time hours and shared their code in the open for everyone to use.

The least you can do is to be friendly and courteous when communicating. It
also goes for when you report bugs and even if the people in the other end
snap back at you or seem to imply that you are stupid. You can take the high
ground.
9 changes: 8 additions & 1 deletion people/negative.md
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
## Negative feedback
# Negative feedback

When writing and participating in Open Source projects, you can get quite a
lot of feedback due to the open and publicly accessible nature of what you are
Expand All @@ -17,3 +17,10 @@ When it works, people are silent. When something fails, the crowds roar.

It is good that you get to know about the problems, then you can work on
fixing them!

## When you provide the feedback

As a user of Open Source, we should strive to remember to also tell developers
and creators that we appreciate their hard work when things are working great
and when the projects solve our problems as intended. We do not have to wait
for things to fail to provide feedback.

0 comments on commit a273184

Please sign in to comment.