MESAHub / MESAHub/mesa-contrib
Version control branches?
Nobody has claimed this yet.
- Dominant language
- Fortran
- Stars
- 14
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
I know most of these hooks are maintained individually, but it might be nice with each new version branch of MESA to create a new version branch here as well. That way when the procedures are (or are not) updated with each version they are tagged/included appropriately with the versions of MESA they are compatible with. It would help to make it more clear when a specific procedure is no longer being maintained for newer versions of MESA.
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 entry points are named. First clarify how MESA version branches should map to this repository and how procedure compatibility will be represented. Done means an agreed branching and maintenance approach that clearly identifies which procedures are compatible with each MESA version.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fortran, git
- Domain
- devtools, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100