-
Notifications
You must be signed in to change notification settings - Fork 849
chore: Update README with fork info #1270
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
base: master
Are you sure you want to change the base?
Conversation
|
||
> [!WARNING] | ||
> This project has been abandoned and it's not receiving any more updates. If you want to continue to receive updates | ||
> or contribute, please feel free to look at the active fork at: https://github.com/ByteNess/aws-vault |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
there are currently multiple forks.
if you can add a list of alternatives, I'll approve
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If there is a list I'm happy to add it to the PR!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@FernandoMiguel also a question, would you be interested in donating the project to one of the forks to ensure continued maintenance? It'd also remove splintering the community and enable use to update packagers, like brew
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i dont have the power for that. just an old time contributor with merge privs
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No worries, if anyone pops up with other forks I'm happy to add this now, but otherwise we could merge this and add others later?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@FernandoMiguel shall we merge this now or do you want to add something else?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Anything else we need for this PR?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@FernandoMiguel are you happy merging this to make it clear where people can find a maintained fork?
This project seems to be abandoned and I've created a fork where we can continue to update and contribute as an community. I've also bumped deps and addresses some of the security issues.
In case anyone can still merge thing, I suggest we redirect users to an active fork. We'll also need to do something like this if we want to preserve naming in the existing packaging.