Team Votes(#456)

Back
ID Category Title Creator Status Result
456organizationWhen temporarily disabling anything (infrastructure, code, doesn't matter) without an explicit expiration time or certain undoing action such as a server reboot, whoever did the disabling should always and immediately file an issue on Gitlab (or another pre-agreed-upon place with a process for handling, such as a XONRELEASE TODO comment if applicable) to document the disablement and track the re-enablement, including instructions for how to re-enable and what conditions are necessary to re-enable. If possible, a backlink should be placed (e.g. the commented out section should point at the Gitlab issue with another comment) - if this isn't possible, fine (e.g. when temporarily setting a bot Matrix power level to -1 to mute it).divVerentPASSED5:0(0 abstained, 11 didn't vote)
-
User Decision Comment
AsciiWolfNONE
FreddyYES
AntibodyNONE
bones_was_hereNONE
divVerentYESThis serves to reduce pressure on people trying to fix it, and also to prevent the disablement from sticking around for longer because nobody thought of re-enabling (e.g. due to getting distracted, or investigation taking longer and losing context).
Dr. JaskaYESThis will add some additional burden, at times possibly unnecessarily if followed literally, but it can save a lot of effort in the long run. For now this vote and its wording looks good to me.
HalogeneNONE
illwieckzNONE
k9erNONE
LegendGuardNONE
morosophosNONE
MrBougoNONE
NitroxisNONE
Spike29YES
terencehillYES
z411NONE