Welcome to FerriteDistributed.jl contributor documentation! In this document you find information about:
If you are new to open source development in general there are many guides online to help you get started, for example first-contributions. Another great resource, which specifically discusses Julia contributions, is the video Open source, Julia packages, git, and GitHub.
Contributing to documentation is a great way to get started with any new project. As a new user you have a unique perspective of what things need to be documented and explained better -- if something confuses you, chances are you're not alone. Remember that also simple changes like fixing typos are welcome contributions. If you are looking for specific things to work on you can look at open issues.
Small changes can be done easily in GitHub's web interface (see Editing
files). Every page in the documentation have an Edit on GitHub button at
the top, which takes you to the correct source file. The video Making Julia documentation
better guides you through these steps.
Useful resources
- General information about documenting Julia code in the Julia manual.
- Documentation for
Documenter.jlwhich is used to render the HTML pages. - Documentation for
Literate.jlwhich is used for tutorials/examples.
If you have found a bug or a problem with FerriteDistributed.jl you can open an issue. Try to include as much information about the problem as possible and preferably some code that can be copy-pasted to reproduce it (see How to create a Minimal, Reproducible Example).
If you can identify a fix for the bug you can submit a pull request without first opening an issue, see Code changes.
Bug fixes and improvements to the code, or to the unit tests are always welcome. If you have ideas about new features or functionality it might be good to first open an issue or discussion to get feedback before spending too much time implementing something.
If you are looking for specific things to work on you can look at open issues.
Remember to always include (when applicable): i) unit tests which exercises the new code, ii) documentation, iii) a note in the CHANGELOG.md file.