Difference between revisions of "Danger committee"

From Pumping Station One
Jump to navigation Jump to search
Line 1: Line 1:
{{NeedsUpdate|This page is somewhat confusing. If Danger Committees are formal (even if informal), attention should be brought to it for each piece of equipment, and more information on the process provided on this page.}}
+
When we get a new tool like the Bridgeport or ShopBot, initially nobody is authorized, or trained as an authorizer, and nobody can authorize others. To solve the chicken and egg problem, an ad hoc group forms around the tool that becomes the initial group of authorized uses. They figure the tool out, determine what is dangerous about it, address safety issues, acquire initial tooling, perform setup and calibration, etc. They clear the way for the membership to use the tool. They also form the pool of initial authorizers to get other people trained and authorized.
  
The "Danger Committee" is the unofficial official term for the first group of hackers to figure out what is too dangerous to do with a new tool where we don't necessarily have a lot of knowledge or experience. The name is also a joke because it's a "safety committee" that has been hackerspaceified. Generally speaking, what a danger committee is or does has to adapt heavily depending on the tool or equipment being researched, so it's most frequently explained with examples instead of definitions.
+
The "Danger Committee" is the unofficial official term for the first group of hackers to figure out what is dangerous about a new tool. The name is tongue-in-cheek because it's a "safety committee" that has been hackerspaceified. What a danger committee is or does will adapt heavily to tool or equipment being researched.
 +
 +
As many tools at PS:One allow for any authorized member to authorize any other member, there is not always a danger committee.
  
It also has a role to play in authorizations. When we get a new tool like the Bridgeport or ShopBot, nobody initially is authorized, so nobody can in turn authorize others. To solve the chicken and egg problem, an ad hoc group forms around the tool that becomes the initial group of authorized uses. They in turn figure the tool out, figure what is dangerous about it, remediate safety issues, acquire initial tooling, perform setup and calibration, etc. In other words, they clear the way for the membership to use the tool. They also form the pool of initial authorizers to get other people trained and authorized.
+
A danger committee's role is over, mostly, once procedures for authorization and operation have been determined.  
  
As many tools at PS:One allow for any authorized member to authorize any other member, the danger committee often fades into obscurity.
+
Who forms a danger committee? [[JFDI]], or the owner of the tool, or the Board, or the Area Host.

Revision as of 19:20, 2 December 2017

When we get a new tool like the Bridgeport or ShopBot, initially nobody is authorized, or trained as an authorizer, and nobody can authorize others. To solve the chicken and egg problem, an ad hoc group forms around the tool that becomes the initial group of authorized uses. They figure the tool out, determine what is dangerous about it, address safety issues, acquire initial tooling, perform setup and calibration, etc. They clear the way for the membership to use the tool. They also form the pool of initial authorizers to get other people trained and authorized.

The "Danger Committee" is the unofficial official term for the first group of hackers to figure out what is dangerous about a new tool. The name is tongue-in-cheek because it's a "safety committee" that has been hackerspaceified. What a danger committee is or does will adapt heavily to tool or equipment being researched.

As many tools at PS:One allow for any authorized member to authorize any other member, there is not always a danger committee.

A danger committee's role is over, mostly, once procedures for authorization and operation have been determined.

Who forms a danger committee? JFDI, or the owner of the tool, or the Board, or the Area Host.