From: Tim Cross <email@example.com> To: firstname.lastname@example.org Subject: Re: Concerns about community contributor support Date: Thu, 22 Apr 2021 05:35:25 +1000 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <CAF-FPGMr46vnWbp6=60u9Dz_R9cJgK6u_HaTHe1r4FXF5SfrKw@mail.gmail.com> "Bruce D'Arcus" <firstname.lastname@example.org> writes: > I've been thinking about this general issue over the past year, as > it's a common problem regardless of project, hosting platform, etc. > > I do agree in general that situations where submission of ideas and > patches languish without attention are a problem. > > But while I don't think there are any easy answers, I do think clarity > upfront can help. > > For example, perhaps there needs to be a prominent statement early on > this page, which states upfront how the community vets new ideas or > patches, what someone who submits such can expect, including in terms > of timeline, and how to interpret lack of response? > > https://orgmode.org/worg/org-contribute.html > Yes, we can certainly help manage expectations, which I think is going to be more effective. At the very least, it is a good place to start. Perhaps it would be worthwhile if everyone interested in this issue have a look at what is on worg about contributing and propose some additions/updates? Responding to essentially just flag you have seen the patch message really only adds noise and may even 'drown out' those responses which add real 'value' to any discussion. I also doubt that asking people to do this would actually result in any actual change of behaviour by subscribers. -- Tim Cross
next prev parent reply other threads:[~2021-04-21 19:45 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 2021-04-21 15:38 ` Bruce D'Arcus 2021-04-21 19:35 ` Tim Cross [this message] 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 \ --email@example.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).