From: Christopher Dimech via Emacs news and miscellaneous discussions outside the scope of other Emacs mailing lists <emacs-tangents@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: arne_bab@web.de, me@eshelyaron.com, Emacs-tangents@gnu.org
Subject: Re: Blog post
Date: Thu, 14 Dec 2023 19:57:53 +0100 [thread overview]
Message-ID: <trinity-5b436a7d-9fcd-4e9f-971e-fd18c1f4b50e-1702580273420@3c-app-mailcom-bs13> (raw)
In-Reply-To: <831qbora48.fsf@gnu.org>
> Sent: Friday, December 15, 2023 at 5:01 AM
> From: "Eli Zaretskii" <eliz@gnu.org>
> To: "Christopher Dimech" <dimech@gmx.com>
> Cc: arne_bab@web.de, me@eshelyaron.com, Emacs-tangents@gnu.org
> Subject: Re: Blog post
>
> > Cc: Eshel Yaron <me@eshelyaron.com>, Emacs-tangents@gnu.org
> > Date: Thu, 14 Dec 2023 17:20:56 +0100
> > From: Christopher Dimech via Emacs news and miscellaneous discussions outside the scope of other
> > Emacs mailing lists <emacs-tangents@gnu.org>
> >
> > I put the emphasis on the maintainers themselves to eliminate chaos within
> > their project. The latter could be the specific area where our opinions differ.
> > Users typically focus upon specific details, whereas software designers focus on
> > making everything work well together. From my experience, being a maintainer requires
> > a higher level of concentration and control of the external.
>
> It is quite clear to me from what you wrote above that your mental
> model and vision of maintainership of a project like Emacs are very
> different from the reality, starting from what does it mean to be a
> maintainer of such a project and what is its job description.
>
> Given that, your criticism is mostly off-mark.
Yes, my vision of maintainership of any project is much different.
---
via emacs-tangents mailing list (https://lists.gnu.org/mailman/listinfo/emacs-tangents)
prev parent reply other threads:[~2023-12-14 18:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m15y11tg4s.fsf@dazzs-mbp.home>
[not found] ` <trinity-0e15ff81-6901-4293-abff-454d399fb1e9-1702540610690@3c-app-mailcom-bs11>
[not found] ` <87bkatw58b.fsf@web.de>
[not found] ` <trinity-9c465c27-b800-41cb-b03f-8072d7be102f-1702545753141@3c-app-mailcom-bs13>
[not found] ` <877clhw2my.fsf@web.de>
2023-12-14 12:16 ` Blog post Christopher Dimech via Emacs news and miscellaneous discussions outside the scope of other Emacs mailing lists
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 [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=trinity-5b436a7d-9fcd-4e9f-971e-fd18c1f4b50e-1702580273420@3c-app-mailcom-bs13 \
--to=emacs-tangents@gnu.org \
--cc=arne_bab@web.de \
--cc=dimech@gmx.com \
--cc=eliz@gnu.org \
--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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).