-
Notifications
You must be signed in to change notification settings - Fork 70
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
README: Add link to resource owners wiki page #109
Conversation
Now we have the table of Kata resources and owners on a wiki page, let's link it from the main community README to make it easier to find. Fixes: kata-containers#71 Signed-off-by: Graham Whaley <[email protected]>
I thought it was time to get the data out of an Issue and into a more formal place, so I've moved the table to the wiki, and linked to it from the top level community README. @ClaireMassey @ttx, fyi, as your names appear in the table as well ;-) |
Not sure if wiki is the best place, but I support to list them in a more formal place |
:-) I put them in the wiki page as:
I appreciate that putting into an actual document would make it easier to find - I suspect most folks never visit the (two, slender) wikis we have, and hence, I added the link out to the wiki page to try and help point folks in the right direction. If we get consensus to move to a markdown do, then np, I'll re-PR.. |
Hi @grahamwhaley thanks! 😍 I‘ll insert an entry for ARM CI resources in resource-owners. |
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.
Thanks @grahamwhaley.
One more ack needed before we can land this doc change. |
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.
+1
Now we have the table of Kata resources and owners on a wiki page,
let's link it from the main community README to make it easier
to find.
Fixes: #71
Signed-off-by: Graham Whaley [email protected]