MakerFLOSS/docs/house-rules.md
sjat 16f56fd961
All checks were successful
Build docs site / build (push) Successful in 30s
Build slides / build (push) Successful in 48s
docs: standardise filenames to ASCII kebab-case + ISO date prefix
Adopt one filename convention everywhere except hardware host pages
(those are pinned to their hostnames by the index validator):

  - ASCII lowercase
  - kebab-case word separator
  - dated docs: YYYY-MM-DD-label.md (hyphen between date and label)
  - English regardless of content language

Renames:
  docs/makerFLOSS_house_rules.md                        -> docs/house-rules.md
  docs/infrastruktur/                                   -> docs/infrastructure/
  docs/infrastructure/vps-og-dns.md                     -> docs/infrastructure/vps-and-dns.md
  docs/presentations/2026-05-11_messaging.md            -> docs/presentations/2026-05-11-messaging.md
  docs/presentations/2026-05-11_SoMe-taxonomi.md        -> docs/presentations/2026-05-11-social-media-taxonomy.md
  notes/todo/2026-04-14_todo.md                         -> notes/todo/2026-04-14-todo.md
  notes/todo/OM_services.md                             -> notes/todo/om-services.md
  notes/todo/indkøbsliste.md                            -> notes/todo/wishlist.md
  notes/communications/2026-03-16_facebookpost.md       -> notes/communications/2026-03-16-facebook-post.md

Other touches:
- Document the convention in CLAUDE.md under Working Norms.
- Refresh the stale Repository Structure block in CLAUDE.md to reflect
  the docs/ vs notes/ split introduced in f6d589e.
- Update the House rules link in docs/index.md and the nav entry in
  mkdocs.yml to the new house-rules.md path.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-18 17:07:26 +02:00

1 KiB
Raw Permalink 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:

  • Social
    • 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 viable 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; UI in Danish+English.
    • Git: Trunk-based development, feature branches, simple commit messages.
    • Environments: Containerised and reproducible.
    • Hardware: All setups documented and labeled physically.
    • Decisions: Sociocratically decided - lightweight markdown decision logs.
    • Licenses: FLOSS (MIT) by default.