Good point @ contacting discuss@ either way. I added that to the wiki page.
The "toilet issue" was simply that the toilets got plugged up and we didn't have a plunger. Mak brought a plunger the next morning, and Adrian fixed them. Nothing complicated. What IS complicated is the number of emails, text messages, and IRC messages that went to various people, and that became increasingly more insulting and irritating and confusing. Ian joked privately that we need to have a "post mortum investigation" where we review access logs and camera footage to determine blahblahblah - the point is that it was way overblown because we don't really have a process for this sorta thing. And hehe, I said "shit" in a story about shit. :) Ron On 2013-05-06 10:06, Justin Lacko wrote: > Sounds like the right way to handle things. What was the "toilet issue" > anyways? I saw some emails on the subject but didn't even know it had > escalated this much... > > I think it makes sense to send an email to discuss@ as well, to let people > know that a problem has been identified and admin@ has been contacted, so > admin@ doesn't get emails from multiple people for the same issue. > > Also lol at a toilet incident and you saying we don't need any of "that > shit." :) > > > On 6 May 2013 09:36, Ron <[email protected]> wrote: > > > Hey all, > > > > If last week's "toilet incident" has told me anything, it's that we > > don't know how to handle issues properly as a group without driving each > > other nuts or shaming each other, so let me propose a more formal > > process. > > > > I posted mostly this text to the following wiki page, please edit if you > > disagree or can think of a better way to handle something: > > > > http://www.skullspace.ca/wiki/index.php/Incident_handling > > > > Also, I realize this is a little long, but I think it's important to > > read... > > > > == > > > > If you notice a problem at the space that needs speedy resolution (like > > plugged toilets), you have ownership of the problem until you pass it on > > to somebody else (don't worry, it's easy!) - here's what to do: > > > > 1. If you can fix the problem yourself, there's somebody around who can > > fix it, or you know the "right" person to contact, let them know > > directly and they can choose to take ownership (please email admin@ when > > it's resolved so we know what's going on). > > > > 2. If you can't fix the problem yourself or you don't know who to ask or > > the 'right' person is unable/unwilling to take ownership, and it's a > > problem that another member might be able to help with, email discuss@. > > > > If you are on discuss@ and you can't help, please don't reply; only > > reply if you can actually make a difference (we don't need extra > > noise/chatter). Replying = taking ownership (though you can pass it off > > to admin@ any time). > > > > 3. If it's something discuss@ can't resolve (eg, an issue with the > > landlord or a legal issue), or discuss@ doesn't resolve it in a > > reasonable amount of time ("reasonable" depends on the problem, > > obviously), escalate to admin@. Somebody on admin@ will take ownership > > and make sure it gets done. Once you've done that, please drop it. > > > > Please don't act on behalf of admin@ if it's something serious, or > > especially if it's something that threatens our safety (either > > physically or as an organization). Escalate to admin@. > > > > 3a. If it's a network issue, and email is still available, email > > netops@. If it's a network issue and email is *not* available, please > > contact Colin Stanners, Mak, or myself. > > > > 4. Once it's resolved, if admin@ wasn't involved, please let admin@ know > > it happened, and how it was fixed. > > > > The things we *don't* need are: > > - An avalanche of emails and/or text messages to a variety of different > > people > > - Confusion about who owns an issue > > - ie, an abundance of people contacted to help, none of whom know who > > else is involved or WTF is going on > > - Shaming - either public or private, and either before or after > > - Massive overreactions > > - Please don't email individual board members unless there's a very good > > reason - just email admin@ so we can take care of it as needed, that's > > why we're here! > > > > ^ All of which happened, for some insane reason, during the "toilet > > incident". Seriously people, that was not a complicated problem, and it > > was easily resolved. We don't need any of that shit. Just contact the > > right people and let the problem work itself out. > > > > TL;DR: If you notice a problem, you own it. If you think it'll help, > > alert discuss@ - where somebody else can take ownership if they're able > > to - or admin@ - where somebody definitely will. Once somebody else > > takes ownership, drop it. Whenever it gets resolved, the current owner > > should email admin@ with what happened and how it was fixed. Unless it's > > a plugged toilet, in which case, who the hell cares? Just deal with it. > > > > Hope that clears things up! Edit the wiki page if you think you can do > > something better! > > > > Ron > > _______________________________________________ > > SkullSpace Discuss Mailing List > > Help: http://www.skullspace.ca/wiki/index.php/Mailing_List#Discuss > > Archive: https://groups.google.com/group/skullspace-discuss-archive/ > > > _______________________________________________ > SkullSpace Discuss Mailing List > Help: http://www.skullspace.ca/wiki/index.php/Mailing_List#Discuss > Archive: https://groups.google.com/group/skullspace-discuss-archive/ _______________________________________________ SkullSpace Discuss Mailing List Help: http://www.skullspace.ca/wiki/index.php/Mailing_List#Discuss Archive: https://groups.google.com/group/skullspace-discuss-archive/
