Problem
Current contributor onboarding can be clearer regarding supported Python versions, R scope, and what CI actually validates.
Proposal
Add or update contributor documentation with a compact support matrix covering:
- Supported Python versions
- R component scope / supported environments
- What combinations are validated in CI
- Recommended local test commands by area (Python, R, docs, etc.)
Also clarify which checks are required before submitting changes versus optional deeper validation.
Acceptance criteria
- One canonical documentation section for the support matrix
- Clear distinction between required vs optional local checks
- Linked from
CONTRIBUTING.md
Contribution
I’d be happy to work on this issue and contribute a PR if this approach sounds good.
Problem
Current contributor onboarding can be clearer regarding supported Python versions, R scope, and what CI actually validates.
Proposal
Add or update contributor documentation with a compact support matrix covering:
Also clarify which checks are required before submitting changes versus optional deeper validation.
Acceptance criteria
CONTRIBUTING.mdContribution
I’d be happy to work on this issue and contribute a PR if this approach sounds good.