From: Ihor Radchenko <yantar92@gmail.com>
To: Tim Cross <theophilusx@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Concrete suggestions to improve Org mode third-party integration :: an afterthought following Karl Voit's Orgdown proposal
Date: Sun, 05 Dec 2021 22:55:16 +0800 [thread overview]
Message-ID: <87lf0z9k4r.fsf@localhost> (raw)
In-Reply-To: <87mtlf41xc.fsf@gmail.com>
Tim Cross <theophilusx@gmail.com> writes:
> - The suggested org mode in a browser example is unlikely to be
> acceptable to the FSF (or RMS). The FSF is very much against cloud
> based computing services or any web service which uses non-free
> Javascript (which is most of them and one of the many reasons Github
> is discouraged by the FSF).
You are not right. I am well aware about the freedom of computation and
proposed organise because it is not actually cloud-based. Organise is a
frontend. It is licensed under AGPL. AGPL is recommended by FSF for
network software.
> A number of the ideas proposed are good ideas for org mode generally -
> for example, a repository of reference documents which could be used for
> testing purposes would be extremely useful for org-mode development and
> testing. Likewise, any effort to clarify the syntax and remove any
> ambiguities is beneficial for org mode itself. However, the emphasis and
> priority needs to remain focused on org mode as a mode for Emacs. The
> use of org mode by other external programs is really outside (but
> related) to the project.
May you clarify which one of the proposed changes has insufficient
emphasis on org mode for Emacs? If you have concrete ideas for
improvement, feel free to propose them.
> As a consequence and to eliminate/remove potential conflicts with FSF
> philosophy and goals, it may be worth considering spinning off a
> separate project. which happens to use the same markup syntax, but is
> not a GNU project (though it would be good to still be GPL'd).
I think that's what Karl proposed? I created this thread with specific
purpose to adapt his ideas to Org mode as a free software under FSF.
> If you want ot get a feel for the sort of issues which could come up
> when trying to develop/support 3rd party tools, have a look at the
> recent thread on creating an LSP server for emacs-lisp. While I
> personally disagree with most of the fears raised by some contributors
> to that thread and disagree with RMS's view that such a server would not
> be in the best interests of Emacs, the thread does give you a sample of
> the sort of issues which could come up with efforts to support or
> encourage 3rd party libraries for org markup, much of which could be
> avoided if the work is clearly not part of, related to or supported by
> the main org-mode project.
I have looked through that thread. I do not think that it applies.
Implementing LSP server for Elisp will give little benefit for Emacs while
giving a "free" and large benefit to non-free software at the same time.
Our situation is different. What I propose in a nutshell is: (1) Improve
our technical documentation; (2) Improve our test coverage; (3) Attract
more users to Org mode. Everything gives benefits to Org. In addition to
better integration.
Best,
Ihor
next prev parent reply other threads:[~2021-12-05 14:54 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-05 7:35 Concrete suggestions to improve Org mode third-party integration :: an afterthought following Karl Voit's Orgdown proposal Ihor Radchenko
2021-12-05 9:16 ` Juan Manuel Macías
2021-12-05 10:24 ` Ihor Radchenko
2021-12-05 11:08 ` Juan Manuel Macías
2021-12-05 11:54 ` Heinz Tuechler
2021-12-05 12:08 ` Ihor Radchenko
2021-12-05 13:32 ` Tim Cross
2021-12-05 13:52 ` Bruce D'Arcus
2021-12-05 22:20 ` Tim Cross
2021-12-05 14:30 ` Ihor Radchenko
2021-12-05 22:39 ` Tim Cross
2021-12-08 13:47 ` Ihor Radchenko
2021-12-08 14:39 ` Tim Cross
2021-12-08 16:16 ` Dr. Arne Babenhauserheide
2021-12-08 17:07 ` Russell Adams
2021-12-08 19:22 ` Dr. Arne Babenhauserheide
2021-12-08 20:14 ` Russell Adams
2021-12-08 21:50 ` Tim Cross
2021-12-09 8:12 ` Dr. Arne Babenhauserheide
2021-12-08 21:25 ` Tim Cross
2021-12-09 8:07 ` Dr. Arne Babenhauserheide
2021-12-09 8:36 ` Timothy
2021-12-09 9:18 ` Ihor Radchenko
2021-12-09 10:46 ` Eric S Fraga
2021-12-09 15:21 ` Russell Adams
2021-12-09 16:25 ` Eric S Fraga
2021-12-09 21:15 ` Samuel Wales
2021-12-09 23:27 ` Dr. Arne Babenhauserheide
2021-12-10 2:42 ` Tim Cross
2021-12-10 6:08 ` Dr. Arne Babenhauserheide
2021-12-11 10:03 ` Ihor Radchenko
2021-12-11 21:19 ` Tim Cross
2021-12-06 19:41 ` Karl Voit
2021-12-05 18:59 ` Juan Manuel Macías
2021-12-05 23:24 ` Russell Adams
2021-12-06 5:57 ` Juan Manuel Macías
2021-12-06 6:02 ` Timothy
2021-12-06 7:24 ` Juan Manuel Macías
2021-12-06 10:04 ` Greg Minshall
2021-12-06 14:59 ` Juan Manuel Macías
2021-12-06 17:59 ` Tom Gillespie
2021-12-06 18:25 ` M. ‘quintus’ Gülker
2021-12-06 18:42 ` Russell Adams
2021-12-06 18:47 ` Timothy
2021-12-06 19:28 ` Russell Adams
2021-12-06 19:34 ` Timothy
2021-12-06 18:30 ` Russell Adams
2021-12-06 19:10 ` Gerry Agbobada
2021-12-08 12:56 ` Ihor Radchenko
2021-12-06 10:08 ` Greg Minshall
2021-12-06 19:45 ` Karl Voit
2021-12-07 11:08 ` Vincent Breton
2021-12-08 13:13 ` Ihor Radchenko
2021-12-08 13:30 ` Ihor Radchenko
2021-12-05 13:06 ` Tim Cross
2021-12-05 14:55 ` Ihor Radchenko [this message]
2021-12-05 18:54 ` Timothy
2021-12-06 11:08 ` Max Nikulin
2021-12-06 18:43 ` Russell Adams
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=87lf0z9k4r.fsf@localhost \
--to=yantar92@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=theophilusx@gmail.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.