TopoToolbox / TopoToolbox/libtopotoolbox
Track feature parity between v2 and v3
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 2
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Description
I would like to have a table or something defining the functions implemented by TopoToolbox v2 and whether they have been implemented by v3 within libtopotoolbox and/or the packages.
This goes beyond libtopotoolbox, but this is as good a place as any to keep track of this task.
A GitHub project within the TopoToolbox organization might be the best way to handle this, because we could automatically link it to issues. It might also be something worth rendering on the main topotoolbox.github.io page.
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 comparing the functions implemented by TopoToolbox v2 with v3 in libtopotoolbox and its packages. Review whether a GitHub Project or a table on the topotoolbox.github.io page is the appropriate tracking location; done means the feature parity is recorded and kept linkable to related issues.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100