Lilypond Communication

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

lilypond Updated

File contents

Forums

Limit communication about LilyPond development to these official forums:

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.

lilypond/lilypond/tree/main/.agents/skills/lilypond-communication commit c505c4f843

Frequently asked questions

npx skillmds@latest add lilypond/lilypond-communication