<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi all<br>
<br>
On 29-Feb-12 21:30, Curtis Rueden wrote:
<blockquote
cite="mid:CADN69yme_NePuOE+2faNQ30bWYtEFgJGOPGse7+wb0pcni9-NQ@mail.gmail.com"
type="cite">Hi Tobias,<br>
<br>
<blockquote style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex" class="gmail_quote">I moved
the net.imglib2.algorithm and net.imglib2.stats packages<br>
from the imglib2-core into the imglib2-algorithms sub-project
(because<br>
thats where they should belong.)<br>
</blockquote>
<br>
The problem with moving things from core to algorithms right now
is that implicitly, it changes the license from BSD to GPL.
ImageJ2 cannot include imglib2-algorithms, because of this license
difference.<br>
<br>
</blockquote>
[snip...]<br>
<blockquote
cite="mid:CADN69yme_NePuOE+2faNQ30bWYtEFgJGOPGse7+wb0pcni9-NQ@mail.gmail.com"
type="cite">
<br>
The tricky bit is, the other primary motivator for multiple JARs
is, as touched on above, licensing. We need to balance and
reconcile those two needs. The most surefire solution is to have a
separate module/JAR for each combination of licenses and
dependencies—and hopefully that number of modules remains
manageable.<br>
<br>
Maybe it is time to split up imglib2-algorithms into multiple
submodules? I would be happy to do it, if we all agree.</blockquote>
<br>
<br>
So if I get the bug picture correctly and try to summarize it: <br>
<br>
- ImageJ2 is a standalone software, that only contains BSD pieces.
It uses as its core imglib2, and the concerned packages (core, io,
nothing else, right?) are all BSDs. The BSD license was chosen to
facilitate dissemination in other softwares, e.g. commercial ones (I
am pretty sure I got it wrong there).<br>
<br>
- Fiji is distribution that includes ImageJ2. It is GPL3 and as such
allows extra goodies, such as the imglib2 packages that are not BSD,
like the algorithms. imglib2 algos are GPL3 so that we constrain
creations based on these algos to be GPL3: then we (Fiji community)
can benefit.<br>
<br>
Right?<br>
<br>
<br>
Then the way to know what should go to core vs algorithms depend on
what ImageJ2 want to offer. There might be a list of target features
for ImageJ2: when they are all implemented, the IJ2 team know that
the soft has reached version 1.0. <br>
<br>
So, any part of imglib2 that is needed to complete this list of
feature should go to the core. <br>
<br>
In that view, Curtis said that having the ability to display
histograms is a IJ2 core feature, so it should go to the core. The
FloydSteinberg dithering is more like a plugin, so it can go to
algorithms. But why algorithms could not be a single large package?
<br>
<br>
Does that make sense?<br>
<br>
cheers<br>
jy<br>
</body>
</html>