Contributing guidelines
=======================

We want to make contributing to this project as easy and transparent as
possible.

Our Development Process
-----------------------
New versions are being developed in the "main" branch,
or in their own feature branch.
When they are deemed ready for a release, they are merged back into "main"
again.

So all contributions must stage first through "main"
or their own feature branch.

Pull Requests
-------------
We actively welcome your pull requests.

1. Fork the repo and create your branch from `main`.
2. If you've added code that should be tested, add tests.
3. If you've changed APIs, update the documentation.
4. Ensure the test suite passes.
5. Make sure your code does not issue new compiler warnings.

Automated Contributions Policy
------------------------------

Contributing to Blosc requires human judgment, contextual understanding, and familiarity with scikit-learn’s structure and goals. It is not suitable for automatic processing by AI tools.

Please refrain from submitting issues or pull requests generated by fully-automated tools. Maintainers reserve the right, at their sole discretion, to close such submissions and to block any account responsible for them.

Review all code or documentation changes made by AI tools and make sure you understand all changes and can explain them on request, before submitting them under your name. Do not submit any AI-generated code that you haven’t personally reviewed, understood and tested, as this wastes maintainers’ time.

Please do not paste AI generated text in the description of issues, PRs or in comments as this makes it harder for reviewers to assess your contribution. We are happy for it to be used to improve grammar or if you are not a native English speaker.

If you used AI tools, please state so in your PR description.

PRs that appear to violate this policy will be closed without review.

For more information on why this is becoming a big issue for open source projects, please see the `Software Review in the Era of AI <https://ropensci.org/blog/2026/02/26/ropensci-ai-policy/>`_ by the rOpenSci folks.

Issues
------
We use GitHub issues to track public bugs. Please ensure your description is
clear and has sufficient instructions to be able to reproduce the issue.

Coding Style 
------------
* 2 spaces for indentation rather than tabs.

License
-------
By contributing to C-Blosc2, you agree that your contributions will be licensed
under the `LICENSE <https://github.com/Blosc/c-blosc2/blob/main/LICENSE.txt>`_ 
file of the project.
