ImageJDev.org web site

[ctrueden]

Hi everyone,

Here is an outline of our vision for the ImageJDev web site, imagejdev.org.
Our ultimate goal is to create a portal into all things ImageJ, but we would
like to solicit ideas from the community about exactly what that means.
Initial ideas include:

*Revision control.* A git repository of the ImageJ source code. We have set
up an experimental version of this resource.
*Existing resources:
** ImageJDev Git repository – http://imagejdev.org/source-code
* Fiji/ImageJ Git repository –
http://pacific.mpi-cbg.de/wiki/index.php/Downloading_and_Building_Fiji_From_Source

*Plugin repository.* A searchable repository of plugins, with users able to
easily submit their own (Drupal makes this easy). We are also interested in
the ability to install from within ImageJ itself using a "plugin manager"
module. (Do people like this idea?)
*Existing resources:*
* ImageJ Documentation Wiki –
http://imagejdocu.tudor.lu/doku.php?id=plugin:start
* ImageJ web site – http://rsbweb.nih.gov/ij/plugins/
* Fiji plugins – http://pacific.mpi-cbg.de/wiki/index.php/Category:Plugins
* The ImageJ Plugins SourceForge project –
http://ij-plugins.sourceforge.net/
* MBF ImageJ manual – http://www.macbiophotonics.ca/imagej/

*Community-driven documentation.* Information on how to use ImageJ for
various purposes, an index of available features, etc.
*Existing resources:*
* ImageJ web site – http://rsbweb.nih.gov/ij/
* ImageJ Documentation Wiki – http://imagejdocu.tudor.lu/doku.php
* MBF ImageJ manual – http://www.macbiophotonics.ca/imagej/

*Project management. *A Trac installation linked to the repository, making
it easy to browse developer efforts and track open issues. For an example of
what this looks like, check out the LOCI Software Trac (
https://skyking.microscopy.wisc.edu/trac/java/).
*Existing resources:
** Fiji gitweb – http://pacific.mpi-cbg.de/cgi-bin/gitweb.cgi
* Fiji Bugzilla – http://pacific.mpi-cbg.de/cgi-bin/bugzilla/

*Continuous integration.* A Hudson installation linked to the repository, as
well as the unit testing framework, to verify that various branches build
and test successfully. Hudson can perform many tasks, such as automatic
generation of JAR files and Javadocs, verification that unit tests pass,
reporting any problems via email, off-site backups, or anything else we
decide to script.

As listed above, various resources already exist covering many of these
ideas, so it may be that imagejdev.org can simply serve as an aggregator and
link to them as appropriate. However, there is something to be said for
unifying resources under an easy URL, with centralized authentication
systems. We would also be willing to host existing resources on
imagejdev.org, if anyone is interested in doing that.

Are there other resources people would like to see included or linked on the
site?

-Curtis

[was: ImageJ development involvement/contributions]
On Wed, Dec 2, 2009 at 9:16 PM, Raymond Martin <[hidden email]> wrote:

>  > http://imagejdev.org/
>
> I already went to that site before joining this list and looked through
> every
> page. Not much there to indicate what involvement might be permitted and
> further documentation is not available or is missing.
>

[was: A few notes (AWT2Swing) ...]
On Wed, Dec 9, 2009 at 2:50 PM, Raymond Martin <[hidden email]> wrote:

> I had a look at some of the more recent information on imagejdev.org
> and I have to say that I would be interested in discussing the points made
> further. The majority of the ideas seem to make sense, but there are a few
> that I personally think should be examined more closely before being
> strictly
> adhered to. I wonder if that site is going to open to allow postings and
> discussions?
>

[was: Add a plugin to the plugin list]
On Fri, Dec 11, 2009 at 9:32 AM, Christian Moll <[hidden email]>wrote:

> to add a plugin to the imagejdocu wiki. Press on the "Create New Content"
> and fill the form. Afterwards you will get a template side that you can
> edit.
> If your plugin-page is ready to share to the community, you have to edit
> the http://imagejdocu.tudor.lu/doku.php?id=plugin:start.
>
> All this can only be done by registered users.
> http://imagejdocu.tudor.lu/doku.php?id=plugin:start&do=register
>

[was: Outsider's opinion]
On Fri, Oct 23, 2009 at 4:38 PM, Johan Henriksson <[hidden email]>wrote:

> given how many features you can squeeze into 1MB code (vs 10GB images),
> it's hard to even motivate why you would like to download plugins
> separately rather than the entire project in one go. that cuts away the
> need for a plugin manager and yet another automatic updating system
> (that has to be made secure).
>