Thank you for contributing to the Urban Data Science Toolkit.
- Review the target repository's open issues, pull requests, documentation, and supported-version policy.
- For substantial changes, open or join an issue so scope and implementation can be discussed before significant work begins.
- Keep pull requests focused and include tests for changed behavior.
- Follow any repository-specific contribution guidance in addition to this organization-wide policy.
All contributions, including work recovered from a fork, receive the same technical review. Maintainers consider correctness, compatibility, tests, documentation, packaging, security, and long-term maintenance cost.
Submission does not guarantee acceptance. Maintainers may request that a large change be divided into smaller pull requests or adapted to current project architecture and compatibility requirements.
UDST welcomes proposals to upstream valuable improvements developed in public forks. A pull request incorporating fork-derived work should identify:
- the source repository, branch, pull request, and relevant commits;
- the original authors and contributors;
- material adaptations made for the upstream project; and
- tests added or changed.
UDST will preserve original commit authorship where practical and provide explicit credit when work must be adapted or rewritten. Attribution does not replace license and provenance review. Contributors should submit only work they have the right to contribute.
Material contributions should be credited in commit history where it can be retained cleanly and in release notes when the work ships. A Co-authored-by trailer should be used only when the resulting commit genuinely incorporates that person's contribution.
Policies concerning contributor certification or contributor license agreements will be documented separately if adopted.