-
Notifications
You must be signed in to change notification settings - Fork 0
Description
Hi @ctrueden and @dietzc, I finally finished to work on the OmeroBrowser and I'm read to release a first version of it. You can find the last version here.
I would like to understand what, in your opinion, is the best way to release it: as a plugin or bundled with imagej-omero?
The first thing to say is that this browser is based on a common project that I use in the Omega project.
Everything is setup for maven but I don't have an artifact repository yet so in case we would want to release it bundled in imagej-omero I would need to set one up.
The second thing is that either release solutions would have their own advantages.
The plugin solution would allow me to have more visibility and direct feedback from the user base, while the bundled solution would facilitate interaction with developers.
For this reason it is quite difficult to have to chose. Do you have any suggestions?
Do you see a way in which both solutions would be adopted at the same time?
Let me know what you guys think.
Thanks.