From: Jean Louis <bugs@gnu.support>
To: emacs-devel@gnu.org, Bastien <bzg@gnu.org>
Cc: Boruch Baum <boruch_baum@gmx.com>,
Stefan Kangas <stefankangas@gmail.com>,
Emacs-Devel List <emacs-devel@gnu.org>
Subject: Re: bug archiving policy
Date: Sat, 12 Dec 2020 05:40:18 +0000 [thread overview]
Message-ID: <BB7A3917-E99A-402A-8B0A-18562D7024A0@gnu.support> (raw)
In-Reply-To: <87h7osyjby.fsf@bzg.fr>
Do you doubt it also when user reports straight from Org mode? Would it be wrong for standard emacs bug function to detect org mode and ask user if it is org related, and if it is, to route user to org report function? You don't need to ask if user does not begin bug report from Org mode
Routing is to me logical and reasonable, I get surprised that it is not and was not obvious at inception of Org bug report function and that interface within Emacs splitted into two directions of reporting bugs with later regrets and efforts to make it again right. If not solved sooner, instead of 4 or 5 per month it may results amount to 40 or 50 in some time as Org and Emacs become popular.
There are few other functions that want separate bug reporting such as TeX etc. They add to confusions.
It is more useful to have centralized bug database as that way there are better responses to users. More skilled people not subscribed to org mailing list for answer and solve bugs. Imagine if that goes further to split each package bug report to separate mailing lists, it does not branch reasonably.
Then we get into silly discussions with users telling them from official making lists how Org is not Emacs, etc. wronging and thus rejecting users.
Functions shall be united and they may remain at two places. I would even place it as main menu after Help as number of reported bugs does not correspond appropriately to number of Emacs and Org users.
The general Emacs bug function should be improved with references or button to jump to Org mode report template if it is org mode related. One click.
Org more function should report to central database debbugs, use procmail or equivalent to automatically route those bugs to org mailing list. If you don't know how, ask me or somebody who knows.
Things can be solved centrally without kicking users back and forth.
Am December 11, 2020 5:58:57 AM UTC schrieb Bastien <bzg@gnu.org>:
>Jean Louis <bugs@gnu.support> writes:
>
>> Something like:
>>
>> If user is in Org mode, then to be asked:
>>
>> - is this Org mode bug?
>>
>> then if no, to proceed to standard bug report.
>
>I see how this could be useful, but maybe Org is the only package in
>this situation (i.e. suffering from separate ways of reporting bugs),
>so I doubt implementing a specific behavior for Org is correct.
>
>The stream of Org-related bugs reported with M-x report-emacs-bug is
>really not that big.
next prev parent reply other threads:[~2020-12-12 5:40 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-06 9:26 bug archiving policy Boruch Baum
2020-12-06 9:52 ` Stefan Kangas
2020-12-06 10:14 ` Boruch Baum
2020-12-06 10:24 ` Jean Louis
2020-12-10 11:08 ` Bastien
2020-12-10 11:23 ` Stefan Kangas
2020-12-10 14:21 ` Eli Zaretskii
2020-12-11 5:53 ` Bastien
2020-12-06 10:18 ` Jean Louis
2020-12-10 11:10 ` Bastien
2020-12-10 11:57 ` Jean Louis
2020-12-11 5:58 ` Bastien
2020-12-12 5:40 ` Jean Louis [this message]
2020-12-12 13:44 ` Stefan Monnier
2020-12-13 9:48 ` Bastien
2020-12-13 16:00 ` Michael Albinus
2020-12-13 16:30 ` Bastien
2020-12-13 18:00 ` Michael Albinus
2020-12-13 17:09 ` Org-mode in debbugs [was Re: bug archiving policy] Glenn Morris
2020-12-13 17:58 ` Michael Albinus
2020-12-10 11:07 ` bug archiving policy Bastien
2020-12-10 13:45 ` Org-mode bugs in the Emacs bug tracker (was: Re: bug archiving policy) Stefan Kangas
2020-12-11 5:36 ` Org-mode bugs in the Emacs bug tracker Bastien
2020-12-11 13:11 ` Stefan Kangas
2020-12-11 21:47 ` Tim Cross
2020-12-11 23:53 ` Bastien
2020-12-12 1:46 ` Tim Cross
2020-12-12 5:11 ` Jean Louis
2020-12-13 9:41 ` Bastien
2020-12-11 23:45 ` Bastien
2020-12-12 5:42 ` Jean Louis
2020-12-06 9:56 ` bug archiving policy Eli Zaretskii
2020-12-06 10:18 ` Boruch Baum
2020-12-06 10:24 ` Eli Zaretskii
2020-12-06 10:39 ` Boruch Baum
2020-12-06 10:57 ` Eli Zaretskii
2020-12-06 11:13 ` Boruch Baum
2020-12-06 11:22 ` Michael Albinus
2020-12-06 11:28 ` Boruch Baum
2020-12-06 10:21 ` Boruch Baum
2020-12-06 10:52 ` Eli Zaretskii
2020-12-06 11:09 ` Stefan Kangas
2020-12-06 11:18 ` Boruch Baum
2020-12-06 11:25 ` Michael Albinus
2020-12-06 11:30 ` Boruch Baum
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BB7A3917-E99A-402A-8B0A-18562D7024A0@gnu.support \
--to=bugs@gnu.support \
--cc=boruch_baum@gmx.com \
--cc=bzg@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=stefankangas@gmail.com \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.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).