Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add 'profiles' for the Source Track #1142

Open
TomHennen opened this issue Sep 20, 2024 · 1 comment
Open

Add 'profiles' for the Source Track #1142

TomHennen opened this issue Sep 20, 2024 · 1 comment
Labels
source-track

Comments

@TomHennen
Copy link
Contributor

@adityasaky suggested that it might make the source track more clear if we

  1. Define 'profiles' for source control systems as a combination of VCS, SCP, attestation issuers, etc...
  2. Each profile should explain how it would meet the various source level requirements
  3. Remove many of the examples that are currently inlined with the requirements themselves

@adityasaky mentions this would be made easier once we define a source control system #1128 .
@TomHennen
Copy link
Contributor Author

This is probably a good way to address @marcelamelara's comment here #1128 (comment)

@adityasaky adityasaky mentioned this issue Sep 20, 2024
Open
@TomHennen TomHennen mentioned this issue Sep 20, 2024
Open
@adityasaky adityasaky mentioned this issue Oct 3, 2024
Merged
TomHennen pushed a commit that referenced this issue Oct 14, 2024
@adityasaky
content: draft: Clarify branch protection in source track (#1175)
3f435fe 
Re: #1136

I'm trying to separate "branch protection" which is typically associated
with SCP features from the property we want for the branches intended
for consumption. I've also applied the SCS terminology we adopted in
another PR.

The framing of how this can be accomplished is still a bit TBD, if we
decide to adopt something like #1142 suggests, we could move the Git +
GitHub/GitLab piece out? That's also where we could discuss server side
pre-receive hooks etc.?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
source-track
Projects
Issue triage
Status: 🆕 New
SLSA Source Track
Status: Ready for work!
Milestone
No milestone
Development

No branches or pull requests
1 participant
@TomHennen