David Hadas comments

Results 48 comments of


                                            David Hadas

Security response team rotation is outdated

Q from @dprotaso: is the TOC on the [email protected] mailing list?

Add definitions of alpha/beta/GA to maturity levels

Add Broadcom to the security embargo list

@dprotaso - for diligence, would you please confirm that anyone exposed to the email address `[email protected]` have read and approved the [Embargo policy](https://github.com/knative/community/blob/main/working-groups/security/disclosure.md#embargo-policy)?

New Repo: `autoscaler-keda`

hi, As this is sponsored by Serving, we should wait for @dprotaso to comment before moving forward to create the repo. Other than that, looks fine to me.

PROCESS CHANGE: Merge Client and Functions WG together

+1 No strong opinion regarding the name - I am fine with a short one (e.g. CLI WG) and having [the WG description](https://github.com/knative/community/blob/main/working-groups/WORKING-GROUPS.md) stating it also handles Functions.

🚨 PROCESS CHANGE: Merging some working groups and committees to better reflect current contributor engagement

Qs and a comment that were raised today in TOC - as input for SC. Qs: - How do the new governance ensure balancing between contributors associated with specific vendors...

🚨 PROCESS CHANGE: Merging some working groups and committees to better reflect current contributor engagement

_Regarding the desire to merge SoC and ToC:_ > Sorry I couldn't understand the suggestion here. Can you elaborate please? @aliok The point I was making is very similar to...

Add rhuss and dsimansk as approvers to all kn plugins

Need rebase

Make SECURITY.md consistent

@upodroid hey, we are adding this file to all repos (as part of the security audit if there is also away to make sure it is added to all future...

KBS: Add a `Delete` method to /resource/{repository}/{type}/{tag}

CC: @bpradipt, @fitzthum, @portersrc