From: Stefan Kangas <stefankangas@gmail.com>
To: 41373@debbugs.gnu.org
Subject: bug#41373: GNU ELPA: Add "reporting bugs" to individual package pages
Date: Sun, 17 May 2020 19:14:57 -0700 [thread overview]
Message-ID: <CADwFkmkVLtBN_R6Z+0WdKjwsBYUHgXAFpjfiR17atG+BUq5zRQ@mail.gmail.com> (raw)
One user reports:
That change fixes the issue! Great! Let’s file a bug and then submit the
fix for it… except… the project.el file contains absolutely no
information about how to submit bugs or patches. There’s nothing on the
project.el web page. No websites, no bug tracker, no email addresses.
Folks, if you maintain Open Source software and you ever wonder why
you’re not getting contributions… this is why you’re not getting
contributions: because you don’t spend any time thinking about making it
easy (or in this case, even possible) for folks to contribute back to
your project.
So, instead of supplying a bug report and a patch, so that other folks
might avoid this problem when they upgrade their Emacs packages (and
instead of working on PROJECT APOLLO, like I planned to do today), I’m
writing this blog post. Hopefully, after I post this online in a few
places, Cunningham’s Law will kick in and somebody will show up and tell
me where I can send this patch after all…
https://genehack.blog/2020/05/open-source-annoyances-and-affordances/
I think this is situation could be alleviated by including a static
section on the pages for individual packages which explains how to
report bugs.
Best regards,
Stefan Kangas
next reply other threads:[~2020-05-18 2:14 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-18 2:14 Stefan Kangas [this message]
2020-05-18 18:04 ` bug#41373: GNU ELPA: Add "reporting bugs" to individual package pages Glenn Morris
2020-05-18 18:07 ` Eli Zaretskii
2020-05-19 0:20 ` Stefan Kangas
2020-05-18 18:12 ` Dmitry Gutov
2020-05-19 0:15 ` Stefan Kangas
2020-05-20 3:54 ` Richard Stallman
2020-05-20 5:30 ` Eric Abrahamsen
2020-05-25 9:04 ` Bastien
2020-05-25 15:39 ` Eric Abrahamsen
2020-05-25 17:09 ` Glenn Morris
2020-05-25 17:49 ` Eric Abrahamsen
2020-06-01 6:32 ` Bastien
2020-06-01 18:29 ` Eric Abrahamsen
2020-06-01 18:41 ` Eli Zaretskii
2020-06-01 19:25 ` Eric Abrahamsen
2020-06-01 19:38 ` Eli Zaretskii
2020-06-01 20:06 ` Eric Abrahamsen
2020-06-01 19:52 ` Glenn Morris
2020-06-01 20:31 ` Eric Abrahamsen
2020-05-25 11:51 ` Dmitry Gutov
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=CADwFkmkVLtBN_R6Z+0WdKjwsBYUHgXAFpjfiR17atG+BUq5zRQ@mail.gmail.com \
--to=stefankangas@gmail.com \
--cc=41373@debbugs.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.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).