From: Torsten Wagner <torsten.wagner@gmail.com>
To: Bastien <bzg@gnu.org>
Cc: Org Mode Mailing List <emacs-orgmode@gnu.org>
Subject: Re: idea, bug report template
Date: Mon, 9 Apr 2012 10:37:38 +0900 [thread overview]
Message-ID: <CAPaq-gMHOARRnnc5yS_wa17JaqiQqmaPc3JjamYNZb4RXinR_A@mail.gmail.com> (raw)
In-Reply-To: <878vi9dr5q.fsf@gnu.org>
Hi Bhastien, ;)
thanks for the pointer. Indeed this does much of the idea I had already.
A few points which might be add
* If called with a region marked, this region could be put into the
mail. That is mark the "defect" region and call
`org-submit-bug-report' and you are almost done with your report.
* As for the privacy concern. The org-mode settings could be saved to
an extra file and attached as a zipped attachment. It would be still
rather easy for devs to see it but it would not be exposed on the
mailing list archives for any kind of data crawler. E.g. some might
have email-addresses saved and hence they might receive a lot of spam
if this addresses are exposed on the web.
* The text could include a first responder guide to help people to
send in clean and good bug-reports. It could include to ask people to
start emacs without personal config-files, to make sure the bug is not
actually a misconfiguration. A bunch of questions to fill in. E.g.,
* Abstract of the bug report (3-5 sentence)
* Please select from the keywords below the ones which fits your problems best
* Description
** What did you try yo do?
** What did you expect to happen?
** What happen?
* Did the problem appear for the first time resp. did it work previously?
* Is the problem still reproducible after starting emacs with emacs -q
(do not load init files)?
* Please copy here a minimal example which demonstrate the problem.
Try to reduce it to the real problem.
* Please attach here any error log you might received
* Writing down this list makes me wonder if the bug-report buffer
shouldn't be a org-buffer itself so people could test there minimal
example within that buffer and the bug report could be split into two
parts org-create-bug-report and org-submit-bug-report (create a mail
with the bug report org-buffer as content). The last could call the
first hook if no bug-report buffer is present.
Torsten
On 6 April 2012 20:40, Bastien <bzg@gnu.org> wrote:
> Hi Thorsten,
>
> check `org-submit-bug-report'. We can certainly improve this and
> make it more structured/interactive.
>
> Thanks,
>
> --
> Bastien
prev parent reply other threads:[~2012-04-09 1:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAPaq-gO6OtGLiRLfTYxatRFTxpikgUh1D0CXdFe_HdynB29QUA@mail.gmail.com>
2012-04-06 11:17 ` idea, bug report template Torsten Wagner
2012-04-06 11:40 ` Bastien
2012-04-06 13:21 ` Thorsten
2012-04-09 1:37 ` Torsten Wagner [this message]
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=CAPaq-gMHOARRnnc5yS_wa17JaqiQqmaPc3JjamYNZb4RXinR_A@mail.gmail.com \
--to=torsten.wagner@gmail.com \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
/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/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).