public inbox for
 help / color / mirror / Atom feed
From: "ezannoni at gmail dot com" <>
Subject: [Bug Infrastructure/29615] prototype & document SOP for signed-git-op repo
Date: Mon, 26 Sep 2022 17:39:01 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Elena Zannoni <ezannoni at gmail dot com> changed:

           What    |Removed                     |Added
                 CC|                            |ezannoni at gmail dot com

--- Comment #3 from Elena Zannoni <ezannoni at gmail dot com> ---
Butting in... 
Serhei, yes that document. I think this is also worth taking a look at:
Has the use of the tags spelled out, and the roles of the reviewers and the
submitters of patches and what they "agree" to do/represent.

In addition, there is the SPDX license identifier thing, that the kernel has.
For further supply chain security/identification/SBOMs and whatnot. 

I am not saying to mimic everything exactly, but to get an idea of what the
kernel was trying to solve with these things.

Note that the kernel workflow is different, only the maintainers push code to
the repo (in the majority of the subsystems), for other projects it might not
be the same (such as the GNU toolchain write after approval case).

You are receiving this mail because:
You are the assignee for the bug.

  parent reply	other threads:[~2022-09-26 17:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-26 13:30 [Bug Infrastructure/29615] New: " fche at redhat dot com
2022-09-26 16:57 ` [Bug Infrastructure/29615] " serhei at serhei dot io
2022-09-26 17:20 ` serhei at serhei dot io
2022-09-26 17:39 ` ezannoni at gmail dot com [this message]
2022-09-27 11:45 ` mark at klomp dot org
2022-09-27 13:23 ` serhei at serhei dot io
2022-09-27 20:10 ` mark at klomp dot org
2023-06-01 19:54 ` mark at klomp dot org
2023-10-14  1:02 ` fche at redhat dot com

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:

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

  git send-email \ \ \ \

* 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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).