unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: Yuan Fu <casouri@gmail.com>, Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Review a blog post about emacs-devel
Date: Thu, 30 Apr 2020 19:42:03 +0300	[thread overview]
Message-ID: <01d7c1b8-446c-dcfc-b6ea-f04c93bb4bba@yandex.ru> (raw)
In-Reply-To: <04ADB630-EE50-450D-B7EC-DD115C242500@gmail.com>

Hi Yuan,

On 30.04.2020 18:19, Yuan Fu wrote:

>> On Apr 29, 2020, at 10:28 PM, Richard Stallman <rms@gnu.org> wrote:
>>
>> [[[ To any NSA and FBI agents reading my email: please consider    ]]]
>> [[[ whether defending the US Constitution against all enemies,     ]]]
>> [[[ foreign or domestic, requires you to follow Snowden's example. ]]]
>>
>> Would you please talk about "free software" or "libre software", not
>> "open source”?
>> [...]
>> Also, please don't use GitHub as a standard of comparison.  That would
>> promote GitHub, which is counter to what we aim to do.
>>
> 
> I removed “open source” since it’s not the main subject. I used GitHub as a comparison because it _is_ the most familiar workflow right now. I don’t think admitting the fact promotes GitHub. Also I wouldn’t say I used GitHub as a standard as comparison, but simply as another well-known workflow. Here is my edited first paragraph:
> 
> Emacs, /the/ editor we all use and love, has been running for decades, receiving contribution from hundreds of hackers along the way. Because it predates recent popular workflows (a.k.a GitHub and friends) by many years, you can’t do the usual thing—open issues, fork and make PR’s, etc. However, Emacs’s development workflow isn’t as tedious and difficult as many people imagines (in particular, you don’t need Gnus or deal with email in Emacs, or setup anything fancy).
> 
> 
>> Please don't promote Emacs Lisp packages that we don't have papers
>> to include in Emacs or GNU ELPA.  That includes Magit.
>>
> 
> I think we should promote all free software, non-selectively. Maybe the freedom of Magit is less secure because Jonas haven’t signed the assignment (yet); but I don’t think it’s enough difference to treat Magit differently.

These are good counter-points, so I think it's just fine if you make 
your post without honoring some of Richard's requests.

Swapping "open source" for "free software" is a good thing to do, though.



  reply	other threads:[~2020-04-30 16:42 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-27 20:58 Review a blog post about emacs-devel Yuan Fu
2020-04-27 21:31 ` Noam Postavsky
2020-04-27 21:37   ` Yuan Fu
2020-04-29  6:33 ` Colin Baxter
2020-04-29  6:49 ` Jean-Christophe Helary
2020-04-29 14:08   ` Yuan Fu
2020-04-29 14:51   ` Drew Adams
2020-04-29 16:14     ` Yuan Fu
2020-04-30  2:28 ` Richard Stallman
2020-04-30 15:19   ` Yuan Fu
2020-04-30 16:42     ` Dmitry Gutov [this message]
2020-04-30 15:52   ` Stefan Kangas
2020-04-30 16:26   ` 조성빈
2020-04-30 16:50     ` Stefan Kangas
2020-05-02 18:58       ` Yuan Fu
2020-05-05  7:56         ` Jean-Christophe Helary
2020-05-07 19:40           ` Yuan Fu
2020-05-15  2:57             ` Yuan Fu
2020-05-15  5:55               ` Clément Pit-Claudel
2020-05-15 16:22                 ` Yuan Fu
2020-05-15  6:52               ` Eli Zaretskii
2020-05-15 16:20                 ` Yuan Fu

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=01d7c1b8-446c-dcfc-b6ea-f04c93bb4bba@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=casouri@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=rms@gnu.org \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).