Take a look at the timeSinceRotation function in the BaseWeightedMultisig contract:
This function is not used within the contract. However, its functionality could be utilized in the _updateRotationTimestamp function:
The (currentTimestamp - lastRotationTimestamp_) calculation in _updateRotationTimestamp duplicates the logic in timeSinceRotation.
QA, this is a code quality issue with no direct security implications. However, it represents a missed opportunity for code reuse and improved readability.
To improve code quality and readability, utilize the timeSinceRotation function in _updateRotationTimestamp:
