Thanks for your interest in contributing to RayFlare! The following is a set of guidelines for contributing to RayFlare, an open-source, integrated optical modelling of complex stacks. The goal of these guidelines is to make the development of the package efficient and sustainable and to ensure that every commit makes it better, more readable, more robust and better documented. Please feel free suggest changes and improvements.
(this guide is based on the Atom editor guide)
This project and everyone participating in it is governed by the RayFlare Code of Conduct. By participating, you are expected to uphold this code. Please report unacceptable behavior to the repository Administrator.
This section guides you through submitting a bug report for RayFlare. Following these guidelines helps maintainers and the community understand your report, reproduce the behavior, and find related reports.
Before creating bug reports, please check this list (including the closed issues) as you might find out that you don't need to create one. When you are creating a bug report, please include as many details as possible.
Note: If you find a Closed issue that seems like it is the same thing that you're experiencing, open a new issue and include a link to the original issue in the body of your new one.
Bugs are tracked as GitHub issues. Explain the problem and include additional details to help maintainers reproduce the problem:
- Use a clear and descriptive title for the issue to identify the problem.
- Describe the exact steps which reproduce the problem in as many details as possible. For example, start by explaining how you installed RayFlare and what you where trying to do.
- Provide specific examples to demonstrate the steps. Include links to files or GitHub projects, or copy/pasteable snippets, which you use in those examples. If you're providing snippets in the issue, use Markdown code blocks.
- Describe the behavior you observed after following the steps and point out what exactly is the problem with that behavior.
- Explain which behavior you expected to see instead and why.
- If there is any error output in the terminal, include that output with your report.
Provide more context by answering these questions:
- Did the problem start happening recently (e.g. after updating to a new version of RayFlare) or was this always a problem?
- If the problem started happening recently, can you reproduce the problem in an older version of RayFlare? What's the most recent version in which the problem doesn't happen? You can download older versions of RayFlare from the releases page.
- Can you reliably reproduce the issue? If not, provide details about how often the problem happens and under which conditions it normally happens.
Include details about your configuration and environment:
- Which version of RayFlare are you using?
- What's the name and version of the OS you're using?
- Are you running RayFlare in a virtual machine? If so, which VM software are you using and which operating systems and versions are used for the host and the guest?
- If the problem is related to S4, which compiler did you use? What were the installation steps you followed?
This section guides you through submitting an enhancement suggestion for RayFlare, including completely new features and minor improvements to existing functionality. Following these guidelines helps maintainers and the community understand your suggestion 📝 and find related suggestions 🔎.
Before creating enhancement suggestions, please check this list (including closed issues) as you might find out that you don't need to create one. When you are creating an enhancement suggestion, please include as many details as possible.
Enhancement suggestions are tracked as GitHub issues. Create an issue on that repository and provide the following information:
- Use a clear and descriptive title for the issue to identify the suggestion.
- Provide a step-by-step description of the suggested enhancement in as many details as possible.
- Describe the current behavior and explain which behavior you expected to see instead and why.
- Explain why this enhancement would be useful to most RayFlare users, maybe including some links to scientific papers showing the enhancement in action.
- List some other packages or applications where this enhancement exists.
- Specify the name and version of the OS you're using.
The process described here has several goals:
- Maintain RayFlare's quality
- Fix problems that are important to users
- Engage the community in working toward the best possible RayFlare
- Enable a sustainable system for RayFlare's maintainers to review contributions
Please follow these steps to have your contribution considered by the maintainers:
- Describe clearly what is the purpose of the pull request. Refer to the relevant issues on Bugs or Enhancements. In general, an issue should always be open prior to a pull request, to discuss its contents with a maintainer and make sure it makes sense for RayFlare. If the pull request is a work in progress that will take some time to be ready but still you want to discuss it with the community, open a draft pull request.
- Include relevant unit tests and integration tests, where needed.
- For new features and enhancements, include documentation and examples. Both in the code, as docstrings in classes, functions and modules, and as proper documentation describing how to use the new feature.
- Follow the styleguides
- After you submit your pull request, verify that all status checks are passing
What if the status checks are failing?
If a status check is failing, and you believe that the failure is unrelated to your change, please leave a comment on the pull request explaining why you believe the failure is unrelated. A maintainer will re-run the status check for you. If we conclude that the failure was a false positive, then we will open an issue to track that problem with our status check suite.
While the prerequisites above must be satisfied prior to having your pull request reviewed, the reviewer(s) may ask you to complete additional design work, tests, or other changes before your pull request can be ultimately accepted.
- Use the present tense ("Add feature" not "Added feature")
- Use the imperative mood ("Move cursor to..." not "Moves cursor to...")
- Limit the first line to 72 characters or less
- Reference issues and pull requests liberally after the first line
- When only changing documentation, include
[ci skip]in the commit title - Consider starting the commit message with an applicable emoji:
- 🎨
:art:when improving the format/structure of the code - 🐎
:racehorse:when improving performance - 🚱
:non-potable_water:when plugging memory leaks - 📝
:memo:when writing docs - 🐧
:penguin:when fixing something on Linux - 🍎
:apple:when fixing something on macOS - 🏁
:checkered_flag:when fixing something on Windows - 🐛
:bug:when fixing a bug - 🔥
:fire:when removing code or files - 💚
:green_heart:when fixing the CI build - ✅
:white_check_mark:when adding tests - 🔒
:lock:when dealing with security - ⬆️
:arrow_up:when upgrading dependencies - ⬇️
:arrow_down:when downgrading dependencies
- 🎨
- Use Markdown.
- Reference methods and classes in markdown with the custom
{}notation:- Reference classes with
{ClassName} - Reference instance methods with
{ClassName::methodName} - Reference class methods with
{ClassName.methodName}
- Reference classes with