Contribution

This section summarizes how to contribute and where to find details. We adopt the CLIMADA contribution workflow and conventions.

1) Contribute

We follow the CLIMADA workflow for branching, tests, and reviews. Please read the CLIMADA guide:

• CLIMADA development guide

Typical steps: fork -> branch -> tests -> pull request.

For extended resources for CLIMADA development, visit:

• Guide to CLIMADA development

2) Report issues or problems

Open an issue and include:

• Clear description and minimal example

• Expected vs actual behavior

• Version info (package, Python, OS)

• Relevant logs or traceback

3) Seek support

Talk to the CLIMADA group

• Before starting to code, coordinate with one of the repository admins.

• Align on the big picture: intersections with other projects, potential conflicts, changes to CLIMADA core, and additional dependencies.

• Also talk with members of the core development team (see the GitHub wiki).

• Bring your idea to a developers meeting to get advice, find collaborators, and identify reviewers.

• Keep communicating as your plans evolve.

4) How to stay informed or participate

• GitHub repository

• Developer and user mailing list

• Monthly developers and users meetings (please register for the mailing list to receive invitations)

• Contribution guide