Repository navigation
Equipment tagging at DoES
Something broken, unsafe, or needing attention? Log it, then tag it.
The maintenance tag plate lives in the main space, under the Liver Bird light. It holds:
| What | Colour / look | Use it when |
|---|---|---|
| OUT OF SERVICE card | Red plastic | Do not use this machine |
| MAINTENANCE REQUIRED card | Yellow plastic | Usable with caution; something needs fixing |
| Paper gift tags + elastic | White paper | Always: write the GitHub issue number on these |
| Pen | In the front channel | Fill in the paper tag |
Plastic cards are reusable. Paper tags are disposable (hang them with the elastic).
flowchart TD
A["You notice a problem"] --> B{"Can you fix it safely right now?"}
B -->|Yes| C["Fix it"]
C --> D{"Worth recording?"}
D -->|Yes| E["Open a somebody-should issue and close it when done"]
D -->|No| Z["Done"]
B -->|No| F["Open a somebody-should issue"]
F --> G["Note the issue number e.g. 2240"]
G --> H{"Is the machine unsafe or unusable?"}
H -->|Yes do not use| I["Take a RED OUT OF SERVICE card"]
H -->|No use with care| J["Take a YELLOW MAINTENANCE REQUIRED card"]
I --> K["Write the issue number on a paper tag"]
J --> K
K --> L["Hang paper tag and plastic card on the machine"]
L --> M["Add labels on the GitHub issue Tool plus Broken or Maintenance or Bug"]
M --> N["Leave the plate tidy pen back in the slot"]
Open a new issue:
https://github.com/DoESLiverpool/somebody-should/issues/new
Keep it S.M.A.R.T.: what broke, where it is, and what “fixed” looks like.
You need the issue number (e.g. #2240) before you walk over to the machine. That number is the link between the physical tag and the tracker.
flowchart LR
Q{"Can someone safely keep using this?"} -->|No| R["RED OUT OF SERVICE"]
Q -->|Yes but be careful| Y["YELLOW MAINTENANCE REQUIRED"]
| Card | Means | Typical GitHub labels |
|---|---|---|
| OUT OF SERVICE (red) | Do not use. Power off / leave alone if that is safer. | Tool label + Broken
|
| MAINTENANCE REQUIRED (yellow) | Proceed with caution. Something still needs doing. | Tool label + Maintenance (routine) or Bug (one-off / transient) |
If you are unsure, prefer red / OUT OF SERVICE. Safer for the next person.
- Take a paper tag and the pen from the plate.
- Write clearly:
-
Issue number (e.g.
#2240): required - Short note (optional): what failed, date, your name
-
Issue number (e.g.
- Put the elastic through the reinforced hole.
- Hang the paper tag on the machine (handle, frame, or somewhere obvious, not covering a safety switch).
- Clip or hang the matching red or yellow plastic card with it so the status is visible from across the room.
The plastic cards already say “GIT ISSUE NUMBER ON TAG”; that means the paper tag. You do not need to write on the plastic.
On the issue sidebar, add:
- The Tool: label for that machine (if it has one)
-
Broken,Maintenance, orBugas above - A Room: or priority label if you know them (
1 - Must DoES, etc.)
Full label guide: CONTRIBUTING.md
flowchart TD
A["Machine is fixed"] --> B["Remove paper tag and plastic card"]
B --> C["Bin or recycle the paper tag"]
C --> D["Return the plastic card to the plate"]
D --> E["Close the GitHub issue add a short comment saying what fixed it"]
E --> F["Remove Broken Maintenance or Bug if you are closing the issue"]
Do not leave a red or yellow card on a working machine. The next person will trust the tag.
| Bay on the plate | Contents |
|---|---|
| OUT OF SERVICE | Red plastic cards |
| MAINTENANCE | Yellow plastic cards |
| PAPER | Blank gift tags (hole toward the string bay) |
| STRING | Spare elastics (drop them through the slot in the divider) |
| PEN | Biro / Sharpie |
If the plate is empty of paper tags or the pen has wandered, open a shopping / supplies issue on somebody-should, or restock it yourself.
You can print or pin this next to the plate:
Broken kit?
- Open an issue → somebody-should / new
- Write the #number on a paper tag
- Hang it with a red card (do not use) or a yellow card (use with care)
- When fixed: take the tags off, return the plastic card, close the issue
- Issue first, tag second. A card without a number is hard to follow up.
- One issue per failure when you can. Reuse the same number if you are updating the same fault.
- No GitHub account? Ask someone in the space to open the issue with you, or leave a clear note and ask them to file it, then tag once you have the number.
-
Health & safety / PAT fails still get a red card and a
Broken(and usuallyHealth & Safety) label. - Plastic cards are 3D-printed; if you run out, reprint from the plate / tag project files rather than leaving machines unmarked.
*Further post with access to the STL files coming soon.
Quick Links: Website • Groups • Rooms • Equipment • Issue Tracker • Discussion Group • Image Credits
☝️ Filter all pages above!
(Full search available on the top of page)
WiFi: DoESLiverpool, password: decafbad00
- Wiki Home
- Making
- Get involved
- In The Space
- Bank and PayPal Details
or