JOREK Community Governance Rules

1. Mission

JOREK remains a central community code for 3D non-linear MHD and hybrid fluid-kinetic fusion plasma simulations. Goals: Keep the code unified, share knowledge, ensure fair collaboration and citation.

2. License & Contributions

• License: LGPLv3.0-or-later.
• Contributions: Every pull request requires Developer Certificate of Origin (DCO 1.1): Signed-off-by: Name <email>. Confirms rights and LGPL compatibility.[web:19]
• Maintainers review (or coordinate review) and merge pull requests.

3. Publication Rules (Mandatory)

Please make sure you follow the publication rules for all conference contributions and publications.

4. Code Cohesion

• Forks: Share modifications upstream with the main repository via pull requests.
• No Renaming: JOREK is a trademark. Forks must be named "JOREK-fork-vX". Pure renames are not recognized.
• Version Control: Releases via GitHub tags. Merge upstream regularly.

5. Decision-Making

• Decisions are usually taken by the core developers team upon consultation of the community.
• The core developers team decides by vote about changes of core developers team members and the list of gate keepers / maintainers.
• A list of the main contributing institutions is maintained (updated by the core dev team upon request).
• In case of conflicts in the core developers team regarding a decision, each of these institutions will nominate a representative; the committee formed by these representatives will take a decisions on the conflict matter.

6. Code of Conduct

• Be respectful and collaborative. Report violations to maintainers.

This agreement binds the community. Questions? Open an Issue.