emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@gmail.com>
To: Tim Cross <theophilusx@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Org ML integration with an existing Discourse instance (was: IM dev discussions?)
Date: Wed, 28 Sep 2022 11:27:32 +0800	[thread overview]
Message-ID: <87sfkcfaaj.fsf@localhost> (raw)
In-Reply-To: <86fsgcisim.fsf@gmail.com>

Tim Cross <theophilusx@gmail.com> writes:

> Given that Discourse is open source and free (in GNU sense being GPL
> v2), perhaps a better approach would be to try and get the FSF to host a
> Discourse server from GNU projects (not just org). This would be in
> addition to the mail lists hosting currently provided.

I think that it is premature to talk about this just yet.
As I stated in the subject, I am more interested in ML-Discourse
integration possibility. Preferably with an existing Discourse instance.

We can indeed have a community Discourse (hosted by FSF or some other
means). But it will not help with current fragmentation of the Org
community. Not adding yet another place for discussion.

> I think Discourse is an interesting take on things and I can see how it
> could be beneficial to org mode, but we need to be realistic about the
> costs and resources needed. We have to have a reasonable confidence
> regrading long-term viability (i.e. our ability to administer and
> resource the service). I think it would be a mistake to rely on a 3rd
> party provider unless we have high confidence that 3rd party will be
> able to resource and maintain a server over the long term.

I envision Org ML being a central hub of the Org community with ability
to access its portions from other platforms (like Discourse). Individual
platforms may or may not include the whole message traffic from Org ML.
The key point is making it easy to share Org core-related questions with
Org ML without compromising accessibility ML provides.

A number of people prefer using shiny new platforms these days. If those
platforms can be transparently connected to Org ML, we do not need to
worry about new trendy things dying out over a couple of years. Org ML
will still remain and record the relevant discussions in public inbox.
Yet, people who are cringy about using email will be able to communicate
with the core Org community.

Ihor Radchenko,
Org mode contributor,
Learn more about Org mode at https://orgmode.org/.
Support Org development at https://liberapay.com/org-mode,
or support my work at https://liberapay.com/yantar92

  parent reply	other threads:[~2022-09-28  3:27 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 [this message]
2022-09-27 21:01   ` Org ML integration with an existing Discourse instance Bastien
2022-09-28  1:10     ` 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=87sfkcfaaj.fsf@localhost \
    --to=yantar92@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=theophilusx@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).