From: Till Kamppeter <till.kamppeter@gmail.com>
To: Michael Sweet <msweet@msweet.org>
Cc: Open Printing <printing-architecture@lists.linux-foundation.org>
Subject: [Printing-architecture] New issue on GitHub: Bug/Feature/Security selection screen
Date: Sun, 29 Jan 2023 19:48:36 -0300 [thread overview]
Message-ID: <1ea9f7d3-e1c0-2e7c-64fb-7ce18a5202b7@gmail.com> (raw)
Hi,
now I have activated the functionality of reporting security bugs
privately on all repositories of OpenPrinting, but unfortunately, in the
web UI of GitHub it is not intuitive to find the way to the place for
reporting a security issue privately.
When I am on your private GitHub, usually on PAPPL, and click the "New
Issue" button on the Issues page, there appears a selection screen, to
tell whether my report is about a bug, a feature request, or a security
bug. The normal GitHub interface is that if I click on "New Issue" I am
immediately in the form for a public issue report. The private one is
hidden in the "Security" section ...
Other bug trackers, like good old Bugzilla or Launchpad allow you to
choose between public and private in the bug input form.
How can I add such a selection page to the GitHub repos of OpenPrinting?
Or could you add this feature?
Till
next reply other threads:[~2023-01-29 22:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-29 22:48 Till Kamppeter [this message]
2023-01-30 1:47 ` [Printing-architecture] New issue on GitHub: Bug/Feature/Security selection screen Michael Sweet
2023-01-30 1:58 ` Till Kamppeter
2023-01-30 2:17 ` Till Kamppeter
2023-01-30 2:31 ` Michael Sweet
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1ea9f7d3-e1c0-2e7c-64fb-7ce18a5202b7@gmail.com \
--to=till.kamppeter@gmail.com \
--cc=msweet@msweet.org \
--cc=printing-architecture@lists.linux-foundation.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox