-
Notifications
You must be signed in to change notification settings - Fork 635
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
Process for transitioning Google Docs in CNCF-based workspace #1079
Comments
Actually I think @amye answers my question already on #980 (comment) If that is the case, I'm happy to send a PR to document this a bit more. |
It's up to the projects for where they want to keep those copies, there isn't one standard way to do this. |
They can or they should? Wouldn't it be better to standardize given the risks pointed out in #980? I think we had consensus there on this. |
Tom - because we don't have this currently as a requirement for moving levels, its recommended these be moved, however we can't enforce projects to move those files. This is planned to be addressed as part of the moving levels update so its consistent moving forward. I've captured it here: cncf/tag-contributor-strategy#366 (comment) so we don't lose track of this. |
Wonderful, that's what I was thinking as well - Thanks @TheFoxAtWork! |
Now that #980 is completed and KEDA is in public comment period for our Graduation proposal I am wondering what the procedure is to move documents in to the CNCF based workspace?
Should we just file an issue or work with service desk instead?
From what I'm seeing, when KEDA's public comment period is over we can move it to CNCF workspace.
Tasks
The text was updated successfully, but these errors were encountered: