OpenFreeEnergy / OpenFreeEnergy/openfe
Protocol modules renaming
Open
Nobody has claimed this yet.
2.0
- Dominant language
- Python
- Stars
- 331
- Forks
- 56
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 13
Description
In #1769 we find that the original naming structure for protocols is inadequate. We should try to find a structure that makes sense to us and users for an OpenFE v2.0.
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
Start by reading issue #1769 and the discussion in this issue to understand why the current protocol naming structure is inadequate. Map the existing protocol modules and identify the proposed OpenFE v2.0 naming requirements. Done means the project has an agreed, documented module structure and a clear migration scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100