Description: MOD_DESCRIPTION
Date First Discussed: DATE_FIRST_DISCUSSED
Date Most Recently Discussed: DATE_MOST_RECENTLY_DISCUSSED

Proposals

The following are proposals for this mod, in ranked order.

• PROPOSAL_1 (Proposal Date: DATE_1; Avg. rating: AVG_RATING_1; Accepted)
• PROPOSAL_2 (Proposal Date: DATE_2; Avg. rating: AVG_RATING_2; Accepted)
• PROPOSAL_3 (Proposal Date: DATE_3; Avg. rating: AVG_RATING_3; Accepted)
• PROPOSAL_4 (Proposal Date: DATE_4; Avg. rating: AVG_RATING_4; Blocked)
• PROPOSAL_5 (Proposal Date: DATE_5; Avg. rating: AVG_RATING_5; Blocked)

Description: Queerious Labs can be secured when not in use, and users of the space can get into the space to make use of it with minimal bureaucratic overhead.
Date First Discussed: N/A
Date Most Recently Discussed: N/A

Proposals

The following are proposals for this mod, in ranked order.

• No proposals yet.

Description: Queerious Labs's tools are usable, well-maintained, and accessible to people who need to use them.
Date First Discussed: 2019-09-21
Date Most Recently Discussed: 2019-10-12

Details

The top rated proposal was to have tool-specific constraints on usage. To support this, we discussed some options for what
we can do. The ideas we settled on were as follows:

1. Have a README template that we can fill out and print and laminate and then mount on the constrained tools to point people to information about the tool and its constraints on usage.
2. Have a general info sheet we can give people explaining that some tools will have tool-specific constraints on usage, and that information about the tool will be posted on the tool.
3. Have a mailing list that makes it easy for people to get in touch with folx who are responsible for the tool-specific constraints.

Proposals

The following are proposals for this mod, with their ratings to their left. They have been sorted by average rating.

• 4.666666667 = Have tool-specific constraints on usage
• 4.5 = If it breaks, post to the mailing list about it.
• 4.4 = Have a maintenance schedule
• 4.333333333 = Talk together about “important” equipment to establish norms around it
• 4.166666667 = If it breaks, leave a note about the problem.
• 4.166666667 = Require explicit permission for certain tool use
• 4 = If it breaks, tell someone about the problem.
• 4 = Soviets/User Groups which define tool-specific policies, etc. vs space-wide policies, and coordinate around needs, etc.
• 4 = Online “form” or page w/ info and agreements for use
• 3.833333333 = If it breaks, post about it to discourse.
• 3.833333333 = Avoid short term hacks to fix things / prefer “correct”/“standard” repairs
• 3.833333333 = Handouts w/ policy info
• 3.333333333 = Require explicit permission for tool hacking/fixing
• 3.333333333 = Require repair training before tool repair/hacking
• 3.166666667 = Require safety and basic use (SBU) training before tool use
• 3 = Hold scheduled supervised use times where the supervisor is only responsible for the sticking to the process, not for assisting or teaching
• 2.833333333 = Hold scheduled supervised use times where the supervisor is responsible for the sticking to the process, including assisting or teaching
• 2.5 = Tool signout system / sign out a tool w/ a tool librarian or a signout computer before being able to use it
• 1.833333333 = Do nothing
• 1.666666667 = Require explicit permission for any tool use