public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] A new GLSA schema
Date: Sat, 12 Nov 2022 06:09:47 +0100	[thread overview]
Message-ID: <68c8ce8bf2bf90b239b63bb65935c2c3e91c7554.camel@gentoo.org> (raw)
In-Reply-To: <CAHY5Mef4mnJpTpYCsd5E=D5Ex-27vNxVWZwJMDu9Kc1iADPqhw@mail.gmail.com>

On Fri, 2022-11-11 at 16:06 -0600, Gordon Pettey wrote:
> On Thu, Nov 10, 2022 at 6:27 PM John Helmert III <ajak@gentoo.org> wrote:
> 
> > On Thu, Nov 10, 2022 at 09:49:27PM +0100, Jonas Stein wrote:
> > > On 10/11/2022 03:27, John Helmert III wrote:
> > > > The first GLSA in glsa.git is GLSA-200310-03, the third GLSA of
> > > > October 2003. It used roughly the same format of the GLSAs we release
> > > > today, in 2022, making that format almost as old as me.
> > > 
> > > IFF we change the format, we should not invent a new standard [1] but
> > > use existing one like CSAF [2]
> > > 
> > > [1] https://imgs.xkcd.com/comics/standards.png
> > > [2] https://oasis-open.github.io/csaf-documentation/
> > 
> > We're not inventing a new "standard", we're upgrading the format we use
> > to distribute GLSAs.
> > 
> 
> Standard, format, semantics. You are producing a new schema in a field
> where at least one usable (and already-improved?) schema exists. NIH?

GLSA: 2003
CSAF: 2016

Sure sounds like OASIS did a NIH there.

-- 
Best regards,
Michał Górny



      parent reply	other threads:[~2022-11-12  5:09 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-10  2:27 [gentoo-dev] [RFC] A new GLSA schema John Helmert III
2022-11-10  3:43 ` Michał Górny
2022-11-10  3:58   ` Sam James
2022-11-10  4:10     ` Marc Schiffbauer
2022-11-10  4:19       ` John Helmert III
2022-11-10  6:46         ` Marc Schiffbauer
2022-11-10  4:13   ` John Helmert III
2022-11-10  8:43     ` Jaco Kroon
2022-11-10  9:40       ` Matthew Smith
2022-11-10  9:48         ` Jaco Kroon
2022-11-10 10:19       ` Sam James
2022-11-10 10:51         ` Jaco Kroon
2022-11-10 14:24       ` John Helmert III
2022-11-10 20:07         ` Jaco Kroon
2022-11-10 20:55           ` Mart Raudsepp
2022-11-11  0:22             ` John Helmert III
2022-11-10 20:49 ` Jonas Stein
2022-11-11  0:27   ` John Helmert III
2022-11-11 22:06     ` Gordon Pettey
2022-11-11 22:40       ` Sam James
2022-11-11 22:43         ` Sam James
2022-11-12  0:01           ` Jonas Stein
2022-11-12  0:03             ` Sam James
2022-11-12 13:15               ` Jonas Stein
2022-11-12  0:04           ` Gordon Pettey
2022-11-12  0:06             ` Sam James
2022-11-12  5:09       ` Michał Górny [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

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

  git send-email \
    --in-reply-to=68c8ce8bf2bf90b239b63bb65935c2c3e91c7554.camel@gentoo.org \
    --to=mgorny@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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