OpenSurgicalVisionOPEN SCIENCE. SHARED PROGRESS.
Sign in to CVAT
EN

CONTRIBUTE

Contribute to the project

Seven contribution tracks and a first contribution in about 30 minutes.

Engineering & research

Build pipelines. Test ideas. Make every result reproducible.

Python · ML · MLOps

Clinical contribution

Bring clinical expertise to annotation and research review.

Annotation · Clinical review

Testing & quality

Find edge cases and make our quality checks stronger.

QA · Data quality

Documentation & translation

Turn technical work into clear, accessible knowledge.

Writing · EN / RU

Community & communications

Tell the story of open research. Help people find their place.

Community · Design

Coordination & partnerships

Connect volunteers, research groups and universities.

PM · Partnerships

Education

Make experiments teachable, including the ones that did not work.

Notebooks · Teaching
Studying medicine? See hundreds of real operations, train your anatomy with feedback and do research on real data.For medical studentsStudying computer science? Real data, real computer vision problems, code review and an open portfolio.For CS studentsTeaching medicine? A ready base for a student research group, term papers and theses.For educatorsLooking for a topic? 56 research topics for medical and technical programmes.Research topics

Start with a small task

You do not need to train models to help. There are seven tracks: clinical review, engineering, testing, documentation, communications, partnerships and education. Pick a small task where it is clear who will check the result and how.

Students and educators

Medical students annotate recordings of real operations, computer science students write code and train models, and together they produce term papers, theses and talks on open data. Read more on the pages for medical students, for computer science students, for educators and departments and in the list of research topics.

A first contribution in about 30 minutes

  1. 0–5 minutes. Read the contributor guide and pick a good first issue. None fits? Propose your own.
  2. 5–10 minutes. Agree the scope in the issue, fork the repository and create a branch.
  3. 10–20 minutes. Make one change and run the checks. If a check could not be run, say so.
  4. 20–25 minutes. Review your diff and commit with a DCO sign-off: git commit -s -m "Clarify a setup step". The sign-off confirms you have the right to contribute this work.
  5. 25–30 minutes. Open a pull request linked to the issue: what you changed, what you checked, what questions remain.

Never add patient data or your employer’s material.

How we work

  • Decisions are made asynchronously: if it is not in an issue, it does not exist.
  • Feedback is respectful and specific.
  • A task with no update for two weeks may go back to the shared queue.
  • We aim to respond to a newcomer’s first pull request within 48 hours.

Read the code of conduct and governance. Report vulnerabilities through the security policy and ask general questions in Discussions.