-
Notifications
You must be signed in to change notification settings - Fork 26
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
CNCFSD-2191 LitmusChaos #218
Comments
Hey @nate-double-u we have applied for Graduation for LitmusChaos. The process has kickstarted and is progressing well. The docs review is an important item awaited. As an urgent request can we try expediting this? |
Congrats @prithvi1307, that's great news! I'll chat with the team and see what we can do. We still have quite a backlog. (Relevant PR: cncf/toc#1297) |
Hi @prithvi1307, I think that we can probably bump this up the priority list a little bit, but I still don't think this will happen right away. My understanding is that the the TOC has a significant backlog themselves. I think that the TOC has about a 9 month backlog, and one of these analysis usually takes about 6 weeks. |
Thanks @nate-double-u thanks for the update. Understand the backlog on the TOC front but want to understand the backlog on the docs review team? Can we still target getting this done by mid-August? |
/cc @nate-double-u /cc @prithvi1307 I've started work on the Litmus Chaos tech doc analysis. I expect to complete the analysis in a couple weeks, maybe sooner. Will keep you posted. |
Thanks @dwelsch-esi |
@prithvi1307 Good question. What is specifically required from the community: Before the doc analysis PR is merged: Review the analysis and provide feedback: What your concerns are about the docs, what questions you have about the analysis, and any ideas you have about prioritizing and implementing issues brought up in the analysis. After the PR is merged: Recruit contributors and work on the issues that are generated from the analysis. It's also helpful if contributors who are involved in documentation gain some knowledge about the documentation process and how it integrates with OSS development. That can be as quick as reading some of the CNCF process docs (see below) or as involved as taking the docs for developers courses offered by LF/CNCF. What we've done in the past is to have a call once I've mostly completed the analysis but before I've written the issues, to give the community a chance to provide some informed input. I'll probably open the PR for this next week, at which point we can set up the call. You can also comment on the PR; we've had some very productive discussions there as well. In the meantime, please feel free to discuss comments or concerns you have about the doc or the CNCF process via Slack or email. I would ask that anyone wanting to discuss the doc analysis process please read about the process first at the CNCF TechDocs repo, especially the assistance.md, analysis/criteria.md, and sandbox-doc-primer.md files. (Litmus is past the sandbox stage, but that document contains a lot of info and terminology that's helpful to understanding the doc analysis.) /cc @nate-double-u |
@prithvi1307 @umamukkara I've written a draft of the analysis for Litmus Chaos. I'd like to get your feedback on the document, then possibly meet with you and other stakeholders before completing the implementation plan and assessments. Can I ask you to please:
If you have any questions please don't hesitate to contact me. Thanks! /cc @nate-double-u |
https://cncfservicedesk.atlassian.net/browse/CNCFSD-2191
LitmusChaos has requested a TechDocs analysis
The text was updated successfully, but these errors were encountered: