imagej / imagej/imagej-modelzoo

Hosting models for BioImage.IO

Open
#5 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Java
Stars
6
Forks
4
PR merge metrics
No merged PRs in 30d

Description

We are changing the way we provide models for BioImage.IO, please take a look at here: https://github.com/bioimage-io/bioimage.io/blob/master/docs/join-partners.md

This is the manifest file for Fiji: https://github.com/bioimage-io/fiji-bioimage-io/blob/master/manifest.bioimage.io.yaml

Since Fiji/ImageJ is a community partner, I think it's better to migrate this repo: https://github.com/bioimage-io/fiji-bioimage-io to the imagej organization, either merge with this repo or keep as is.

We are also thinking if a third-party contributor made a model for your imagej plugin, it make more sense to submit it to your managed model repo rather than BioImage.IO.

Another question I have is, what's the logo and name you would like to use? ImageJ or Fiji? In any case, you can change them yourself here: https://github.com/bioimage-io/fiji-bioimage-io/blob/6034c76cda97fd9db48c8c1d6e2e285d1a80136b/manifest.bioimage.io.yaml#L2-L16

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading docs/join-partners.md and the linked manifest.bioimage.io.yaml, then review the current fiji-bioimage-io repository structure. Clarify whether the repository should move or merge, where third-party models should be hosted, and whether the branding should use ImageJ or Fiji. Done means these hosting, repository, and naming decisions are agreed and reflected in the relevant repository or manifest.

Written by the indexing model from the issue text.

Assessment

Domain
devops, machine-learning
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.