From: ian martins <email@example.com> To: Org-Mode mailing list <firstname.lastname@example.org> Subject: Re: Concerns about community contributor support Date: Wed, 21 Apr 2021 08:55:57 -0400 [thread overview] Message-ID: <CAC=rjb7psWRQ-43Eg9XteUR3mxne0yiEE_86rYPrOeshCXv+ZQ@mail.gmail.com> (raw) In-Reply-To: <email@example.com> [-- Attachment #1: Type: text/plain, Size: 1808 bytes --] Timothy, thanks for raising this. I agree with everything you've said in this thread. I think it may be a hard problem to solve, but maybe we can start by just trying to improve. To be clear the problem I'm talking about is that potential contributors sometimes receive no response from the list. Maybe it could help to normalize somewhat generic responses. Here are some possible situations where we might not respond to a patch submission, followed by a potential response we might consider: 1. A patch looks useful to me, but I feel I don't know if it's a good idea for org in general, or maybe I think it is but I cannot apply the patch because (I'm not a maintainer, I don't have elisp experience, I haven't signed the copyright release, etc) "Thanks for submitting this. I'd use it. Hopefully a maintainer will take a look." 2. A patch does not look useful to me, but I can see how it may be useful to someone else and it was posted a while ago and no one has commented yet. "Thanks for submitting this. It looks like this affects an org feature that not many of us use. Sorry, but it might not get much attention." 3. A patch does not look useful to me, and can't imagine how it is useful in any context. "What is your use case?" These trite responses may be seen as mailing list noise, but I don't think so. They assure the patch submitter that their patch has been seen and at least for (1) they signal to maintainers that the patch would be useful to somebody. There are volunteer maintainers for the codebase, and volunteers who help with the mailing list. Maybe someone who wants to help with this could check Bark once in a while and respond to submissions that have been missed or post them to the list to put them in front of everyone again. [-- Attachment #2: Type: text/html, Size: 2087 bytes --]
next prev parent reply other threads:[~2021-04-21 12:57 UTC|newest] Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-16 18:43 Timothy 2021-04-17 23:29 ` Thomas S. Dye 2021-04-18 1:56 ` Tim Cross 2021-04-18 19:39 ` Timothy 2021-04-18 22:45 ` Tim Cross 2021-04-19 21:43 ` David Masterson 2021-04-19 22:21 ` Gustav Wikström 2021-04-23 0:16 ` David Masterson 2021-04-19 23:46 ` Tim Cross 2021-04-20 8:21 ` Tom Gillespie 2021-04-23 0:34 ` David Masterson 2021-04-20 9:28 ` Jean Louis 2021-04-23 0:38 ` David Masterson 2021-04-18 5:04 ` Timothy 2021-04-18 18:45 ` Thomas S. Dye 2021-04-18 19:12 ` Timothy 2021-04-18 19:46 ` Thomas S. Dye 2021-04-18 19:59 ` Timothy [not found] ` <a64adc3de7be49039372851ea31e4f7c@VI1PR0102MB3327.eurprd01.prod.exchangelabs.com> 2021-04-19 10:04 ` Eric S Fraga 2021-04-20 3:54 ` Timothy 2021-04-19 22:07 ` Gustav Wikström 2021-04-21 9:33 ` Jean Louis 2021-04-21 9:50 ` Tim Cross 2021-04-21 10:25 ` Heinz Tuechler 2021-04-21 12:55 ` ian martins [this message] 2021-04-21 13:07 ` Timothy [not found] ` <1c557c0e35e04440ba2dadfe57e5b590@VI1PR0102MB3327.eurprd01.prod.exchangelabs.com> 2021-04-21 13:27 ` Eric S Fraga 2021-04-21 15:31 ` ian martins 2021-04-21 15:38 ` Bruce D'Arcus 2021-04-21 19:35 ` Tim Cross 2021-04-22 0:36 ` ian martins 2021-04-22 0:48 ` Tim Cross 2021-04-22 2:35 ` Timothy 2021-04-22 5:14 ` Maintaining babel packages — a list of packages that need help? Dr. Arne Babenhauserheide 2021-04-22 10:10 ` ian martins 2021-04-26 7:25 ` Bastien 2021-04-22 10:00 ` Concerns about community contributor support ian martins 2021-04-21 19:31 ` Tim Cross 2021-04-25 4:30 ` Bastien 2021-04-25 5:52 ` Contributor Steward role (was Re: Concerns about community contributor support) Timothy 2021-04-25 7:13 ` Bastien 2021-04-25 6:17 ` Concerns about community contributor support Tim Cross 2021-04-25 7:19 ` Bastien 2021-04-26 0:23 ` Tim Cross 2021-04-26 5:00 ` Bastien 2021-04-26 6:07 ` Tim Cross 2021-04-26 7:34 ` Bastien 2021-04-25 10:10 ` Help with reproducing bugs reported on this list (was: Concerns about community contributor support) Bastien 2021-04-27 6:28 ` Help with reproducing bugs reported on this list Bastien 2021-04-25 21:40 ` Concerns about community contributor support Nick Savage 2021-04-26 7:22 ` Bastien 2021-04-29 14:07 ` D 2021-04-29 14:16 ` Bastien 2021-04-29 14:44 ` D 2021-04-29 14:29 ` Ihor Radchenko
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='CAC=rjb7psWRQ-43Eg9XteUR3mxne0yiEE_86rYPrOeshCXv+ZQ@mail.gmail.com' \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: Concerns about community contributor support' \ /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
Code repositories for project(s) associated with this 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).