Skip to content

Latest commit

 

History

History
40 lines (26 loc) · 1.71 KB

CONTRIBUTING.md

File metadata and controls

40 lines (26 loc) · 1.71 KB
Raw

Contribution Guidelines

Content

Style & Format

All Markdown tables in Vocabulary/ should be follow this format:

| Spelling | English Usage/Implication | Definition |
| -------- | ------------------------- | ---------- |
| foo | bar | baz |

Column titles are not standardized, but the first column should have the Kumilinwa word, and the second should contain the definition. Optional additional columns can be added to demonstrate an English equivalent or to provide additional context.

Maintaning

Issues

  • Check for duplicates before creating new issues. If you find a duplicate, close the newer one and reference back to the original.
  • Keep titles concise and descriptive. Add sufficient detail in the body and detail all major changes.

Labels

  • Issues with the critical label are high priority and should be addressed as soon as possible.
  • Add all relevant labels please! Only maintainers may add labels such as nyo, question, duplicate, or incomplete.
  • An issue should be closed and marked as not planned if it has the nyo label.

Pull Requests

  • Keep PRs concise and focused. If you have multiple unrelated changes, create multiple PRs.
  • PRs should be reviewed by at least one maintainer before merging.
  • When possible, reference any issues addressed in a comment (i.e. fixes #1) so that they will be automatically closed upon merging.

Labels

  • Maintainers: PRs with the critical label should be reviewed and merged as soon as possible. These take priority over everything else.
  • Don't merge if it has the DONOTMERGE label. A PR should be closed if it has the nyo label.
  • Follow same label rules as issues.