-
Notifications
You must be signed in to change notification settings - Fork 237
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
Add user guide #64
Comments
Could we use github pages? or just a folder with markdown is ok for now? |
/kind documentation |
@ArangoGutierrez: GuidelinesPlease ensure that the issue body includes answers to the following questions:
For more details on the requirements of such an issue, please see here and ensure that they are met. If this request no longer meets these requirements, the label can be removed 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/test-infra repository. |
We can probably start with markdown and move it to github pages when there is some useful content :) |
I'll start this /assign |
I just added in the description a list of things I would like to cover. Anything else? |
for a v0.0.1 , we are ok i Think |
one more thing to add to CQ concept is queueing strategy |
/kind feature
/size M
Something more comprehensive that the existing README. Some of the use cases in bit.ly/kueue-apis can be dumped into samples/guides.
If possible, generate some documentation out of the APIs, similar to https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.23/
Contents (not necessarily each one will be a page, but they could be sections on existing pages).
The text was updated successfully, but these errors were encountered: