Contributing

Principles

  • Cite authoritative Debian sources (policy, developer refs, team announcements, BTS).

  • Capture rationale (WHY) with procedures (HOW).

  • Prefer incremental MRs over large dumps.

  • Mark uncertain statements with .. TODO:: or .. note:: OPEN QUESTION.

Workflow (Draft)

  1. Open or pick an issue describing the content gap.

  2. Write/update a focused page or subsection.

  3. Add cross-references / glossary entries as needed.

  4. Request review from a relevant team member.

  5. Merge after at least one acknowledgment (policy TBD).

Style

  • Present tense for current policy; label historical deviations.

  • Use short paragraphs and bullet lists for steps.

  • Define acronyms on first use.