-
Notifications
You must be signed in to change notification settings - Fork 212
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
Enhancement of Technical Outcomes #1063
Comments
Hello @wzshiming, I am thrilled at the prospect of contributing to the enhancement of KWOK's website, specifically in detailing the technical outcomes as outlined in issue #1063. I have a recent experience with the Kyverno Chainsaw project, where I substantially improved its documentation to better showcase its advanced features. Initially, the quick start guide did not fully represent the capabilities of Chainsaw. To address this, I immersed myself in understanding the tool's innovative features through extensive research, including a series of insightful blog posts:
These articles helped me gain a deep understanding of Chainsaw's unique features like assertion trees, resource templating, and resource diff in assertion failures. Leveraging this knowledge, I adopted a narrative approach in the documentation to contextualize these features through real-use case examples. My contributions were compiled into a pull request, which has since been merged. The enhancements are now visible in the latest release of the Kyverno Chainsaw documentation, specifically in the Chainsaw Characteristics section. For KWOK, I envision a similar approach. I plan to begin with a comprehensive review of KWOK's existing resources and identify key features through further research, including available documentation, blog posts, and community insights. My goal is to outline how these features collectively achieve high-level technical outcomes in areas like Chaos Testing, Performance, Simulation, and Scalability, presenting them in a clear, structured, and engaging manner. I am keen to bring my documentation skills and enthusiasm for Kubernetes technologies to the KWOK project. Please let me know the best way to start contributing to this effort. Best regards, |
Thank you, but this program is pending approval, if this is approved, Monday 13th May to start mentee applications. |
@wzshiming sir i am also interested in mentorship #1063 |
The application is already open |
Hi @wzshiming , I am interested in working on this issue, I have been doing some research around the same, I have some questions, |
Hi @wzshiming, I'm interested in working on this issue for the LFX summer term. |
The application is already open, If you want to be a mentee of LFX, apply here |
The term is over |
@wzshiming: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
What would you like to be added?
https://mentorship.lfx.linuxfoundation.org/project/ef8e7637-2eb6-4672-8f6c-c9f9f0677da0
A section of the KWOK website detailing these technical outcomes.
We have identified the following areas of focus:
Here are some of the traces I found involving the use of kwok:
Some of the talks that mention kwok are:
Some of the docs that use kwok are:
Some of the projects that use kwok are:
we shouldn’t mention the description of the specific project. If possible, focus on what kwok can be used for, at most mentioning at the end of the content that the project is a practice of it.
Why is this needed?
On the KWOK homepage (https://kwok.sigs.k8s.io/), we aim to document the technical outcomes of using KWOK. These outcomes represent the aggregation of some of KWOK's features to achieve a high-level technical goal.
ref cncf/mentoring#1227
The text was updated successfully, but these errors were encountered: