unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Jonathan Brielmaier <jonathan.brielmaier@web.de>
Cc: 68962-done@debbugs.gnu.org
Subject: bug#68962: website: directly link the security mail address
Date: Thu, 30 May 2024 09:45:50 -0400	[thread overview]
Message-ID: <878qzre7ld.fsf@gmail.com> (raw)
In-Reply-To: <709deb2f-c3ab-c0bc-514f-cb9ea4a3a689@web.de> (Jonathan Brielmaier's message of "Wed, 7 Feb 2024 00:19:51 +0100")

Hi Jonathan,

Jonathan Brielmaier <jonathan.brielmaier@web.de> writes:

> Is there a reason why we don't link to the mail alias directly on the
> security page:
> https://guix.gnu.org/en/security/
>
> Because the mailman archive doesn't make really sense for most of the
> users as it's only accessible with a password.
>
> What about this small patch?
>
> ```
> diff --git a/website/apps/base/templates/security.scm
> b/website/apps/base/templates/security.scm
> index 8a72950..429e5df 100644
> --- a/website/apps/base/templates/security.scm
> +++ b/website/apps/base/templates/security.scm
> @@ -43,7 +43,7 @@ system|GNU Hurd|GNU Guix package manager|Security
> updates") #\|)
>           `(p
>             "To report sensitive security issues in Guix itself or the
>              packages it provides, you can write to the private mailing
> list "
> -          (a (@ (href
> "https://lists.gnu.org/mailman/listinfo/guix-security"))
> +          (a (@ (href "mailto:guix-security@gnu.org"))
>                ("guix-security@gnu.org")) ".  This list is monitored by a
>              small team of Guix developers."))
>         ,(G_
> ```

LGTM.  I've pushed it.

-- 
Thanks,
Maxim




      reply	other threads:[~2024-05-30 13:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-06 23:19 bug#68962: website: directly link the security mail address Jonathan Brielmaier via Bug reports for GNU Guix
2024-05-30 13:45 ` Maxim Cournoyer [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://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=878qzre7ld.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=68962-done@debbugs.gnu.org \
    --cc=jonathan.brielmaier@web.de \
    /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/guix.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).