From: Christopher Dimech via Emacs news and miscellaneous discussions outside the scope of other Emacs mailing lists <emacs-tangents@gnu.org>
To: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
Cc: Eshel Yaron <me@eshelyaron.com>, Emacs-tangents@gnu.org
Subject: Re: Blog post
Date: Thu, 14 Dec 2023 13:16:56 +0100 [thread overview]
Message-ID: <trinity-ba420a78-5337-4801-a256-9e9bf23cd675-1702556216316@3c-app-mailcom-bs13> (raw)
In-Reply-To: <877clhw2my.fsf@web.de>
> Sent: Thursday, December 14, 2023 at 9:29 PM
> From: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
> To: "Christopher Dimech" <dimech@gmx.com>
> Cc: "Eshel Yaron" <me@eshelyaron.com>, emacs-devel@gnu.org
> Subject: Re: Blog post
>
>
> Christopher Dimech <dimech@gmx.com> writes:
>
> > From your experience, have your rants been justified ? Introspection
> > of other people's rants should be considered part of the work. After
> > all, expletives towards demigods have occurred since time immemorial,
> > and will surely continue.
>
> Yes, they were totally justified — but usually not helpful. Most times
> they needlessly hurt people who then often stopped contributing. A
> friendly text may have helped to stay together and actually fix the
> problem to move forward as community. - Arne
Nobody gets hurt. It is commonly a type of vengeance (a form of
retaliation) intended to dissuade contrarian views directed towards
the developers.
The Gnu Project is built on the fundamental premise that software is for
the benefit of its users, not solely its developers. This perspective
emphasizes the importance of creating an inclusive and collaborative
community where users can contribute, share ideas, and provide feedback
without reprisals from developers - unlike what generally happens with
Proprietary Software Developers.
The "Information for Gnu Maintainers" states that when a developer receives
a report, the maintainers have to keep in mind that such reports are crucial
for our work - so always thank each person who sends a report.
This is not to say that a considerate peaceful problem solving should not
be the common way of approaching the developer team. Ultimately the job
of the maintainers is to exercise their authority so they can focus upon
improving the next version of the program. Stopping one's contribution
rather than exercising one's authority is Conflict Avoidance that shows
a Lack of Responsibility - a sign of failure.
----- Christopher Dimech
Administrator General - Chilkat Design Build - Naiad Informatics - Gnu Project
Society has become too quick to pass judgement and declare someone
Persona Non-Grata, the most extreme form of censure a country can
bestow.
In a new era of destructive authoritarianism, I support Richard
Stallman. Times of great crisis are also times of great
opportunity. I call upon you to make this struggle yours as well !
https://www.gnu.org https://www.fsf.org/
---
via emacs-tangents mailing list (https://lists.gnu.org/mailman/listinfo/emacs-tangents)
next prev parent reply other threads:[~2023-12-14 12:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-14 7:09 Blog post Eshel Yaron
2023-12-14 7:56 ` Christopher Dimech
2023-12-14 8:30 ` Dr. Arne Babenhauserheide
2023-12-14 9:22 ` Christopher Dimech
2023-12-14 9:29 ` Dr. Arne Babenhauserheide
2023-12-14 12:16 ` Christopher Dimech via Emacs news and miscellaneous discussions outside the scope of other Emacs mailing lists [this message]
2023-12-14 12:46 ` Dr. Arne Babenhauserheide via Emacs news and miscellaneous discussions outside the scope of other Emacs mailing lists
2023-12-14 13:11 ` Emanuel Berg
2023-12-14 16:20 ` Christopher Dimech via Emacs news and miscellaneous discussions outside the scope of other Emacs mailing lists
2023-12-14 17:01 ` Eli Zaretskii
2023-12-14 18:57 ` Christopher Dimech via Emacs news and miscellaneous discussions outside the scope of other Emacs mailing lists
2023-12-14 9:33 ` Eli Zaretskii
2024-01-10 23:14 ` Stefan Kangas
2024-01-11 9:26 ` Eshel Yaron
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=trinity-ba420a78-5337-4801-a256-9e9bf23cd675-1702556216316@3c-app-mailcom-bs13 \
--to=emacs-tangents@gnu.org \
--cc=arne_bab@web.de \
--cc=dimech@gmx.com \
--cc=me@eshelyaron.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.