If something is required that can't be donated, contact admin@. That's always the place to go if there's something you can't handle. It's our job to take care of stuff like that.
If it's an actual *emergency* - ie, water is flowing or a fire is burning - either bankroll it yourself or take the money from the donation/drink box, and in either case we'll sort it out after. But only do that if you can't get ahold of admin@ first, or, like I said, it's an emergency. I updated the wiki page to say the emergency stuff. Ron On 2013-05-06 10:18, Roswyne wrote: > One thing that could be a factor in resolving an issue is money. If parts > are required, whoever's on site may not have cash on hand (or > transportation) to get them. > > Is that a "bump to admin" thing, or could the donation bin be used to cover > the cost? (if so, should admin approval be needed?) > On May 6, 2013 9:35 AM, "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/
