emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@gnu.org>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: Payas Relekar <relekarpayas@gmail.com>,  emacs-orgmode@gnu.org
Subject: Re: Org ML integration with an existing Discourse instance
Date: Tue, 27 Sep 2022 23:01:18 +0200	[thread overview]
Message-ID: <87o7v0h6qp.fsf@gnu.org> (raw)
In-Reply-To: <87edvxnnqw.fsf@localhost> (Ihor Radchenko's message of "Tue, 27 Sep 2022 17:57:27 +0800")

Ihor Radchenko <yantar92@gmail.com> writes:

> The main question we need to answer is who is going to maintain that
> Discourse instance. AFAIU, Bastien is mainly concerned with the extra
> maintenance burden.

Not just this: I'm concerned with setting up a user-to-user discussion
space that reify a split between users (on a forum) and developers (on
the mailing list).

If a community-driven Discourse instance for Org emerges, that will be
a good thing: people could go there instead (or on top) of SO/reddit
if they don't want/like to interact on a mailing list.

If this instance is stable and useful enough and futur Org maintainers
feel like this should be advertized as forum.orgmode.org, they will be
able to do it of course.


  parent reply	other threads:[~2022-09-27 21:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-26  6:34 IM dev discussions? Payas Relekar
2022-09-26 15:33 ` Hendursaga
2022-09-27  9:57 ` Org ML integration with an existing Discourse instance (was: IM dev discussions?) Ihor Radchenko
2022-09-27 18:18   ` Tim Cross
2022-09-27 18:49     ` Bruce D'Arcus
2022-09-27 19:37       ` Tim Cross
2022-09-28  3:27     ` Ihor Radchenko
2022-09-27 21:01   ` Bastien [this message]
2022-09-28  1:10     ` Org ML integration with an existing Discourse instance Timothy
2022-09-28  6:27       ` Bastien
2022-09-29  3:54         ` Ihor Radchenko
2022-09-27 20:57 ` IM dev discussions? Bastien
2022-09-28  1:22   ` Ihor Radchenko
2022-09-28  6:55     ` Bastien

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:

  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=87o7v0h6qp.fsf@gnu.org \
    --to=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=relekarpayas@gmail.com \
    --cc=yantar92@gmail.com \


* 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


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