You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@norwoodj created this tool, and it's wonderful! I would like to propose a change to make the project take the next steps to becoming even more of a core tool in the Helm / K8s / open-source toolchain: moving to a new organization!
Since this project is now being maintained by several people other than the creator @norwoodj, I think we should move the project (and other associated repositories) to the https://github.com/helm-docs organization. As a huge fan of this project, I reserved this organization name a while ago to make sure no one else snatched it.
This issue will serve as a placeholder for the work of moving things over to the new organization, if it's approved of course.
After creating this issue, I will make @norwoodj the Owner of the organization; afterwards he can remove me, and add whomever else he would like.
Let's do this!
Is your feature request related to a problem? Please describe and/or link to a bug issue.
Hey @sc250024. Thanks for taking the time to create this organization and this issue. I think this is a good idea and I will plan to transfer the repository to that organization. I just want to be sure before doing so that this won't mess with any of the changes that @Nepo26 has made to the repository recently.
Henrique has kindly been helping organize issues, clean up the repository, review PRs, etc. In short, all of the things I should have been doing but never get the time to do. I, (and everyone else who cares about this project) owe him a tremendous debt of gratitude.
Anyway, if Henrique gives the okay that making this change won't cause any problems for him, I'm happy to move the repository. In the meantime, I've added him to the helm-docs organization as well.
@norwoodj feel free to remove me from the organization. I didn't create it with the intention of inserting myself as an owner. It was just to reserve the name.
Hey @sc250024, thank you! This may help us standardize the name and make it better.
@norwoodj the main problem with changing the organization right now is messing with people's pipeline that get from our releases.
So I think we could align it to probably change to the new organization after we select the main points for 2.0 and finish them. Nevertheless, we can expect it to be all ok by Q2 2024. What do you think ?
General Summary
@norwoodj created this tool, and it's wonderful! I would like to propose a change to make the project take the next steps to becoming even more of a core tool in the Helm / K8s / open-source toolchain: moving to a new organization!
Since this project is now being maintained by several people other than the creator @norwoodj, I think we should move the project (and other associated repositories) to the https://github.com/helm-docs organization. As a huge fan of this project, I reserved this organization name a while ago to make sure no one else snatched it.
This issue will serve as a placeholder for the work of moving things over to the new organization, if it's approved of course.
After creating this issue, I will make @norwoodj the Owner of the organization; afterwards he can remove me, and add whomever else he would like.
Let's do this!
Is your feature request related to a problem? Please describe and/or link to a bug issue.
This is a feature request to move https://github.com/norwoodj/helm-docs (and all needed repositories) to the https://github.com/helm-docs organization.
Expected Behavior
No response
Current Behavior
No response
Possible Solution
No response
Alternatives you've considered
No response
Further Information
No response
The text was updated successfully, but these errors were encountered: