-
-
Notifications
You must be signed in to change notification settings - Fork 135
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 fork of VaultSharp #118
Comments
👍 thanks! @rajanadar Would be good to get access to push to nuget |
First, I thank you for the support. Second, I apologize for the break. Had a personal medical emergency for a few months. Irrespective of that, I should have added collaborators to this project. I have now added both of you, so that this doesn't happen again EVER. The plan is as follows.
Thanks. |
Hello @rajanadar, glad to hear from you. Hope you are doing well. What do you think about completely moving it to VaultSharp organization? You will have Admin permissions there. In this way, the community will be able to support the project when you (or any of us) are busy. The organization is a great place to start. If you reject, I think, we will continue to work on the separate package to avoid such situations. But let's do cool things together. This is Open Source, your great idea with VaultSharp already have a community, and we ready to help you to improve it. What do you think? |
At this point, there is the full history of the project in this repo, along with all issues, right NuGet package names, the documentation website and also closing down on a million download. I am full steam on 1.4.x efforts starting next week. I have a lot of other colleagues and projects who work off my fork as well. I would love to not disrupt them. I totally understand the concern of another break, and am ready to make you and any number of other folks who were active and passionate, as collaborators to avoid this issue in the future. |
You always can move this project with the full history of the project in this repo, along with all issues to organization. What is the problem?
I think it is a little bit late. If you don't want community help, then why do you put this project to OpenSource?
really? I can show you my PR, with the text "Let me look at this in a couple of days". It will take almost a year :(
I say again, we are not going to break this project!!! and package!! We will move it to the organization and continue to develop it with you |
@Marusyk, |
@rajanadar what do you mean? |
|
A few of us Vaultsharp users got impatient with the lack of progress here, so we have created a fork of VaultSharp to be found here: https://github.com/VaultSharp/VaultSharp/
Please note that we really appreciate the work of @rajanadar and we welcome him to collaborate if he again wants to participate in the vaultsharp community.
Since the VaultSharp package on nuget.org is owned by @rajanadar we could not publish the fork under the old name, so the fork is published under the name "VaultSharp.vNext" : https://www.nuget.org/packages/VaultSharp.vNext/
The text was updated successfully, but these errors were encountered: