Add DevContainer Definitons For One-Click Dev Env Setup about cloud-provider-gcp HOT 6 OPEN

Hi, thanks for the offer, I don't think this is something anyone is prepared to maintain at the moment.

There's some cleanup work ongoing and this is probably something to consider down the line.

@BenTheElder That's fair. Thank you for responding.
For when you have the bandwidth later on: I'm not a maintainer, but would be happy to keep it up to date with smaller contributions (fixing CVEs, bumping compiler versions, etc. - the mundane stuff).

from cloud-provider-gcp.

This issue is currently awaiting triage.

If the repository mantainers determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

from cloud-provider-gcp.

Hi, thanks for the offer, I don't think this is something anyone is prepared to maintain at the moment.

There's some cleanup work ongoing and this is probably something to consider down the line.

from cloud-provider-gcp.

Thanks!

I'm not sure to what extent I'm personally going to stay involved, for now helping escalate / coordinate some of the more pressing gaps like #686 re: cloud provider extraction, I think we're still figuring out who will handle what long term and then go from there, but I'd like to think anyone would be happy to accept help like this.

At the moment I think approvers will be a bit buried in some time-sensitive projects like #683 #686 😅, longer term personally I'd like to see enhancements to the development process etc but I can't commit yet versus existing responsibilities in the broader kubernetes project and internally ...

from cloud-provider-gcp.

Thanks!

I'm not sure to what extent I'm personally going to stay involved, for now helping escalate / coordinate some of the more pressing gaps like #686 re: cloud provider extraction, I think we're still figuring out who will handle what long term and then go from there, but I'd like to think anyone would be happy to accept help like this.

At the moment I think approvers will be a bit buried in some time-sensitive projects like #683 #686 😅, longer term personally I'd like to see enhancements to the development process etc but I can't commit yet versus existing responsibilities in the broader kubernetes project and internally ...

@BenTheElder Got it, thank you for responding! :-)

from cloud-provider-gcp.

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

from cloud-provider-gcp.