Re: Some ideas with Emacs

[Marcin Borkowski]

On 2019-12-03, at 05:58, Richard Stallman <address@hidden> 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. ]]]
>
>   > A _manual_ should be e.g. comprehensive (i.e., cover the whole of its
>   > subject).  A _book_ on a subject does not have to be so.
>
> I see the distinction you are making, but it doesn't affect our stance.

I see.

What about "non-free", paper-only books I asked about?

> Our principles of free documentation apply to any works that we would
> distribute or recommend to help people learn to use the software.
> Whether it is a manual meant to be complete, or a book that treats any
> choice of topics, if it doesn't carry a free license we ought not to
> refer users to it in any way.  What we ought to do is use or write
> some free documentation to explain the same methods and techniques.

Let me say that I admire your stance (even if I do not agree with it).
I have to say that being convinced about existence of objective moral
principles and defending them firmly is a rare thing nowadays.

>   > Could you define "political points which are outside the practical topic
>   > of the manual"?
>
> There is a precise criterion in the GFDL itself.

I see.

>   >   The FSF does refer to e.g. MS
>   > Windows (in the Emacs manual, of all places).  How is a CC-NC/CC-ND book
>   > (not "manual"!!!) worse than that?
>
> The Emacs manual does not recommend using Windows.  It refers to
> running Emacs on Windows to encourage Windows users to run Emacs.  We
> consider it ok to mention the existence of Windows because we expect
> users already know about it.  It is unlikely anyone will learn about
> the existence of Windows from the Emacs Manual and start using Windows
> as a result.

OK, that makes sense.

> See the section References in the GNU Coding Standards for the way
> we judge such questions.

I read the relevant part.  I think the crucial thing is (again) the
question whether such a book is "documentation" or not.  (In my opinion
it is not.)

> We have the motto that a nonfree program is worse than no program at
> all.  What does this mean?
>
> It is clear that a nonfree program might be of some practical use,
> whereas a nonexistent program is of zero practical use.  The point of
> this motto is precisely that we don't judge solely by practical use.
> Our goal is to win freedom, so we prize freedom over practical use.
> The nonfree program is not a contribution to the free world -- rather,
> it is a trap that we should help people climb out of.

While I do not agree with you here, I admit that this stance is
consistent.  And again, putting morality above practicality is something
I consider in general a rare and good thing.  (BTW, off the top of my
head, I can't think of any organization believing really firmly in its
principles and valuing them above pragmatism even against a majority
besides the Roman Catholic Church and the FSF.)

> The same applied to documentation (manuals or not).  Documentation simply
> means a work that teaches you how to use something.  I think the book
> you have in mind would be documentation.

As I mentioned above, my definition is different.  Let me try to
explain.  (This may be a bit oversimplified, but I want to convey the
general idea.  Also, I will use the word "free" in the sense you use it
to talk about software and documentation.)

Elisp Reference is documentation.  It contains everything you need to
understand Elisp.  Its purpose is to _teach Elisp_.  I think I agree
that documentation to free software should (in the moral sense) be free.

Elisp Intro is _not_ documentation, it is a textbook.  It contains
nothing new you could not learn or easily think up yourself after you
read and understood the Elisp Reference.  Its purpose is to teach Elisp
_in an easier and faster way_.  I think it is nice but not required
(again, in the moral sense) that a textbook about free software is free.

Now what I've written above is not strictly and logically correct:
formally, you don't _ever_ need documentation for free software, because
you have the source code.  So I would guess that there is some
subjectivity here - what is and what is not "documentation" depends on
the audience (a sufficiently advanced programmer does not need even the
Elisp Reference at all).  This problem might mean that either I am
wrong, or it makes sense to consider an "average user" or a similar
construct.

Notice that the "References" section to GNU Coding Standards
(https://www.gnu.org/prep/standards/standards.html#References), which
was mentioned earlier in this thread, seems to suffer from a very
similar problem when it uses the criterion of a non-free program or
system to be "well known".

> Would you please make your book free, so that it contributes?

I am considering this as one of the options.

>   > As an even more theoretical exercise, assume I wanted to write a book...
>   > called "Memoirs of an Emacs user", which would be an artistic
>   > representation of my process of Emacs and Org-mode gradually embracing
>   > my life;-) - possibly including practical tips on Emacs usage?  Would
>   > you mind talking about it here?
>
> A book like this would not be documentation -- at least, mostly not.
> It would be a sort of memoir.  I think CC-NC-ND is an acceptable
> license for a memoir, precisely because it is NOT documentation -- it
> does not have the purpose of teaching people practical skills or
> guiding them in doing a task.
>
> See https://gnu.org/philosophy/copyright-vs-community.html for more
> explanation.

Thanks for your explanation.  I will definitely read that document.

Best regards,

--
Marcin Borkowski
http://mbork.pl