It's really up to you, if you want to cede some creative control, or if you want full control.
Hadrien Mary
@hadim
it does indeed
Well I want to make it easly accessible so an "official" plugin is better in my opinion
Curtis Rueden
@ctrueden
So then you have two choices: "standard" or "external"
"external" gives you more control, whereas "standard" makes less work for you.
Hadrien Mary
@hadim
and I don't think I'll loose control on it or if I do that will be for the best I guess
hum what is the difference for the end user ?
does they have to enable update site ?
for external
Curtis Rueden
@ctrueden
Well, by "cede control" I mean: someone else might cut a release of your plugin. Your master branch should be release ready all the time. Etc.
Standard and external are both explained at the link above.
_
Hadrien Mary
@hadim
Ok then a standard plugin is ok for me
Curtis Rueden
@ctrueden
If standard, it lives at https://github.com/fiji and has sc.fiji groupId. The maintainers can push commits, cut releases, etc.
If external, you keep in your org. Different groupId. No one but you (unless you desire otherwise) can push commits etc. Fiji maintainers need to file PRs.
The downside is that if we need to make a change to bring your plugin up to compatible again with the latest stuff, then there might be a delay on you merging it, leaving users with a broken version of your plugin for days or weeks.
Does that make sense?
Hadrien Mary
@hadim
Yes perfectly
Curtis Rueden
@ctrueden
But some devs have been prickly about other people e.g. cutting version 3.0.0 of their plugin when they had some big idea about what "3.0.0" was going to be on their internal roadmap.
SemVer doesn't really conform to that romantic versioning idea, though.
Hadrien Mary
@hadim
I am fine and don't worry I am not really prickly
Let's go for a standard plugin then.
Curtis Rueden
@ctrueden
Anyway, "standard" plugin does not mean you stop supporting it, though. Standard Fiji plugins should have a support, debugger and reviewer at minimum. (A lot don't, but that's life.)
Cool.
I see that you listed yourself with all those roles, so that's great.
Hadrien Mary
@hadim
:-)
Curtis Rueden
@ctrueden
What we want to avoid is getting this awesome plugin into core, then people start using it, then they ask about it on the forum, and... no one answers the questions.
Hadrien Mary
@hadim
I read the Wiki
no I will support it for sure
Curtis Rueden
@ctrueden
Fabulous!
Hadrien Mary
@hadim
at least for few years (I can';t promise my whole life of course)
:-D
Curtis Rueden
@ctrueden
OK, so... can you transfer it to the fiji org then?
Hadrien Mary
@hadim
Is the Zenodo ROi I setup ok for you ?
Curtis Rueden
@ctrueden
Of course. If you need to stop supporting it, I just want to document that in the POM if/when it happens, so we can update the wiki automatically, so people's expectations are updated.
Hadrien Mary
@hadim
Ok perfect.
Curtis Rueden
@ctrueden
It is fine if you want to use Zenodo. I haven't personally gotten into it yet.
I guess ultimately we may publish ROIs for all the core ImageJ stuff, but... it needs to be fully automated or we will go insane.