When contributing to the development of Ariadne, please first discuss the change you wish to make via issue, email, or any other method with the maintainers before making a change.
Please note we have a Code of Conduct, please follow it in all your interactions with the project.
There are many ways you can contribute to Ariadne, and all of them involve creating issues in Ariadne issue tracker. This is the entry point for your contribution.
To create an effective and high quality ticket, try to put the following information on your ticket:
- A detailed description of the issue or feature request
- For issues, please add the necessary steps to reproduce the issue.
- For feature requests, add a detailed description of your proposal.
- A checklist of Development tasks
- A checklist of Design tasks
- A checklist of QA tasks
[Title of the issue or feature request]
Detailed description of the issue. Put as much information as you can, potentially
with images showing the issue or mockups of the proposed feature.
If it's an issue, add the steps to reproduce like this:
Steps to reproduce:
1. Run Ariadne
2. Load a FE model
3. ...
## Design Tasks
* [ ] design tasks
## Development Tasks
* [ ] development tasks
## QA Tasks
* [ ] qa (quality assurance) tasks
This is an example of a good and informative issue:
Using the coordinate descent method currently leads to an unstable solution, because there are functions that do not even lead to a local optimum. This is not good for high order elements, as the solution will only converge in some cases.
It is proposed to use a more complex but more robust Nelder-Mead method.
- Define how best to implement the Nelder-Mead method
- Implement Nelder-Mead method
- Check method convergence
- Check method stability
- Ensure your code compiles. Build project before creating the pull request.
- If you're adding new external API, it must be properly documented.
- The commit message is formatted as follows:
component: <summary>
A paragraph explaining the problem and its context.
Another one explaining how you solved that.
<link to the bug ticket>
- You may merge the pull request in once you have the sign-off of the maintainers, or if you do not have permission to do that, you may request the second reviewer to merge it for you.