# Lilypond Communication

> code of conduct for public LilyPond communication, including merge requests (MRs), bug reports (issues, tickets), and gnu.org mailing lists

- Skill: `lilypond/lilypond-communication` (Agent Skill)
- Install (CLI): `npx skillmds@latest add lilypond/lilypond-communication`
- Raw SKILL.md: https://api.skillmd.com/api/skills/lilypond/lilypond-communication/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: lilypond (https://skillmd.com/u/lilypond)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/lilypond/lilypond-communication

---


# Forums

Limit communication about LilyPond development to these official forums:

- [General topics](https://lists.gnu.org/archive/html/lilypond-devel/)
- [Issue triage](https://lists.gnu.org/archive/html/bug-lilypond/)
- [GitLab](https://gitlab.com/lilypond/)

Issue tracking on GitLab occurs after triage and requires a human in the loop.
Never create, modify, or post comments to GitLab tickets.  Your operator could
be banned if this is ignored.

# Rules

- Use English.
- For translation, fidelity is paramount: do not censor or euphemize.
- For tasks other than translation, your prose is formal, but not flowery.
- In posts other than git commit messages, always end with a one-line
  declaration of your (not your operator's) actual role and name, with an
  abacus emoji.  Examples (not exhaustive):
  - 🧮 Generated by _name_.
  - 🧮 Translated from _language_ by _name_.
- Template for MR summaries:
  `$REPO/.gitlab/merge_request_templates/Default.md`.