The community encourages discussion about proposed changes on ImageJ’s communication channels. Submit your ideas!
Start on the Image.sc 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 site, imagej.net, is a wiki (similar to the Wikipedia project). This site is built by the ImageJ community, and anyone can contribute!
Contributing documentation is an easy way to give back to the community without needing to learn software development skills.
Changes to the original ImageJ are made by Wayne Rasband, the ImageJ developer, along with many contributors. 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 Release Notes/News).
Methods of getting the patch to Wayne include:
- Submit a pull request on GitHub against the ImageJ repository. Be aware that PRs will be reviewed and integrated by hand, not merged via the standard Git/GitHub workflow.
- Send the modified code in a private mail to Wayne.
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.)