From: Timothy <orgmode@tec.tecosaur.net>
To: emacs-orgmode@gnu.org
Cc: Ihor Radchenko <yantar92@gmail.com>,
Payas Relekar <relekarpayas@gmail.com>,
emacs-orgmode@gnu.org
Subject: Re: Org ML integration with an existing Discourse instance
Date: Wed, 28 Sep 2022 09:10:59 +0800 [thread overview]
Message-ID: <87leq4uwdd.fsf@tec.tecosaur.net> (raw)
In-Reply-To: <87o7v0h6qp.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 704 bytes --]
Hi Bastien,
> 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).
For what it’s worth, as a developer I’d be very interested in the ability of a
forum to categorise feature requests/bug reports/workflow discussions, etc.
> 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.
We could canvas reddit for example to see if the people currently on there would
be interested in an Org discourse.
All the best,
Timothy
next prev parent reply other threads:[~2022-09-28 1:22 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 ` Org ML integration with an existing Discourse instance Bastien
2022-09-28 1:10 ` Timothy [this message]
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=87leq4uwdd.fsf@tec.tecosaur.net \
--to=orgmode@tec.tecosaur.net \
--cc=emacs-orgmode@gnu.org \
--cc=relekarpayas@gmail.com \
--cc=yantar92@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).