The community encourages discussion about proposed changes on ImageJ's communication channels. Submit your ideas!
Start on the forum, searching for discussions related to your contribution to get some context & background. It can also be helpful to search for applicable issues and plans across the spectrum of ImageJ resources. The ImageJ community believes that public discussion is important so that ideas are exposed to healthy alternate points of view rather than lost.
If you are interested in helping to tackle open issues, see the wish list page.
This web site
This site, imagej.net, is a wiki (similar to the Wikipedia project). This site is built by the ImageJ community, and anyone can contribute!
If you are an ImageJ user, contributing documentation is an easy way to give back to the community without needing to learn software development skills.
If you are a plugin author, please consider documenting your plugin on this site.
When in doubt, discuss your ideas publicly on the Image.sc Forum!
Changes to ImageJ1 are made by Wayne Rasband, who is the sole ImageJ1 developer. He takes patch submissions and then reworks them to fit within the project's development model and style before merging them. Attribution for the changes is noted in the release notes (see ImageJ1's Release Notes/News).
Methods of getting the patch to Wayne include:
- Send the modified code in a private mail to Wayne. He prefers not to discuss code on the ImageJ mailing list.
- Send a patch to Wayne via private mail. It should apply to the latest revision and must not use any Git extension because Wayne uses
patch(1)to apply the patch.
- Submit a pull request on GitHub against the ImageJ1 repository. Please note, though, that none of the past Pull Requests were merged using the standard Git workflow.
The important part is that Wayne receive the code/patch, since he is the only one with the authority to merge it.
(See also this nice response from Curtis Rueden on the ImageJ mailing list.)