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

Ihor Radchenko <yantar92@gmail.com> writes:

> Payas Relekar <relekarpayas@gmail.com> writes:
>> Perhaps we can check if it is indeed possible to bridge both Discourse
>> and mailing list seamlessly (or close enough). There are some issues
>> with extra chrome and clutter in discourse notifications, but these 2
>> links are what I found in 5 minutes of googling. A more thorough
>> research might just yield what we desire.
> 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.
> Can we simply reuse some of the existing discourse instances like Org
> Roam? Will the existing maintainers be interested to take this task?
> If we have a volunteer to run Discourse and setup the email bridge, I
> feel we can get something really useful.

It is largely about maintenance, but what about hosting? Discourse is
not free - either you have to pay or you have to self host. Where would
we self host?

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

  reply	other threads:[~2022-09-27 18:26 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 [this message]
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   ` 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=86fsgcisim.fsf@gmail.com \
    --to=theophilusx@gmail.com \
    --cc=emacs-orgmode@gnu.org \


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