-
Notifications
You must be signed in to change notification settings - Fork 426
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
Registration #968
Registration #968
Conversation
Hi, |
Hi, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A little more information should be provided in your proposal.
Also, please try remove the .DS_Store
file
Github username: carllei | ||
|
||
## Topic "DevSecOps throughout the DevOps lifecycle" | ||
During the presentation we will talk about the importance of DevSecOps throughout different stages of DevOps lifecycle. We will discuss what are the current best practices in DevSecOps. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- a short statement (1-3 sentences) about the relevance and timeliness for testing and devops
- bullet outline of the presentation
Don't forget to add these two.
To get your PR merged, you have to add the information. So, I guess you should do it ASAP to get the spot for week2. |
Done! |
Hi, I looked through that topic and our topics are about different things. Our group is not talking about Kubernetes at all. I wonder what should we change? |
You are right, their topic is more specific. But they also talk about DevSecOps and the fact that they discuss DevSecOps in context of Kubernetes makes their topic more concrete and therefore more interesting. I think you can make your work different from theirs by focusing more the third section of your agenda "Secure CI/ CD Pipelines (+ some tools)" and discuss a specific tool their. WDYT? |
Thank you for the recommendation, have reformulated it now |
Hi again, we made new changes where we narrow topic more. |
No description provided.