From: ian martins <email@example.com> To: ian martins <firstname.lastname@example.org>, Org-Mode mailing list <email@example.com> Subject: Re: Concerns about community contributor support Date: Wed, 21 Apr 2021 11:31:54 -0400 [thread overview] Message-ID: <CAC=rjb5yh5+0gpouNG4z82T2NURb+bbc6nbOKfSa4UvpCVuKzQ@mail.gmail.com> (raw) In-Reply-To: <firstname.lastname@example.org> [-- Attachment #1: Type: text/plain, Size: 1382 bytes --] On Wed, Apr 21, 2021 at 9:27 AM Eric S Fraga <email@example.com> wrote: > > On Wednesday, 21 Apr 2021 at 12:55, ian martins wrote: > > 1. A patch looks useful to me, but I feel I don't know if it's a good > > [...] > > > "Thanks for submitting this. I'd use it. Hopefully a maintainer > > will take a look." > > Ian, > > I think you will find that a few of us do post answers like this every > now and again. I know that I do. > I didn't mean to imply that you or anyone else never does this. I actually don't do it myself, and on reflection I believe it is for the reasons I listed above (a patch may look helpful but I don't know for sure that it'll be good overall, or it applies to a part of the code that I've not looked at). I thought others might have the same reasons for not responding. The lack of answers to cases 2 & 3 are essentially showing a lack of > interest which is basically an (implicit) answer as well. It may seem > dismissive but, given the volume of email some of us have to deal with > in our day job, it's just reality, I would suggest, without it meaning > to be judgemental in any way. > Lack of interest /is/ an implicit answer. The question is if that is a good way to answer. I agree with Timothy that ignoring newcomers' first attempt at contribution is an effective way to drive people away. Is that worth it in order to reduce email? [-- Attachment #2: Type: text/html, Size: 2013 bytes --]
next prev parent reply other threads:[~2021-04-21 15:33 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 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 [this message] 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=rjb5yh5+0gpouNG4z82T2NURb+bbc6nbOKfSa4UvpCVuKzQ@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).