✎ Edit this page

Contributing

This knowledge base is the shared place to learn about Buddhist tasks: what each task is, how it is measured, the workflows it comes from, and what our experiments found. Everyone who does Buddhist work is welcome here: translators, teachers, editors, artists, librarians, center staff, developers. You do not need to write code or use git. Please follow the code of conduct.

Ways to take part

You can give How Credit
A skill, or any file you give to AI (Claude file, project instructions, style guide, glossary, prompt) Share your files (goes to the prompt library), or for a model paste a link on the homepage authors on the entry; leaderboard row
Test material (exam papers, checked translations, corrected OCR) Propose a benchmark Dataset card; benchmark page
An expert review of a benchmark Review a benchmark: check items and answers in a field you know Named as reviewer in the dataset card
Reading in your language Volunteer as a language reader Named as reader
Compute or API credits Donate compute or API credits: pays for evaluations of everyone’s submissions “Supported by” on the homepage and org profile, if you wish
How your project works Share a workflow Owner of the workflow page
A project or dataset we do not list Add to the Directory —
A fix or a new page “Edit this page” on any page contributors on the page
Feedback on our sites, or a review of a design UX reviews: tell us what was hard, review a design as a persona, write a design, or suggest a persona Named in the design or the persona

New to this? The tutorials teach the steps by doing them. Organizations that contribute often can get their own GitHub team: see Governance.

Improve a task page

Task pages belong to everyone. Click “Edit this page” on the site (or the pencil icon on GitHub) and propose a change. The most useful additions are:

Add your name to contributors in the page’s frontmatter. A maintainer reviews the change; a disagreement about a definition goes to the page’s discussion (an issue or a Discussions thread linked from the page) and both views can be recorded on the page until it is settled.

Who owns a workflow page

Every workflow has an owner: the person or organization whose practice it describes. Choose one of two modes.

Mode Where the document lives What lives here Who can change it
linked Your own place (Google Doc, website, PDF) A short page in our own words: summary, credit, a link to your version, and a map from your steps to tasks You change your document whenever you like. Our page follows it; we update the version and the step map.
hosted This repo The full workflow You review every change to your page (listed in .github/CODEOWNERS). Others suggest edits by pull request.

Rules for both modes:

Share a workflow

  1. Easiest: open a “Share a workflow” issue and paste a link. A maintainer writes the linked page, maps your steps to tasks and asks you to check it.
  2. By pull request: copy templates/workflow.md to workflows/<id>.md, fill it in, run python3 scripts/build.py and python3 scripts/check.py, and open a pull request.

Good workflow pages:

Propose a task

A task is one step that a model or skill can be measured on, such as segmentation or translation review. Open a “Suggest a task” issue, or copy templates/task.md. Task IDs are shared with buddhist-benchmarks tasks/index.json and skill names in buddhist-skills (<task>-<language>), so a new task gets added there too.

Help a task get a benchmark

Most tasks have no benchmark yet. A benchmark starts small: twenty to fifty real items from work you already do, with the answer a careful human would give. See buddhist-benchmarks SUBMIT.md and the task page’s “Help wanted” section.

Propose or run an experiment

Start with an Idea issue. How an experiment is planned, logged and reported is described in experiments/README.md.

For maintainers

✎ Edit this page · History · Discuss