From: Tim Cross <email@example.com> To: Bastien <firstname.lastname@example.org> Cc: email@example.com Subject: Re: Concerns about community contributor support Date: Mon, 26 Apr 2021 16:07:10 +1000 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <email@example.com> Bastien <firstname.lastname@example.org> writes: > Hi Tim, > > thank you very much for your detailed answer. > > Tim Cross <email@example.com> writes: > >> Yes, but with some caveats. > > Thank you! > >> For these reasons, I'm probably not the best person to assist with the >> review and guidance for patches aimed at adding/extending functionality. > > The role of a "contributor steward" is to address the issues Timothy > originally raised about contributors not receiving answers when they > take the time to send a patch or a bug report, it is not about making > technical decisions. Of course, your advice as a long-time user on > these decisions is always very welcome. > >> However, I would be happy to >> >> - Assist in trying to reproduce and confirm bugs >> - Assist in extracting additional information and providing >> guidance/clarification for bug reports >> - Assist with documentation >> - Provide some guidance on patches, particularly bug fixes. > > That's exactly what is badly needed to discharge core maintainers from > routine tasks and to let them focus on technical stuff. > > This has basically been my role in my early years of maintainership: > making sure to keep this list as welcoming as possible, to continue to > attract new people with new ideas (and new bug report). This is a > somewhat undervalued role, but a deeply necessary one -- so again, > thanks for helping here. > >> My time availability can vary greatly depending on work. > > That's no problem. We have a team of Tim's :) > >> Also, as a >> blind user, my ability to reproduce bugs can sometimes be hampered by >> the necessity of running Emacspeak in conjunction with org mode (they >> can sometimes interfere with each other). However, apart from that, more >> than happy to help where I can, so if your happy, sign me up! > > If the task becomes too much for you, you can always say that you > won't be available for a while. > > Thanks! OK, consider me 'singed up". Today I will see if I can re-jig my mail system to make it easier to track and respond. As Timothy seems to be doing a fine job 'catching up' with what is already on updates.orgmode, I'll leave that alone and will focus on responding to new bug reports, patches etc which come through the list. I'll also setup a 'clean' virtual image so that I have a vanilla, clean Emacs config I can use for evaluating/reproducing bugs (current emacs stable 27.2). . What is our position with bugs which can only be reproduced in the current development version of Emacs? I'd expect we track them, but focus more on Emacs stable given that dev is a moving target and any bugs may be resolved by later changes in Emacs? Finally, is it also necessary to monitor org bugs reported to the emacs bug tracker or are they sent on to the emacs-orgmode list via some other process? (I currently do monitor emacs-devel but not the bug tracker). -- Tim Cross
next prev parent reply other threads:[~2021-04-26 6:21 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 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 [this message] 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 \ --firstname.lastname@example.org \ --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).