Fire sprinkler add-on: heads, branch lines, hazard classes
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
Research direction
Read the roadmap entry and the add-on contract first; the issue does not name source files or tests. Map the requested sprinkler heads, network lines, hazard classes, and coordination checks to the contract, then identify any kernel gaps before implementation. Done means each rule cites its code section, has a worked test example, and its calculations have been reviewed by a licensed fire protection engineer.
Written by the indexing model from the issue text.
Description
From the roadmap ("Larger work for discipline experts").
A fire sprinkler add-on built only through the add-on contract, with no kernel edits:
- sprinkler heads (types, K-factors, temperature ratings, coverage);
- branch lines and mains on the shared network concept;
- hazard classifications per space;
- spacing and coverage checks as coordination rules.
Every rule names the code section it comes from and has a worked example in its tests. Calculations need review by a licensed fire protection engineer before merge. If the kernel can't express something, label it kernel gap here first.
- Dominant language
- TypeScript
- Stars
- 85
- Forks
- 10
- Avg merge
- 1h 28m
- Merged PRs (30d)
- 20
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from permitzip/mutinybim
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
area: docs documentation
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
area: web-app bug
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
permitzip/mutinybim#27 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
permitzip/mutinybim#66 · 2 comments ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 48/100
permitzip/mutinybim#65 · 2 comments ·
Maintainers usually reply within 1 day
All issues in permitzip/mutinybim
Similar issues
-
🐛 The Rulekeeper - An index run that gives up on the lock ends SucceededPossibly taken @github-actions claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
SSWConsulting/SSW.Rules#2809 · 1 comment ·
Maintainers usually reply within 1 day
-
automated-triage type/bug type/ci
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
📦 expo-router Android contributor: external needs review sdk-58 severity: medium
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Translate the READMEOpendocumentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
asasemahmed/openboard#68 ·
Maintainers usually reply within 1 day
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 72/100