From: Bastien <bzg@gnu.org>
To: Timothy <orgmode@tec.tecosaur.net>
Cc: emacs-orgmode@gnu.org, Ihor Radchenko <yantar92@gmail.com>,
Payas Relekar <relekarpayas@gmail.com>
Subject: Re: Org ML integration with an existing Discourse instance
Date: Wed, 28 Sep 2022 08:27:26 +0200 [thread overview]
Message-ID: <87sfkc10a9.fsf@gnu.org> (raw)
In-Reply-To: <87leq4uwdd.fsf@tec.tecosaur.net> (Timothy's message of "Wed, 28 Sep 2022 09:10:59 +0800")
Hi Timothy,
Timothy <orgmode@tec.tecosaur.net> writes:
>> 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.
But then the ML and the forum would compete with each other from a
maintainer's point a view: the ones using solely the ML would not get
the same information than the ones using the forum.
>> 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.
Yes, but mentioning that this would not be "the" Org discourse (not
forum.orgmode.org), just "a" Org forum maintained by X for the benefit
of the whole Org community (which is not really a thing actually, just
a mental shortcut for "every Org user out there").
It would be a good outcome to have such a forum: I'd be more comfy
recommending users to ask questions there iff they don't want/like
sharing questions on the ML than recommending them using reddit and
the like.
All best,
--
Bastien
next prev parent reply other threads:[~2022-09-28 7:12 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
2022-09-28 6:27 ` Bastien [this message]
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=87sfkc10a9.fsf@gnu.org \
--to=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=orgmode@tec.tecosaur.net \
--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).