Note to clarify the distinction between cf-units and cfunits
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- python
- Domain
- documentation
Research direction
Start by reading issue #89 and the existing cf-units documentation to find where the package distinction belongs. Explain that both cf-units and cfunits exist and why someone might choose one over the other; the work is done when the distinction is clear to documentation readers.
Written by the indexing model from the issue text.
Description
📚 Documentation
See #89. We just need to make it clear that both packages exist and why you might want to use one or the other.
- Dominant language
- Python
- Stars
- 79
- Forks
- 46
- Avg merge
- 9d 12h
- Merged PRs (30d)
- 1
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.
More from SciTools/cf-units
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
New: Issue Type: Bug
Difficulty 3/5 1-2 days Newbie friendliness 68/100
All issues in SciTools/cf-units
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100