Bug reports
Open a GitHub issue with input data shape, expected behavior, actual behavior, version, platform, and a minimal reproduction.
Support
Join the Discord
Ask setup questions, coordinate contributor work, and get quick help before opening a large PR.
Where to go
Feature requests
Describe the workflow, user impact, proposed API, and whether it belongs in C++, Python, docs, or integrations.
Questions
Use Discord for quick questions. Use GitHub Discussions or issues when the answer should become searchable project knowledge.
Security
Do not post secrets or private data in public issues. Report security-sensitive findings privately to the maintainer first.
GSSoC and contributor flow
Merged PRs are labeled with type, area, size, level, quality, and GSSoC labels so contributors receive clear credit and maintainers can audit the release history.
| Label family | Meaning |
|---|---|
type:* | Bug, feature, docs, testing, performance, refactor, devops, security, or design. |
area:* | CSV parser, C++ core, Python API, quality, schema, pandas interop, docs, benchmarks, website, CI/packaging. |
size:* | Rough implementation size from tiny to large. |
level:* | Contributor scoring level for merged GSSoC work. |
quality:clean | Applied to merged work that is scoped, tested, and easy to maintain. |
Contributor expectations
- Claim or discuss an issue before doing broad work.
- Keep PR titles in Conventional Commit format so release notes are generated correctly.
- Add focused tests for behavior changes, edge cases, and regressions.
- Update docs or the website when public behavior changes.
- Keep unrelated formatting or refactors out of feature and bug-fix PRs.
Contributors
Recent contributors are loaded from GitHub when the browser allows API requests.
Loading contributors...