Open to anyone in the group, whatever your career stage or organization.
This rule has no exceptions. Don't commit, upload, or paste:
- patient-level or clinical trial data
- proprietary models, internal datasets, or unpublished compound information
- anything your employer or a regulator would treat as confidential
Use public or synthetic data only. nlmixr2lib is a good source. If you're not sure something is safe to share, don't. Ask in Discussions first. One bad upload can become a real problem for someone's employer.
- For anything non-trivial, start a Discussion thread before you write code.
- Fork the repo and work on a branch.
- Open a PR against
mainand explain what changed and why. - A maintainer reviews and merges. Expect some feedback first.
Write tasks and workflows other people can run. Document them well enough that someone new to the topic can follow along. Include public or synthetic examples so others can reproduce your results.
Fine, and often the point. Say what it does, why it belongs in the thread you're posting in, and that it's yours.
What gets hidden: a comment whose substance is the pitch, an account whose only activity here is a product link, or a commercial product introduced as a community contribution. If you want your tool taken seriously, run it through First Run and post what happened. That lands better than a link.
Ask in Discussions or raise them at a monthly meeting.
Be professional and respectful. We follow ISoP's community norms.