MakerFLOSS/docs/makerFLOSS_house_rules.md
sjat 48a72de10e docs: clarify language and fix grammar in house rules
- 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>
2026-05-10 19:14:23 +02:00

1.1 KiB
Raw Blame History

marp pagination
true true

makerFLOSS Working Norms (v0.1)

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 keep rules to a minimum. Here are the main ones:

  • Political

    • We make mistakes — but try to make them in our labs, not in production.
    • If you break something, try to fix it. If you can't, say so and ask for help.
    • We only use proprietary software when there is no FLOSS alternative.
    • We foster collaboration by being open and not gatekeeping (everyone can get root access).
    • Try not to do anything that forces us to write a new rule.
  • Technical

    • Language: English for code, docs, and commits (meeting notes may be in Danish)
    • Git: Trunk-based development, feature branches, simple commit messages
    • Environments: Containerised and reproducible
    • Hardware: All setups documented and labeled physically
    • AI: Allowed but reviewed — no secrets in commits
    • Decisions: Lightweight markdown decision logs
    • Licenses: FLOSS by default