The KeePassXC people are also volunteers and dealing with the fallout of this decision.
True, but let them settle it without turning a few thousand people against one person.
well it is that one person causing issues
If by issues you mean looking out for people's privacy sure, someone has to.
by issues I mean breaking existing users' workflow, possibly literally locking them out (I personally use a yubikey with my keepass db, for example).
There is a very simple solution he could have done: not rename the existing package. Just give his fork a new name. That's it, everybody is happy.
So yes, he is the one causing issues. Because the issue isn't in the features he removed, but by breaking the users'expectation that the package they installed yesterday, is the same one they're updating today.
The KeePassXC people are also volunteers and dealing with the fallout of this decision.
True, but let them settle it without turning a few thousand people against one person.
well it is that one person causing issues
If by issues you mean looking out for people's privacy sure, someone has to.
by issues I mean breaking existing users' workflow, possibly literally locking them out (I personally use a yubikey with my keepass db, for example).
There is a very simple solution he could have done: not rename the existing package. Just give his fork a new name. That's it, everybody is happy.
So yes, he is the one causing issues. Because the issue isn't in the features he removed, but by breaking the users'expectation that the package they installed yesterday, is the same one they're updating today.