From: Jean Louis <email@example.com> To: Bastien <firstname.lastname@example.org> Cc: email@example.com Subject: Re: Someone to oversee Org bugs as reported with M-x report-emacs-bugs? Date: Fri, 11 Dec 2020 09:12:16 +0300 [thread overview] Message-ID: <X9MNwNsrgXp5SJeI@protected.rcdrun.com> (raw) In-Reply-To: <firstname.lastname@example.org> * Bastien <email@example.com> [2020-12-11 08:18]: > Dear all, > > as the subject says: it would be nice to have someone overseeing Org > bugs that are reported with M-x report-emacs-bugs. > > These bugs end up in the Emacs debbugs tracking tool: > > https://debbugs.gnu.org/cgi/pkgreport.cgi?package=emacs > https://www.gnu.org/software/emacs/manual/html_node/emacs/Bugs.html > > They are also sent to the bug-gnu-emacs mailing list: > https://mail.gnu.org/mailman/listinfo/bug-gnu-emacs Process could be somewhat automated if program calculcates what is the month and expands to 2020-12 then downloads automatically the mbox file from: https://lists.gnu.org/archive/mbox/bug-gnu-emacs/2020-12 and conduct grep searches: grep -i "Subject: .*Org" 2020-12 which gives: Subject: bug#45002: gnu.org Mailbox Upgrade!! Subject: bug#43268: Update Org for Emacs 27.2 Subject: bug#45091: 27.1; M-x org-table-paste-rectanble Subject: bug#45091: 27.1; M-x org-table-paste-rectanble Subject: bug#45091: 27.1; M-x org-table-paste-rectanble Subject: bug#45091: 27.1; M-x org-table-paste-rectanble Subject: bug#45091: 27.1; M-x org-table-paste-rectanble Subject: bug#45091: 27.1; M-x org-table-paste-rectangle Subject: bug#45091: 27.1; M-x org-table-paste-rectangle Subject: bug#43268: Update Org for Emacs 27.2 Subject: bug#43268: Update Org for Emacs 27.2 Subject: bug#45091: 27.1; M-x org-table-paste-rectangle Subject: bug#43268: Update Org for Emacs 27.2 Subject: bug#45091: 27.1; M-x org-table-paste-rectangle Subject: bug#45091: 27.1; M-x org-table-paste-rectangle Subject: bug#42484: 26.1: org-mode should display value of links in minibuffer Subject: bug#45147: Org-like cycling in outline-minor-mode Subject: bug#45147: Org-like cycling in outline-minor-mode If somebody has a VPS the report could come once per day. For me it would be quite natural that report arrives as Org file report. It is additionally possible to parse: bug#45147 into a hyperlink to WWW report: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=45147 or to directly link to mbox: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=45147&mbox=yes > Volunteering for overseeing these bugs does not mean you have to > subscribe to this list or to fix all Org bugs there :) But one could do that as it would be useful activity. And when one answers on bug reported through main Emacs interface one could add Cc: to Org mailing list. > First of all, most users use M-x org-submit-bug-report for Org bugs, > which is the preferred way of submitting Org bugs. Maybe they use that, maybe most users use the menu option. Let us not forget that majority of users will never report a bug and that bug reporting should be encouraged. > Secondly, most bugs reported with M-x report-emacs-bugs are bugs > against old versions of Org, already fixed upstream. > > So the idea is just to be able to answer one of these: > > - "Thanks but I cannot reproduce the bug with the latest Org." Org users are not necessarily experienced users who will know what it means: - bug? - when users do not understand the meaning they may not even report. If they wish to improve some feature, they will not report. Option in the Org menu: "Send bug report" could as well be more descriptive to be like: "Send bug report or feature request" and manual could prominently invite users to send bug reports or feature requests. Additionally, I suggest you add in the menu "Subscribe to Org mailing list" to invite users. - "to reproduce the bug" -- this may not have meaning for new users same as for you. It may be also understood as rejection or that user's observation is wrong, thus wronging the user. It needs more description - "latest Org" -- this may not be understood in the same way. It needs pointers how to upgrade. Formulation should be adopted to the view point of a new user, it could be something like: "Thank you for your bug report related to Org mode. New bugs like you reported get resolved in the next development version of the Org mode. The bug as described is not reproducing in that latest development version, so I think that it hsa been resolved. Advise is that you upgrade your Org package in Emacs by doing: M-x .............." Additionally in that snipper under that context that bug is not reproducible, you should tell to user that Org bugs may be reported straight from Org mode menu or by M-x org-submit-bug-report Please do not tell users something like Org is not Emacs as that is confusing, and not true. Telling them harshly that Org bugs have to be submitted to Org mailing list is causing problems as it is wronging users. Do not assume that user, especially one who reports through main interface, would know what you mean. You may formulate it better in the sense that it will be better understood. It is a snippet or template to be used, not something to re-type over and over again. Consider that Org comes with Emacs. GNU/Linux and BSD derivatives distribute Emacs. Users using Org need not know that there exists M-x package-list-packages and various versions of Org. > - "Thanks, I confirm this is a bug, can you forward it to the Org > mailing list at firstname.lastname@example.org?" That is wrong approach and causes more work than necessary. User has already reported the bug properly in that case. Org is part of Emacs and user have clicked Help - Report Emacs Bug. Do not invite user to report again or do more actions. You have got the bug? Just Cc: the org mailing list and keep working with the bug by keeping Cc: in place and following the bug. Do not reject user's report by expecting user would help you send it to mailing list. Engage solving process as report is not at the step 2, don't bring it to step 1 back. To forward to Org mailing list is 1-2 seconds. Instead, you may answer as following: "Thank you for your bug report. I have now included copy of this report to the Org mailing list: email@example.com When answering on this report, please use group reply option or reply to all option so that copied emails get notified. While it is alright to report bugs through the main Emacs interface you are encouraged to use review the menu option Org - Report Bugs for our faster response time." Jean
next prev parent reply other threads:[~2020-12-11 6:17 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-12-11 5:17 Bastien 2020-12-11 6:12 ` Jean Louis [this message] 2020-12-11 6:27 ` Bastien 2020-12-11 6:37 ` Jean Louis 2020-12-13 9:52 ` Bastien 2020-12-13 15:39 ` Jean Louis 2020-12-13 21:48 ` Tim Cross
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=X9MNwNsrgXp5SJeI@protected.rcdrun.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: Someone to oversee Org bugs as reported with M-x report-emacs-bugs?' \ /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).