We welcome questions, reproducibility reports, and contributions from researchers, students, and software users. This guidance applies when a repository does not provide its own contribution instructions. Follow project-specific instructions where available.
Use the relevant repository's Issues for software questions, unexpected results, or installation problems. Briefly describe what you attempted, the software version or commit, the command and relevant environment, and the expected and observed behavior. A small reproducible example is useful when available; an initial question does not require a complete diagnostic report.
When reporting a discrepancy with a publication, identify the relevant figure, table, or analysis and the code and data versions used. Share public or synthetic examples rather than patient-level data, credentials, or restricted research material. Remove sensitive information from logs before posting.
Small corrections can be submitted directly as a pull request. For substantial methodological changes or new features, a brief discussion with the project maintainers can help establish the intended scope. Explain what changes and why, and include a relevant example or check when it helps assess the result. Keep documentation in professional academic English and follow the repository's existing conventions.
Lab collaborators with Write access may commit routine changes directly. Pull requests are useful for discussion and review, but there is no organization-wide requirement for every change to pass a formal approval process.
Follow the license of the repository receiving the contribution. New lab open-source projects use Apache License 2.0 by default; existing projects and third-party components retain their applicable terms. Preserve attribution and relevant license notices. Cite the associated publication and software version when reusing a research method, following the project's citation instructions.
For research collaborations, student inquiries, or lab visits, use the lab contact page. For software support, use the relevant repository so that answers remain available to other users. Communicate respectfully and distinguish implementation issues from methodological questions.