# KORA Open Roles

Date: `2026-05-06`

## Purpose

KORA is opening early unpaid OSS contributor roles so builders, researchers, writers, and community operators can help shape the project through GitHub.

## Required Disclaimer

These are unpaid early open-source contributor roles, not employment positions. Future paid roles, grants, internships, or contributor programs may be considered if funding becomes available, but they are not guaranteed.

## Open Roles

### Early Builder

- Who it is for: developers who want to try KORA and report usability friction.
- What they do: run examples, open feedback issues, suggest improvements.
- Required skills: basic Python and GitHub familiarity.
- Expected weekly time: 1-3 hours.
- First recommended task: run the quickstart and report one improvement.
- GitHub entry point: Discussions or a feedback issue.
- Review requirement: Albert review for benchmark or claim wording.

### Benchmark Runner

- Who it is for: people comfortable running scripts and reporting results.
- What they do: run benchmark commands, document reproducibility notes, report failures.
- Required skills: command line, Python, careful reporting.
- Expected weekly time: 2-4 hours.
- First recommended task: reproduce the current deterministic-heavy benchmark flow.
- GitHub entry point: Benchmark Results discussion or benchmark issue.
- Review requirement: Albert review before public numeric claims.

### Documentation Contributor

- Who it is for: writers and developers who can make docs clearer.
- What they do: improve README, guides, FAQs, and onboarding docs.
- Required skills: Markdown and careful reading.
- Expected weekly time: 1-3 hours.
- First recommended task: fix one confusing section or add one small clarification.
- GitHub entry point: docs issue or docs PR.
- Review requirement: claim-sensitive docs require Albert review.

### Example Builder

- Who it is for: developers who learn by building small examples.
- What they do: create focused examples for KORA execution patterns.
- Required skills: Python and basic testing.
- Expected weekly time: 2-5 hours.
- First recommended task: propose one small example in an issue.
- GitHub entry point: example issue and PR.
- Review requirement: technical review; claim-sensitive copy requires Albert review.

### AI-Assisted Contributor

- Who it is for: contributors using LLMs or vibe-coding tools responsibly.
- What they do: make small docs, examples, tests, or usability improvements.
- Required skills: ability to review generated output and run checks.
- Expected weekly time: 1-4 hours.
- First recommended task: pick a small docs or test issue.
- GitHub entry point: labeled issue and PR.
- Review requirement: disclose AI assistance and respond to review.

### Community Moderator

- Who it is for: people who can keep discussions welcoming and organized.
- What they do: route questions, point to docs, collect recurring feedback.
- Required skills: communication, GitHub Discussions familiarity.
- Expected weekly time: 1-3 hours.
- First recommended task: summarize one discussion thread.
- GitHub entry point: Discussions and community issues.
- Review requirement: Albert review for claim-sensitive responses.

### Developer Advocate

- Who it is for: builders who can explain KORA to other builders.
- What they do: draft tutorials, walkthroughs, demo notes, and feedback summaries.
- Required skills: technical communication and basic KORA usage.
- Expected weekly time: 2-5 hours.
- First recommended task: draft one short tutorial outline.
- GitHub entry point: content review issue.
- Review requirement: Albert review before publishing externally.

### Research Contributor

- Who it is for: researchers interested in execution control and benchmarks.
- What they do: review methodology, propose experiments, contribute reproducibility notes.
- Required skills: research rigor and clear writing.
- Expected weekly time: 2-6 hours.
- First recommended task: review the category thesis or benchmark policy.
- GitHub entry point: research/paper discussion or issue.
- Review requirement: paper and benchmark claims require Albert review.

### Partner Scout

- Who it is for: ecosystem connectors who can identify potential use cases.
- What they do: collect leads and use-case signals without overstating status.
- Required skills: outreach discipline and careful note-taking.
- Expected weekly time: 1-3 hours.
- First recommended task: create one partner-lead issue from a real signal.
- GitHub entry point: partner-lead issue template.
- Review requirement: Albert review for partner-facing language.

### Translation Contributor

- Who it is for: contributors who can localize docs accurately.
- What they do: translate approved docs and identify unclear source wording.
- Required skills: language fluency and Markdown.
- Expected weekly time: 1-4 hours.
- First recommended task: propose one translation target.
- GitHub entry point: translation issue or PR.
- Review requirement: technical and claim-sensitive wording review.

## How To Express Interest

- Use GitHub Discussions for public interest.
- Email or a private form may be used for resume/profile sharing if available later.
- Do not post personal resumes or private data in public GitHub issues.
- Interested people should share GitHub/LinkedIn, role of interest, and one small contribution they can make in the next 2 weeks.

## Contributor Recognition

- PR authorship.
- Release notes where appropriate.
- Acknowledgements where appropriate.
- Paper authorship only under the paper contribution policy.
