-
Notifications
You must be signed in to change notification settings - Fork 210
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
Evaluation of infrastructure provisioning related topics #589
Comments
Will assign this to @GenPage as soon as possible :-) |
I would be interested in joining the workgroup😁 |
I'm very interested to participate in this! |
Initial conversation with @angellk suggested we rename from "Infrastructure Provisioning" to "Infrastructure Lifecycle". 👍 Also, we're working on getting a draft charter up and reaching out to related pending/accepted projects in the ecosystem. Once we have the groundwork started, we'll most likely then start organizing some community meetings |
I would be really interested to partecipate in this working group! |
What's the best way to help with this effort? Just wait, and follow this issue? |
@mbarr-hrp Yes, we will be announcing a charter, slack channel, and regular meetings very soon. |
There is a slack channel on the CNCF slack: https://cloud-native.slack.com/archives/C06USDTN683 We meet bi-weekly on Fridays at noon EDT while we draft a charter: https://zoom-lfx.platform.linuxfoundation.org/meetings/cncf |
Charter Proposal PR: #691 |
To deploy applications successfully, there are efforts that often go hand in hand with infrastructure provisioning and deployment. As we see more projects from the infrastructure space in our TAG and identified (at a poll at KubeCon) that we should get more active in this area, there should be first investigations if it makes sense to build a working group for such topics, if there are enough interested people in this and what the potential scope. of the WG could be.
@GenPage initiated and volunteered to drive this topic, @angellk and @thschue will support his efforts from the TAG side.
Tasks
The text was updated successfully, but these errors were encountered: