These are chat archives for fiji/fiji

30th
Mar 2016
odinsbane
@odinsbane
Mar 30 2016 09:52
We are preparing to release a plugin that we would like to have a fiji plugin. We are not sure if it should be a Standard Plugin or an External project.
odinsbane
@odinsbane
Mar 30 2016 10:26
I think the first one I would like to setup is JFilament. I have met most of the requirements from http://imagej.net/Fiji/Contribution_requirements for a Standard project, but I am not sure I understand why something should be a standard project. It definitely sounds better.
Curtis Rueden
@ctrueden
Mar 30 2016 13:36
@odinsbane So you are sure you want it bundled with Fiji either way? (I.e. so users don't have to enable your extra update site)
Standard gives up some control, in favor of extra help. For instance: if we upgrade a fiji dependency used by your plugin, I might take the liberty of updating your master branch or even cutting a new release if your project is "standard" in the fiji org.
Some devs hate that and don't want Fiji maintainers with those powers. So they prefer external and the Fiji maintainers can only file PRs.
Downside is: your plugin may be broken in Fiji sometimes if you do not act on those PRs with a day or so.
"Sometimes" should be rare though -- we don't break backwards compatility all the time.
odinsbane
@odinsbane
Mar 30 2016 15:01
We definitely would like to bundle it with fiji either way. I think 'standard' sounds find, but I need to make sure everybody is ok with that. I think everything is compatible with the java-8 version of fiji. Ill try to finish getting the pom and the SemVer stuff up to par with the contribution requirements page.
Curtis Rueden
@ctrueden
Mar 30 2016 16:44
@odinsbane :+1: Let us know if any issues arise!