Develop coding style guide
Open
Nobody has claimed this yet.
documentation
- Dominant language
- Fortran
- Stars
- 249
- Forks
- 82
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 3
Description
It would be useful to have a coding style guide. This could cover information about formatting as well as style (do loops vs arrays).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or documentation entry points are named. Start by surveying the repository's Fortran source and existing contributor documentation to identify current formatting and style conventions. Done means publishing an agreed coding style guide that covers formatting and choices such as do loops versus arrays.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fortran
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100