From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users@googlegroups.com
Subject: Communicating on the list
Date: Sun, 18 Dec 2022 19:41:39 +0100 [thread overview]
Message-ID: <Y59e4+Os6XTLJ7iT@ilbers.de> (raw)
Hello together,
I see that technical discussions on the list have led to tone escalation. I'd
like to ask everyone to keep the following points in mind while communicating
on this list:
* Keep a healthy signal-to-noise ratio
* Carefully read and compose the messages -- this will reduce confusion
* Technical solutions often involve trade-offs; satisfying all use cases is not
always possible; use case priority is very personal business; decisions
involve taste and this is ok so
* Keep respectful communication, avoid name calling, sarcasm and otherwise
hostile language
* Stay on-topic
I'd like to see this list welcoming and respectful to advance the Isar project
together.
With kind regards,
Baurzhan
reply other threads:[~2022-12-18 18:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y59e4+Os6XTLJ7iT@ilbers.de \
--to=ibr@radix50.net \
--cc=isar-users@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox