-
Notifications
You must be signed in to change notification settings - Fork 229
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
Approve the proposal to move Knative test infra to be community-managed #786
Comments
/project Open for community feedback |
@chizhg: You must be a member of the knative/community github team to set the project and column. 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. |
@chizhg , we mostly use org-level projects which allow anyone in the org to move / add items, rather than the prow commands. (I added the TOC label for you.) |
Issue currently assigned to me while we look at possibility of Google continuing to host on GCP, or using a crowdfunding site for oss project costs. Examples of those sites are https://lfx.linuxfoundation.org/tools/crowdfunding and https://opencollective.com/opensource |
We are doing this, but it doesn't feel like we need to approve a specific design document at the moment. It would be nice to cut over this infrastructure maybe a week or so after a release from a logistical point of view. |
The proposal has already been approved as Knative is going to be donated to CNCF. The sections in the Knative test infrastructure 1.0proposal have been broken down into separate issues, which are now being tracked in https://github.com/orgs/knative/projects/40/views/11. We are actively working on these issues, and the ETA to resolve them is aligned with the finalization of CNCF donation. Resolving this issue. |
Knative test infrastructure 1.0 is the proposal that aims at solving the below long-standing issues by moving Knative test infra to be community-managed:
The community has decided these should happen post-1.0. But before that, it'll be ideal to have the proposal approved first, so that we can plan on resources ahead.
Since the proposal requires changes that involve multiple parties, it needs to be approved by both Steering Committee and TOC.
The text was updated successfully, but these errors were encountered: