From: Emanuel Berg via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Does Richard M. Stallman still scrutinize and develop the codes of Emacs now?
Date: Thu, 26 Aug 2021 00:25:32 +0200 [thread overview]
Message-ID: <87a6l5kvqb.fsf@zoho.eu> (raw)
In-Reply-To: YSYHoj9AoQHHqSzn@protected.localdomain
Jean Louis wrote:
> As Vim is extensible similarly as Emacs everybody can
> contribute to it by providing extensions.
>
> If software is useful, I don't see any problem if it would
> be developed by single person. That is how majority of
> projects starts.
>
> As it is free software you are free to fork and build upon
> it if there is no possibility where you could, instead of
> forking it yourself, contribute collaboratively.
If a single person does it, that isn't at problem as long as
no one else wants to do it. Then it is "reality".
If a single person does it, and the rest cannot do it except
for forking it and become another "single person doing it",
that's a _huge_ problem and that model is unlikely to be
successful as it would require a brilliant person who can
accomplish wonders with no help from anyone else.
--
underground experts united
https://dataswamp.org/~incal
next prev parent reply other threads:[~2021-08-25 22:25 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-15 6:46 Does Richard M. Stallman still scrutinize and develop the codes of Emacs now? Hongyi Zhao
2021-08-15 6:55 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-15 7:02 ` Jean-Christophe Helary
2021-08-15 7:15 ` Hongyi Zhao
2021-08-15 7:21 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-15 7:39 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-15 7:17 ` Eli Zaretskii
2021-08-15 7:35 ` Hongyi Zhao
2021-08-15 7:42 ` Hongyi Zhao
2021-08-15 8:08 ` Eli Zaretskii
2021-08-15 8:22 ` Hongyi Zhao
2021-08-15 8:29 ` Stephen Berman
2021-08-15 8:41 ` Hongyi Zhao
2021-08-15 9:28 ` Teemu Likonen
2021-08-15 11:54 ` Hongyi Zhao
2021-08-15 12:45 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-15 13:03 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-21 22:05 ` Wayne Harris via Users list for the GNU Emacs text editor
2021-08-22 0:53 ` Jude DaShiell
2021-08-22 1:02 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-22 1:14 ` Jude DaShiell
2021-08-22 1:28 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-22 7:03 ` tomas
2021-08-22 7:35 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-22 17:05 ` Samuel Banya
2021-08-22 17:17 ` Eli Zaretskii
2021-08-22 17:49 ` Arthur Miller
2021-08-22 19:15 ` Samuel Banya
2021-08-23 18:16 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-23 21:01 ` Tim Johnson
2021-08-25 9:04 ` Jean Louis
2021-08-25 22:25 ` Emanuel Berg via Users list for the GNU Emacs text editor [this message]
2021-08-22 13:43 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-15 10:08 ` Arthur Miller
2021-08-19 6:13 ` Jean Louis
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=87a6l5kvqb.fsf@zoho.eu \
--to=help-gnu-emacs@gnu.org \
--cc=moasenwood@zoho.eu \
/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.