Re:Underproduction: An Approach for Measuring Risk in Open S...
by the__alchemist on Tuesday March 30, 2021 @10:19AM
(#26634875)
I've noticed this in the Rust embedded community, especially with STM32 HALs. Each MCU family is run by its own maintainers, and despite the overlap in the hardware, there's fragmentation among features and code style among between the HALs.
The part about priorities is especially relevant - A user of the library may care mostly about features, and correct implementation on a hardware layer, while the repo owners (who don't have much time available) stall bug fix and feature PRs over code style disagreements, long-term maintainability concerns, or not (no longer?) having the time available.
The code style issues can turn what looks to a use to be a clean kill (fixing a bug, adding a peripheral), into an extended back-and-forth, where one party loses interest.
The part about priorities is especially relevant - A user of the library may care mostly about features, and correct implementation on a hardware layer, while the repo owners (who don't have much time available) stall bug fix and feature PRs over code style disagreements, long-term maintainability concerns, or not (no longer?) having the time available.
The code style issues can turn what looks to a use to be a clean kill (fixing a bug, adding a peripheral), into an extended back-and-forth, where one party loses interest.