4 ms·
If you don't like the current maintainers' policy on "future project direction", you can always fork the project. Yes, this involves an increased maintenance b
by 0815test 7y ago
If you don't like the current maintainers' policy on "future project direction", you can always fork the project.
Yes, this involves an increased maintenance burden since you need to actively review what the upstream is doing and figure out how to cleanly pull their changes - but guess what, that's the very same burden that dealing with your proposed changes would have placed on the upstream themselves! "Authoritarianism" doesn't really come into it.
- traverseda 7y agoThere are ways to architect software so that it can be cooperatively developed, so that you can fork and maintain an individual component instead of an entire stack.