-
Notifications
You must be signed in to change notification settings - Fork 198
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
New Release and new maintainer #279
Comments
Gentle ping @nkubala @tstromberg, if you need any help, I'm willing to work on this, as we (the Jenkins Infra) team are relying on this project |
hey @dduportal, first of all thank you so much for stepping up on this, and so sorry it's taking us so long to get back to you! I'm working on putting together a strategy for opening up this project to external maintainers, and was hoping to have something set up before responding here, but I shouldn't have kept you in the dark. we haven't agreed on a strategy quite yet, but I'd absolutely love to have your help on the project. I'll be reaching out to you once we have something, so please stay tuned! |
Hello @nkubala , thanks for the heads up. I'll wait for your feedback but please keep in mind that it seems that there are other requests by other users as well :) |
Hi @nkubala is there any news on this? |
Following. It would go a long way toward making me comfortable using this tool if I was sure it had a future. |
I'd be willing to help with casual contributions as well. |
+1 I am currently exploring the possible of using container-structure-test as a declarative testing utility for https://buildpacks.io (See buildpacks/rfcs#205 and https://github.com/samj1912/buildpacks-venom-executor/blob/3360e7afbc518dac953a2f74daebb299a03f8a6e/examples/paketo-go/test.yaml#L18 for a POC). Would be happy to help out as well. |
Is there any news on this topic? |
Bumping for awareness. I'd like to volunteer myself to help out and close out some open issues. |
Hello @nkubala @tstromberg ,
First of all, thanks for all your effort and time put in this project.
As per #274 (comment), it seems there isn't someone with enough bandwidth to release this project, or to take issues/triage/PR in account.
Would you be willing to add new maintainers to share the burden? In that case I would volunteer.
The text was updated successfully, but these errors were encountered: