Not sure Jaime,
if I'm the right person to give advice regarding your Fiji-related
questions.
For various reasons I don't use Fiji but plain ImageJ and there are,
AFAIK no restrictions regarding the coding of plugins.
Please have a look at the valuable tutorial: "Writing ImageJ Plugins":
<https://imagingbook.com/wp-content/uploads/2013/06/tutorial171.pdf>
Of course you need access to the documentation of the ImageJ-API.
<https://imagej.net/ij/developer/api/allclasses-index.html>
AFAIK, there is *no* "official review or validation process before
public release".
One reason for this is the fact that it is near to impossible to do some
kind of validation of ImageJ itself. Please see older posts regarding
this issue. Below please find a compilation of some aspects I wrote here
2019:
============
From a WIKI we may get some insights to the meaning of the terms
"software verification and validation" (V&V):
<https://en.wikipedia.org/wiki/Software_verification_and_validation>
Cited from this WIKI:
*Software verification is*:
"Assuming we should build X, does our software achieve its goals without
any bugs or gaps?"
"*Verification*: Are we building the product right?"
*Software validation is*:
"Was X what we should have built? Does X meet the high level requirements?"
"*Validation*: Are we building the right product?"
According to this definition, *software validation* is highly
application- or task-specific. For rather universal software tools, such
as ImageJ/Fiji, the task isn't well-defined. This also holds for certain
ImageJ-plugins and, as it turned out in the past, even for software with
a rather restricted scope.
The above definition of *software verification* essentially deals with
the question whether a piece of software is correctly coded (actually it
reaches beyond this question). For this purpose it is necessary to
extensively test the software and perhaps to even check the source code.
============
If you want o make your plugin accessible using Fiji, then please see
here and contact the responsible persons:
<https://forum.image.sc/t/requests-for-creating-imagej-update-sites/40051>
Regards
Herbie
::::::::::::::::::::::::::::::::::::::::::::::::
Am 10.10.25 um 10:57 schrieb JAIME ALMAZAN POLO:
Dear Herbie,
I hope this message finds you well.
My name is Jaime Almazán Polo, and I am a researcher and lecturer at
Complutense University of Madrid (Department of Physiotherapy). Our
research group is currently working on ultrasound-based morphofunctional
assessment, and we are interested in developing a custom plugin for
Fiji/ImageJ to automate and standardize certain image analysis procedures.
Could you please provide information or guidance about the procedure to
propose, register, and distribute a new plugin within the Fiji ecosystem?
In particular, we would like to understand:
-
The technical and administrative steps required to develop and integrate
the plugin.
-
Any documentation, code templates, or repository guidelines recommended
for new contributors.
-
Whether there is an official review or validation process before public
release.
Thank you very much in advance for your time and assistance.
I look forward to your guidance.
Kind regards,
--
ImageJ mailing list: http://imagej.nih.gov/ij/list.html
