-
Notifications
You must be signed in to change notification settings - Fork 498
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.
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
[Assessment] Argo #739
Comments
👍 from Red Hat. |
Thanks for opening this issue up! We will process this when we have our intake prioritization review, which should be soon.. But looks likely to be scheduled after cloud custodian review, which will be about the Sep/Oct timeframe! |
If we have any questions with respect to the self-assessment (and associated documentation), should I reach out to both of you (i.e. via the CNCF Slack instance or this ticket), or are there additional team members we should include? I've gone ahead and created a dedicated channel, Good to meet you! |
I'd be open to lead this one |
Interested to help on this |
Interested in helping on this |
Thanks for your interest in being part of the review team. It would be great if y'all and any other folks interested to be part of the review team state their conflict of interest. Thanks! |
Here's me: Conflict of interest statement template:
|
|
Hey, happy to support this from the Argo CD side 👍 |
Hard conflicts: Soft conflicts: |
Good day, Just a heads-up to the Argo team and their reps: I'm aiming to start assembling reviewers mid-September. I expect it to be a busy time with Kubecon approaching in October. In case anyone hasn't already joined: I'll be using the Slack channel as the primary means of communication (https://cloud-native.slack.com/archives/C029KLSQBD2). I have also put together a private Google group (i.e. mailing list) as a fallback means of communication (typically everything is done through Slack, but if we need to schedule a meeting on short notice through a tool like Doodle, for example, I'll make a point of mentioning it both via Slack and the mailing list). The mailing list will be posted in the Slack channel and anyone that wants to join just needs to ping me via Slack. Have a great week! |
Interested to help. Hard conflicts: Soft conflicts: |
I'm super happy to help with the review |
+CC: @ashutosh-narkar @lumjjb @rficcaglia Good day everyone, Hope Kubecon went well for everyone! Calling out for security reviewers and security review leads for the Argo assessment. I'll also forward this to Brandon and Ash to relay during our Wednesday meeting (I'm unfortunately unable to attend said meetings at the moment due to a recurring scheduling conflict). |
Good day, Here's the dedicated Slack channel for the assessment:
Once we've wrapped up the COI disclosures and have everyone added to the Slack channel, we can setup some last-minute details (i.e. any additional contact details needed, how meetings will be scheduled, etc.), and we can get this underway. Thank you to our security assessors and leads! Edit: reviewers also need to go over this document prior to concluding the COI signoff/disclosure: https://github.com/cncf/tag-security/blob/main/assessments/guide/security-reviewer.md |
Hard conflicts: Soft conflicts: |
Hard conflicts: Soft conflicts: |
Thanks everyone! Updating the list:
@moswil When time permits, could you please join the #sec-assessment-argo channel in Slack? We'll use it for a lot of correspondence going forward. Now to get things in motion: @jlk @apmarshall @nadgowdas @moswil Is there any preference for a live meeting (i.e. I throw together a Doodle invite to see if I can get a good meeting time going to setup the team structure, depending on the time zones and schedule of everyone, or shall we just proceed asynchronously via Slack)? Once that's in place, the security lead plus security reviewers can take over from there. :) |
Hard conflicts: Soft conflicts: |
Chair sign off for conflict of interest |
For those not watching Slack - we're doing the first call for the group this Thursday at 7AM Pacific Time. |
Excellent: welcome aboard. You can find us in the assessment's Slack channel. |
Excellent: welcome aboard! You can find us in the assessment's Slack channel. Please feel free to reach out to me on Slack or via the assessment channel with any questions. |
Excellent: welcome aboard! You can find us in the assessment's Slack channel. Please feel free to reach out to me on Slack or via the assessment channel with any questions. |
Great: 2 additional reviewers + 2 additional shadow reviewers. In addition to the assessment channel link I've noted above, you can also find me via "Matthew Giassa" in the CNCF Slack if you have any 1:1 questions. Cheers! |
chair sign off on conflict statements |
@lumjjb - After our chat - just about an hour ago: Hard conflicts: Soft conflicts: |
+CC: @raesene Hi Rory, When time permits, could you please also fill out one of the conflict-of-interest sign-offs (examples above). Thank you. |
Hard conflicts: Soft conflicts: |
This issue has been automatically marked as inactive because it has not had recent activity. |
This issue has been automatically marked as inactive because it has not had recent activity. |
A quick sign of life... |
A little late in the process - but if you need extra help: Conflict of interest statement template:
|
@hblixt That's awesome to hear! Thanks for the heads-up. |
This issue has been automatically marked as inactive because it has not had recent activity. |
@IAXES What is the current status here? I met and worked with the folks in Detroit and see the links above to the self assessments. However, there is no activity in the slack channel since March 3rd. @jannfis Are you still interested in this completing? I can find folks to push this along and get this to the finish line. I wanted to check there is interest and energy from your side first though. |
This issue has been automatically marked as inactive because it has not had recent activity. |
Closed due to lack of response. |
Project Name: Argo
Github URL: https://github.com/argoproj
cncf/toc#299 (Incubation)
cncf/toc#604 (Graduation - in process)
Self Assessments:
Argo CD
Argo Rollouts
Argo Workflows
Argo Events
Security Provider: No
Argo CD
Argo Workflows
Argo Rollouts
Argo Events
Joint Review
The text was updated successfully, but these errors were encountered: