-
Notifications
You must be signed in to change notification settings - Fork 10
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
Being added to the https://github.com/containers org #71
Comments
I definitely approve of this and am excited for podlet to be a part of a larger organization! I'm going to ping everyone who has contributed to podlet to make sure they ok with this. Everyone please comment either your approval or any concerns/questions you have. Anyone else is free to jump in to this discussion as well! |
Yes, definitely ok with me! |
That sounds great! |
Sure! Do it! That's awesome! 🎉 |
@k9withabone i have issued an invite to you for joining the org. It looks like you can do the transfer and setup from there. |
Awesome! Just got word from the team. @k9withabone You should have received an invite from the containers org so you can initialize the transfer. If you are able to create a CODE-OF-CONDUCT.md and SECURITY.md as well to match our other orgs, that'd be awesome. You can copy them from a repo such as https://github.com/containers/buildah (you can just replace anything with buildah with podlet). |
Ok, podlet is now a part of the containers org! Here's a list of what I think is left to do:
|
According to the Cargo book, it looks like I can add an org team to the package owners. @baude is it ok if I create a "podlet-maintainers" team? |
Updated the to-dos based on the conversation from the podman email list. |
Hi all! Charlie from the Podman Desktop team.
I've been in talks with the containers org, and we'd like to have you be apart of it considering the closeness this tool is to podman.
Podlet is amazing at generating the systemd files and it'd be great to have it be apart of the containers organization.
Let me know if you are all on board with this!
The text was updated successfully, but these errors were encountered: