Merge branch 'develop' into gh_action

Author: tjhunter

CODE-of-CONDUCT.md

@@ -0,0 +1,62 @@
+# Code of Conduct 
+ 
+## Introduction 
+Welcome to the WeatherGenerator development community.  
+ 
+We are committed to providing a welcoming and inspiring environment for all contributors. Our goal is to develop high-quality software and ensure it is robust, reliable, and available as open-source for the benefit of the wider community and open for external contributors. 
+ 
+This Code of Conduct outlines our expectations for participants to foster a positive, productive, and inclusive community. 
+ 
+## Reference 
+This Code of Conduct is adapted and meant to be a summarised form of the [Contributor Covenant](https://www.contributor-covenant.org/), version 2.1, available at https://www.contributor-covenant.org/version/2/1/code_of_conduct. 
+ 
+If the interpretation of this code of conduct is in any way in conflict with the Contributor Covenant, the Contributor Covenant takes precedence. 
+ 
+## Our Standards 
+All contributors are expected to adhere to the following standards: 
+ 
+1. **Respectful Communication**: 
+   - Demonstrate empathy and kindness towards others. 
+   - Use inclusive and respectful language. 
+   - Critique ideas, not people. 
+   - Avoid offensive or derogatory comments. 
+ 
+2. **Collaboration**: 
+   - Be open to constructive feedback. 
+   - Share knowledge and help others. 
+   - Respect differing viewpoints and experiences. 
+ 
+3. **Commitment to Quality**: 
+   - Write clear, concise, and well-documented code. 
+   - Follow established coding standards and guidelines. 
+   - Test and review code thoroughly before submission. 
+   - Provide new tests for new features. 
+   - Submit helpful and constructive feedback on code reviews. 
+ 
+4. **Inclusivity**: 
+   - Be welcoming to new contributors. 
+   - Ensure that all community members can participate fully. 
+   - Encourage diversity in all its forms. 
+ 
+5. **Professionalism**: 
+   - Act professionally in all interactions. 
+   - Refrain from disruptive behavior or harassment. 
+   - Uphold the integrity and reputation of the ECMWF community. 
+ 
+## Our Responsibilities 
+Repository managers are responsible for clarifying and enforcing standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior. 
+ 
+## Scope 
+This Code of Conduct applies to all project spaces, including GitHub repositories, issue trackers, forums, chat channels, and any other means of communication. It also applies when an individual is representing the project or its community in public spaces. 
+ 
+## Reporting Issues 
+If you experience or witness unacceptable behavior, or have any other concerns, please report it by contacting `development (at) weathergenerator.eu`.  
+ 
+All complaints will be reviewed and investigated promptly and fairly. 
+ 
+## Enforcement 
+Enforcement shall take the form of warnings, temporary or permanent bans, as defined in the [Contributor Covenant](https://www.contributor-covenant.org/) 
+ 
+## Contacts 
+ 
+For any questions or further information, please contact `development (at) weathergenerator.eu`

CONTRIBUTING.md

@@ -0,0 +1,75 @@
+# WeatherGenerator Contributing Guide 
+ 
+Thank you for your interest in contributing to the WeatherGenerator! We welcome contributions to help build and develop the WeatherGenerator. This guide will help you get started with contributing to our project. 
+ 
+## Table of Contents 
+ 
+1. [Code of Conduct](#code-of-conduct) 
+2. [Getting Started](#getting-started) 
+3. [How to Contribute](#how-to-contribute) 
+   - [Reporting Issues](#reporting-issues) 
+   - [Submitting Pull Requests](#submitting-pull-requests) 
+4. [Development Guidelines](#development-guidelines) 
+   - [Coding Standards](#coding-standards) 
+   - [Commit Messages](#commit-messages) 
+   - [Testing](#testing) 
+5. [Getting Help](#getting-help) 
+ 
+## Code of Conduct 
+ 
+We are committed to fostering a welcoming and inclusive community. By participating in this project, you agree to abide by our [Code of Conduct](CODE-of-CONDUCT.md). 
+ 
+## Getting Started 
+ 
+1. **Fork the repository**: Create a fork of the repository by clicking the "Fork" button at the top right of the repository page. 
+2. **Clone your fork**: Clone your fork to your local machine, see (https://docs.github.com/en/repositories/creating-and-managing-repositories/cloning-a-repository). In the terminal, one can use the following command: 
+   ```sh 
+   git clone https://github.com/your-username/WeatherGenerator.git 
+   ``` 
+3. **Set up the upstream remote**: Set up the upstream remote to keep your fork up-to-date with the main repository, see again (https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-repository-for-a-fork). In the terminal: 
+   ```sh 
+   git remote add upstream https://github.com/ecmwf/WeatherGenerator.git 
+   ``` 
+ 
+## How to Contribute 
+ 
+### Reporting Issues 
+ 
+If you find a bug or have a feature request, please create an issue on the repository's [issue tracker](https://github.com/ecmwf/WeatherGenerator/issues).  
+When reporting an issue, please use the appropriate issue template and provide as much detail as possible, including steps to reproduce the issue and any relevant logs or screenshots. Please take care not to share personal information in the issue tracker (e.g. usernames, passwords, hostnames, etc). Please use the appropriate tags to categorize your issue. 
+ 
+### Submitting Contributions 
+ 
+lease open first an issue on the repository's [issue tracker](https://github.com/ecmwf/WeatherGenerator/issues) that describes the contribution that you are planning. This can be bug fixes or new features. Having a discussion through the issue early on will ensure that your work aligns with the development roadmap for the WeatherGenerator project and that your PR will eventually be accepted. 
+ 
+#### Implementing and Submitting your Contribution 
+ 
+The WeatherGenerator project follows the standard process of pull requests on Github. If you are unfamiliar, consider following the [Github documentaion on pull requests](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests). 
+Pull requests are expected to have a clear description of the issue. Any significant pull request is expected to have a Github issue associated. 
+ 
+1. **Create a branch**: Create a new branch for your work 
+2. **Make your changes**: Make your changes in your feature branch. 
+3. **Commit your changes**: Please use clear and descriptive commit messages. 
+4. **Push to your fork**: Push your changes to your fork on GitHub 
+5. **Open a pull request**: Open a pull request against the `develop` branch of the WeatherGenerator repository. Provide a clear description of your changes and link any relevant issues. 
+ 
+## Development Guidelines 
+ 
+### Coding Standards 
+ 
+Please follow our coding standards to ensure consistency across the codebase. Refer to our [Coding Standards](CODING_STANDARDS.md) document for details on the conventions and best practices we adhere to. 
+ 
+### Commit Messages 
+ 
+Write clear and concise commit messages that describe the changes made. Where possible and relevant, reference any related issues in the commit message. 
+ 
+### Testing 
+ 
+Ensure that your changes are thoroughly tested by: 
+1. Running existing tests to ensure that they pass. 
+2. Add or update unit tests as necessary to cover your changes.  
+3. Make sure that all tests, new and old, pass before submitting a pull request. 
+
+ 
+Thank you for contributing to the WeatherGenerator! Your contributions are greatly appreciated. 
+