sjat/MakerFLOSS
1
1
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs: clarify language and fix grammar in house rules

Browse source 
- Fix brake → break
- Fix gatekeep → gatekeeping, everybody → everyone
- Cleaner prose throughout, consistent punctuation in lists
- non-FLOSS → proprietary software (more universally understood)
- Shorten "Licenses for what we build" → "Licenses"

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
sjat 2026-05-10 19:14:23 +02:00
parent 0403c9098e
commit 48a72de10e
1 changed files with 13 additions and 13 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

26
docs/makerFLOSS_house_rules.md
View file

@ -5,22 +5,22 @@ pagination: true
# makerFLOSS – Working Norms (v0.1) # makerFLOSS – Working Norms (v0.1)
We aim to experiment, learn together and have fun. MakerFLOSS is not the same as the Orange Makers IT setup - but we try to help out where we can. We aim to experiment, learn together, and have fun. MakerFLOSS is not the same as the Orange Makerspace IT setup — but we help out where we can.
We try to not have too many rules or guidelines, but here are the main ones: We keep rules to a minimum. Here are the main ones:
- Political - Political
- We make mistakes - but try to mostly make them in our labs and not on our production setup. - We make mistakes — but try to make them in our labs, not in production.
- If you brake something - try to fix it. If you can't, tell and ask for help. - If you break something, try to fix it. If you can't, say so and ask for help.
- We only use non-FLOSS if we really have to. - We only use proprietary software when there is no FLOSS alternative.
- We foster collaboration by being open and not gatekeep (everybody can get root access). - We foster collaboration by being open and not gatekeeping (everyone can get root access).
- Try not to do anything that will make us have to create a boring rule. - Try not to do anything that forces us to write a new rule.
- Technical - Technical
- Language: English for code, docs, commits (meeting notes may be in Danish) - Language: English for code, docs, and commits (meeting notes may be in Danish)
- Git: Trunk-based development, feature branches, simple commit messages - Git: Trunk-based development, feature branches, simple commit messages
- Environments: containerized, reproducible setups. - Environments: Containerised and reproducible
- Hardware: all setups documented + labeled physically. - Hardware: All setups documented and labeled physically
- AI: Allowed but reviewed; no secrets in commits - AI: Allowed but reviewed — no secrets in commits
- Decisions: lightweight markdown decision logs. - Decisions: Lightweight markdown decision logs
- Licenses for what we build: FLOSS by default. - Licenses: FLOSS by default