emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eduardo Ochs <eduardoochs@gmail.com>
To: Karl Voit <news2042@karl-voit.at>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: Orgdown: negative feedback & attempt of a root-cause analysis (was: "Orgdown", the new name for the syntax of Org-mode)
Date: Tue, 30 Nov 2021 19:50:13 -0300	[thread overview]
Message-ID: <CADs++6jELyuCOyEGUccoRYrxC2WFdxgNc30XY9btO==KyZTUMg@mail.gmail.com> (raw)
In-Reply-To: <2021-11-30T21-02-53@devnull.Karl-Voit.at>

On Tue, 30 Nov 2021 at 17:46, Karl Voit <devnull@karl-voit.at> wrote:
>
> I chose an in-between approach: defining only a minimal set (name,
> common structure/idea/documentation, Orgdown1, providing a
> collaborative home on GitLab) and hope for a project community that
> will take over (or at least support) from there, discussing syntax
> elements for Orgdown2 and taking the project to its next logical
> steps.
>
> In hindsight, this decision was wrong.
>
> Quite frankly, I don't have the energy to throw away everything and
> start from zero with a different name.
>
> People do not seem to realize what it took to get there - which is
> partly understandingly because I had to learn by doing what it takes
> to get the idea into a coherent and consistent form.
>
> Simply switching to a different name is not just search&replace. It
> would reset the project almost to its very start again, losing the
> go-live effect of previous weekend (whose effect might be
> questionable considering the name discussion), its project URL that
> is now out there, the motivation video which aims to explain the
> motivation to users of Emacs, the EmacsConf21 talk publicity, and it
> would require much effort to reach the status where Orgdown is now.


Hi Karl,

I was at the EmacsConf2021, but I was totally exhausted due to other
chores and spoke to very few people there...

I think that your work is VERY important. I am one of the people who
have tried to learn Org lots of times and got stuck the same number of
times, and any initiative that splits the features - either syntactic
or semantics - into layers of different complexity and importance
will help me very much.

My suggestion about the name is: it's your project, changing its name
is not a trivial task, and the people who complained about the name
did not offer help. If I were you would simply put "find a better name
for the project and change its name to it" in my TODO list as a
low-priority task.

  Cheers =),
    Eduardo Ochs
    http://angg.twu.net/#eev
    https://emacsconf.org/2021/talks/test/


  parent reply	other threads:[~2021-11-30 22:51 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-28 19:46 "Orgdown", the new name for the syntax of Org-mode Karl Voit
2021-11-28 21:34 ` Jean-Christophe Helary
2021-11-28 21:39   ` Bruce D'Arcus
2021-11-28 21:50     ` Tom Gillespie
2021-11-28 22:25 ` Juan Manuel Macías
2021-11-28 22:57   ` Tom Gillespie
2021-11-28 23:16     ` Joost Kremers
2021-11-29  1:36       ` George Mauer
2021-11-29  3:25       ` Juan Manuel Macías
2021-11-29  7:13         ` Dr. Arne Babenhauserheide
2021-11-28 23:24     ` Jean-Christophe Helary
2021-11-29  3:25       ` Devin Prater
2021-12-26 14:54       ` Jean-Christophe Helary
2021-11-29  5:41   ` Marcin Borkowski
2021-11-29 12:18     ` Juan Manuel Macías
2021-11-29 12:36       ` Marcin Borkowski
2021-11-28 22:42 ` Tim Cross
2021-11-29 13:19   ` Karl Voit
2021-11-29 15:12     ` Matt Price
2021-11-29 18:27     ` M. ‘quintus’ Gülker
2021-11-30  7:39       ` Marcin Borkowski
2021-11-30 20:44       ` Orgdown: negative feedback & attempt of a root-cause analysis (was: "Orgdown", the new name for the syntax of Org-mode) Karl Voit
2021-11-30 22:28         ` Dr. Arne Babenhauserheide
2021-11-30 22:50         ` Eduardo Ochs [this message]
2021-12-01  0:41         ` Tom Gillespie
2021-12-01  1:12           ` Tim Cross
2021-12-01  3:28           ` Orgdown: negative feedback & attempt of a root-cause analysis Juan Manuel Macías
2021-12-01 21:17         ` Orgdown: negative feedback & attempt of a root-cause analysis (was: "Orgdown", the new name for the syntax of Org-mode) M. ‘quintus’ Gülker
2021-12-02  6:50           ` Orgdown: negative feedback & attempt of a root-cause analysis Eric S Fraga
2021-12-01 23:43         ` Karl Voit
2021-12-02  1:44           ` Tim Cross
2021-12-02  2:12           ` George Mauer
2021-12-02  8:07           ` Greg Minshall
2021-11-29  2:22 ` "Orgdown", the new name for the syntax of Org-mode Jim Porter
2021-11-29  2:33   ` Michael Ashton
2021-11-29 12:38     ` Max Nikulin
2021-11-29 12:58     ` Christophe Schockaert
2021-11-30 23:50 ` Samuel Wales
2021-11-30 23:56   ` Samuel Wales

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.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CADs++6jELyuCOyEGUccoRYrxC2WFdxgNc30XY9btO==KyZTUMg@mail.gmail.com' \
    --to=eduardoochs@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=news2042@karl-voit.at \
    /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/org-mode.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).