Create a "kitchen sink" version of Fiji

[ctrueden]

Now that we have multiple update sites working so well, and they can shadow upstream sites' files, it makes sense to provide two versions of Fiji:

1. A "stable Fiji" that comes with only the really well-tested stuff enabled.

2. A "kitchen sink Fiji" that comes with lots of wonderful update sites enabled, and hence has new features and bug-fixes, but potentially with new bugs and at the expense of stability.

This caters to both archetypes of users in the wild.

It would of course be possible to transform either Fiji into the other by using "Manage update sites" to add or remove update sites as desired.

We can then list both Fiji distros from http://fiji.sc/Downloads with quick blurbs explaining the difference.

Migrated-From: http://trac.imagej.net/ticket/1982

[ctrueden]

@dscho Feel free to close if you prefer; obviously this issue is not one we would tackle right away. But I think it would be really cool once we are a bit further along on the ImageJ2 release train.

[dscho]

I am mildly negative about this because we try to put as few limits as possible on update site owners -- intentionally. That, however, means that the quality (or the trustworthiness) is highly heterogenous, and I would be really reluctant to give the kitchen sink version the "Fiji" rubber stamp...

[ctrueden]

I agree with @dscho that a "kitchen sink" version of ImageJ should not be called "Fiji" but probably something else, should we ever end up creating the Jenkins job that bundles it up.