From: Ihor Radchenko <yantar92@gmail.com>
To: Payas Relekar <relekarpayas@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Org ML integration with an existing Discourse instance (was: IM dev discussions?)
Date: Tue, 27 Sep 2022 17:57:27 +0800 [thread overview]
Message-ID: <87edvxnnqw.fsf@localhost> (raw)
In-Reply-To: <878rm6wsfv.fsf@gmail.com>
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.
--
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
next prev parent reply other threads:[~2022-09-27 9:58 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 ` Ihor Radchenko [this message]
2022-09-27 18:18 ` Org ML integration with an existing Discourse instance (was: IM dev discussions?) 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 ` 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:
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=87edvxnnqw.fsf@localhost \
--to=yantar92@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=relekarpayas@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 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).