emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@gnu.org>
To: emacs-orgmode@gnu.org
Subject: Someone to oversee Org bugs as reported with M-x report-emacs-bugs?
Date: Fri, 11 Dec 2020 06:17:38 +0100	[thread overview]
Message-ID: <87h7os9b0t.fsf@bzg.fr> (raw)

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

Volunteering for overseeing these bugs does not mean you have to
subscribe to this list or to fix all Org bugs there :)

First of all, most users use M-x org-submit-bug-report for Org bugs,
which is the preferred way of submitting Org bugs.

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."

- "Thanks, I confirm this is a bug, can you forward it to the Org
  mailing list at emacs-orgmode@gnu.org?"

... and to make sure that you _close_ the bug report when necessary.

It is a very nice way to get _some_ work done for Org/Emacs while 
also being part of the Emacs maintainance larger team.

Who's in?

-- 
 Bastien


             reply	other threads:[~2020-12-11  5:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-11  5:17 Bastien [this message]
2020-12-11  6:12 ` Someone to oversee Org bugs as reported with M-x report-emacs-bugs? Jean Louis
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=87h7os9b0t.fsf@bzg.fr \
    --to=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).