Add stats on tools?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 171
- Forks
- 75
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 20
Description
In a recent discussion about tools supporting ome-zarr, I realized that while the tools section is comprehensive, there is little that indicates which exactly would be a good starting point. Maybe we could include gh stars or a small view of the commit activity of the respective repo over time so one can assess the popularity or activity of a repo from our table?
I can see on the downside that this will funnel users to the big few tools that have been around for the longest time, though.
Contributor guide
No contributing guide indexed for this repository
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 locating the tools section and reviewing the recent discussion about tools supporting ome-zarr. Define whether the table should show GitHub stars, commit activity, or another signal, then document the chosen approach and its tradeoffs so readers can compare tool popularity or activity.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100