4 ms·
If you were curious like I was, about why this fork was necessary, I found this on their About page: KeePassXC is a community fork of KeePassX which aims to in
by dublinben 10y ago
If you were curious like I was, about why this fork was necessary, I found this on their About page:
KeePassXC is a community fork of KeePassX which aims to incorporate stalled pull requests, features, and bug fixes that have never made it into the main KeePassX repository.
- sleavey 10y agoDo you know why they have been stalled? Perhaps there's a good reason, like code auditing? Just a shot in the dark - I have no idea.
- roddux 10y agoJudging from TFA it's due to KeePassX having one maintainer, so the pull requests all bottleneck with him. Also mentioned is that one desirable outcome of this is that KeePassXC developers are given co-maintainer status of KeePassX and that they re-merge down the line.
- shincert 10y agoThat's cool. But if that's all this project is, couldn't they have just talked to the one maintainer and offer to help him and be on the team?
- roddux 10y agoI would assume that avenue has been tried -- so this project is to pressurise him into opening up to the idea. No idea though.
- zymhan 10y agoI wonder how often those conversations take place before someone(s) fork a project because it's "abandoned". But I love KeepassX and I'll certainly try using the fork.
- thecardcheat 10y agohttps://github.com/keepassxreboot/keepassxc/issues/43 https://github.com/keepassxreboot/keepassxc/issues/43 states the maintainer hasn't been commenting on PRs. I looked on the keepassx GitHub and some issues with no response are over 2 years old.