From: Ihor Radchenko <yantar92@gmail.com>
To: Bastien <bzg@gnu.org>, Timothy <orgmode@tec.tecosaur.net>
Cc: Russell Adams <RLAdams@adamsinfoserv.com>, emacs-orgmode@gnu.org
Subject: Re: IM dev discussions?
Date: Tue, 27 Sep 2022 17:50:35 +0800 [thread overview]
Message-ID: <87k05pno2c.fsf@localhost> (raw)
In-Reply-To: <87illapti1.fsf@gnu.org>
Bastien <bzg@gnu.org> writes:
> Ihor Radchenko <yantar92@gmail.com> writes:
>
>> Maybe we can nicely ask moderators/active users of reddit/SO to redirect
>> people to Org ML when appropriate? Similar to our current effort with
>> contributor stewards.
>
> That's a very good idea!
>
> If these contributor stewards agree, we can even advertise their role
> on https://orgmode.org/worg/org-maintenance.html
Agree.
Which social website do you have in mind?
I can ask @alphapapa from /r/orgmode.
I guess we can also ask people hanging out on Doom discord and
discourse.
Maybe also Org roam people. They have discourse.
>> May we set a single account on GitHub and link it to Org ML so that
>> people can @mention Org team on GitHub, and we automatically get the
>> email directly to Org ML?
>
> I'm against it: it will make it easier for Org ecosystem maintainers
> on GitHub to send notifications to the Org ML without joining it while
> probably forcing Org maintainers on the ML to follow-up discussions on
> GitHub. That's not a positive outcome.
Fair point. GitHub email never displays comment edits, and I am not sure
how reliable is Github-to-email bridge for complex interactions.
> What I suggest instead to do is to document GitHub accounts of Org
> core maintainers on worg/org-maintenance.org for those who have one.
This sounds reasonable.
> This way maintainers of Org libraries on GitHub will know they can @
> these accounts in their issues. And it will stay the responsability
> of Org core maintainers to decide how to deal with these issues.
>
> For some of them, it will just lead to a reply on the issue (as when
> Org maintainers contribute to non-official Org spaces, like the Doom
> or spacemacs discord servers); for issues that are of importance for
> Org core development, we should suggest them to send an email to the
> list.
I am unsure how visible this kind of information will be for new
third-party package maintainers.
Should we add some information to Appendix A Hacking section of the
manual? (something along the lines that one may contact Org maintainers
in other media like IRC, Matrix, etc and then link to worg/org-maintenance.org)
Or maybe have a section in worg/org-contribute.org? An extension to
"Write add-ons" item.
And, of course, we need to announce this to the existing maintainers.
Upcoming Emacsconf may be a good opportunity.
--
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:54 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-19 22:57 orgmode.org welcome page says to install via MELPA but as writing, this cannot be done David Ventimiglia via General discussions about Org-mode.
2022-09-19 22:59 ` David Ventimiglia via General discussions about Org-mode.
2022-09-20 1:32 ` Bastien
2022-09-20 3:59 ` Ihor Radchenko
2022-09-20 5:36 ` Bastien
2022-09-20 5:41 ` Timothy
2022-09-20 7:50 ` Bastien
2022-09-20 9:22 ` IM dev discussions? (was: orgmode.org welcome page says to install via MELPA but as writing, this cannot be done) Ihor Radchenko
2022-09-20 12:11 ` Russell Adams
2022-09-21 8:05 ` Ihor Radchenko
2022-09-21 8:59 ` Russell Adams
2022-09-21 11:04 ` Russell Adams
2022-09-22 14:13 ` Ihor Radchenko
2022-09-22 15:52 ` IM dev discussions? Bastien
2022-09-22 23:07 ` Matrix (was Re: IM dev discussions?) Tim Cross
2022-09-23 2:38 ` Ihor Radchenko
2022-09-23 2:53 ` Tim Cross
2022-09-23 6:47 ` Bastien
2022-09-23 2:35 ` IM dev discussions? Ihor Radchenko
2022-09-23 6:39 ` Bastien
2022-09-23 10:10 ` Ihor Radchenko
2022-09-25 11:03 ` Bastien
2022-09-25 11:18 ` Timothy
2022-09-26 5:31 ` Bastien
2022-09-26 4:13 ` Ihor Radchenko
2022-09-26 5:57 ` Bastien
2022-09-27 9:50 ` Ihor Radchenko [this message]
2022-09-27 21:37 ` Bastien
2022-09-29 3:39 ` Ihor Radchenko
2022-09-24 1:44 ` Tim Cross
2022-09-24 2:12 ` Timothy
2022-09-24 6:56 ` Ihor Radchenko
2022-09-25 10:46 ` Bastien
2022-09-25 10:53 ` Timothy
2022-09-25 11:53 ` Fraga, Eric
2022-09-26 5:03 ` Bastien
2022-09-24 3:11 ` Mark Barton
2022-09-24 7:02 ` Ihor Radchenko
2022-09-24 13:26 ` Jean Louis
2022-09-25 10:33 ` Bastien
2022-09-25 10:59 ` Ihor Radchenko
2022-09-24 13:22 ` IM dev discussions? (was: orgmode.org welcome page says to install via MELPA but as writing, this cannot be done) Jean Louis
2022-09-25 3:36 ` Ihor Radchenko
2022-09-25 4:21 ` Timothy
2022-09-25 13:37 ` Russell Adams
2022-09-26 4:46 ` Ihor Radchenko
2022-09-26 6:29 ` IM dev discussions? Bastien
2022-09-27 9:51 ` Ihor Radchenko
2022-09-27 19:35 ` Bastien
2022-09-25 16:23 ` IM dev discussions? (was: orgmode.org welcome page says to install via MELPA but as writing, this cannot be done) zimoun
2022-09-22 14:43 ` orgmode.org welcome page says to install via MELPA but as writing, this cannot be done Bastien
2022-09-23 2:40 ` Ihor Radchenko
2022-09-23 6:31 ` Bastien
2022-09-22 15:07 ` Max Nikulin
2022-09-22 17:23 ` Bastien
2022-09-23 16:55 ` Max Nikulin
2022-09-23 16:59 ` Timothy
2022-09-24 3:16 ` Ihor Radchenko
2022-09-25 10:31 ` Bastien
2022-09-24 7:00 ` Bastien
2022-09-24 7:04 ` Timothy
2022-09-25 10:30 ` Bastien
2022-09-25 16:19 ` Timothy
2022-09-26 5:31 ` Bastien
2022-09-26 15:26 ` Eduardo Mercovich
2022-09-27 21:56 ` Bastien
2022-09-24 6:48 ` Bastien
-- strict thread matches above, loose matches on Subject: below --
2022-09-24 7:56 IM dev discussions? Payas Relekar
2022-09-26 6:34 Payas Relekar
2022-09-26 15:33 ` Hendursaga
2022-09-27 20:57 ` 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=87k05pno2c.fsf@localhost \
--to=yantar92@gmail.com \
--cc=RLAdams@adamsinfoserv.com \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=orgmode@tec.tecosaur.net \
/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).