Consider the scope/need of "issues" on this repository
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- github
- Domain
- devtools
Research direction
Review the linked ome/ngff issue and the repository's GitHub issue, Wiki, and Discussions settings. First determine whether this repository should centralize issues in ome/ngff or define separate scopes; done means the maintainers have chosen and applied a clear policy, including the proposed Wiki and Discussions changes.
Written by the indexing model from the issue text.
Description
Currently it is a bit unclear which issues go on "ngff" and which issues go on "ngff-spec".
E.g.
Some options include:
- Disabling "Issues" here and redirecting all issues to ome/ngff. (my choice, for centralizing things)
- Clarifying which issues go where
IMHO people will likely get confused on the scope of which, but there may be advantages of having the two forums.
Definitely "Wiki" and "Discussions" should be disabled here.
It is possible to close issues across repositories automatically too, so we could use that trick.
- Dominant language
- Python
- Stars
- 14
- Forks
- 19
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 ome/ngff-spec
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 Half a day Newbie friendliness 67/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Maintainers usually reply within 1 day
-
comp/desktop P3 type/feature
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
NousResearch/hermes-agent#154285 ·
Maintainers usually reply within 1 day
-
docs: qualify copied and custom kubectl debug policy notesPossibly taken @nym01 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
kubescape/cel-admission-library#166 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
SACGF/variantgrid#2804 · 1 comment ·
Maintainers usually reply within 1 day
-
[BUG] HTTP lifecycle dispatch treats a NO_PROXY-only environment as corporate egress and skips the resolve-and-pinned sessionPossibly taken @bodapatisaikrishna claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day