by Jeff Lewis.
Again, what clearly needs to be implemented now, no matter what, is a Warning System To Protect Moodlers from Serious Bugs that pose a Destructive or Highly Disruptive Threat. Priorities do need to be set, so there will always be a lag time in fixing anything. But time is precious for everyone, and users deserve to be protected, as a matter of conscience, if nothing else.
For example, I can certainly understand why fixing even a destructive bug in a plugin like Reengagement might be a lower priority than fixing a purely annoying one that's impacting a much larger user base. Still, that doesn't justify subjecting Reengagement users to the violence, yes violence, of a known bug that can/will/did literally destroy their hard work. It's one thing when the bug is unknown, and quite another when users are being consciously subjected to a destructive threat, if not yet a reality. The user whose work was destroyed two years ago should have been enough; there was absolutely no justifiable reason to subject me to that loss, let alone all the unsuspecting Reengagement users out there that still don't realize their content is not actually getting backed up.
This is even more abusive to those of us who are not just working on an underfunded and understaffed endeavor, but doing so on a purely volunteer, nonprofit basis, though I'm sure a capitalist would think their bottom line is worth protecting more than a volunteer's time. 🙂
I just checked the Reengagement Activity plugin (https://docs.moodle.org/400/en/Reengagement_activity), and still don't see any mention of this destructive, not just annoying, bug, despite this discussion. How 'bout starting with this?! Still, I am curious how much this is a global issue with Moodle in general, and not just an issue for Reengagement.
For example, I can certainly understand why fixing even a destructive bug in a plugin like Reengagement might be a lower priority than fixing a purely annoying one that's impacting a much larger user base. Still, that doesn't justify subjecting Reengagement users to the violence, yes violence, of a known bug that can/will/did literally destroy their hard work. It's one thing when the bug is unknown, and quite another when users are being consciously subjected to a destructive threat, if not yet a reality. The user whose work was destroyed two years ago should have been enough; there was absolutely no justifiable reason to subject me to that loss, let alone all the unsuspecting Reengagement users out there that still don't realize their content is not actually getting backed up.
This is even more abusive to those of us who are not just working on an underfunded and understaffed endeavor, but doing so on a purely volunteer, nonprofit basis, though I'm sure a capitalist would think their bottom line is worth protecting more than a volunteer's time. 🙂
I just checked the Reengagement Activity plugin (https://docs.moodle.org/400/en/Reengagement_activity), and still don't see any mention of this destructive, not just annoying, bug, despite this discussion. How 'bout starting with this?! Still, I am curious how much this is a global issue with Moodle in general, and not just an issue for Reengagement.