Re: [Notion-devel] what we're waiting for

[Ole J. B. <ole...@ya...>]

>> - fork an earlier version of Ion that didn't include Tuomo's additional
>> terms (or one that had a loophole in it), this means a lot of extra
>> work, when many people would like to see us moving on (start adding new
>> features, rather than going back and fix/add old ones).
>>
>
> Another "PRO" for this option is the libtu and libextl situation.
> AFAIK these libraries are also unmaintained now, and I don't imagine
> them growing in popularity to the point of it being helpful to have
> them as separate libraries.  IIRC, they were still part of the same
> package at the point when the license changes were made, so will be
> part of our original code.  I haven't had a chance to really dig in,
> so for all I know this might be a trivial issue.  All I know is this
> is the issue I ran into (trying to compile/install ion3 on a fresh
> system and failing since libtu/libextl were missing) that made me
> aware of the true extent of the problem.

I'm 99% sure this is a trivial issue.

> Also, what are the libtu and libextl licenses like?  if they're
> standard lgpl we have a great deal of flexibility with what we do with
> them, to the point of possibly using the latest libtu/libextl along
> with the older version of ion as a starting point, but if they are a
> similar modified license, it seems it will be all-or-nothing with
> regard to which version of the sources we use as a starting point.

They use standard licenses:
http://folk.ntnu.no/bronner/temp/ion3/repos/libextl-3/LICENSE
http://folk.ntnu.no/bronner/temp/ion3/repos/libtu-3/LICENSE

Last change in libextl is: Sat Dec 15 15:38:58 CET 2007
                libtu   is: Thu Dec 20 19:04:14 CET 2007
... if my checkout is the most recent. (I'm quite sure of that)

PS: does anyone know how I can check when a darcs repo was checked out
and if it was checked out lazily?

Date of license modification in ion3(-plus): Fri Apr 27 23:50:40 CEST 2007

> On another note, how much information do we have available concerning
> the issues that were fixed in the time between the license change and
> the most recent release?  It will make a rather large difference to
> how easy that work will be to reproduce if we have detailed
> information about the bugs we want to work on.
> More concretely, which resources would we be able to use if we do use
> the pre-license-change source code as a starting point:
> mailing list archives
> darcs commit messages
> changelog
> other???

Darcs patch/change descriptions:
	http://folk.ntnu.no/bronner/temp/post-license-changes.txt

Tarball of pre-license-change (from darcs, not an "official" stable release):
	http://folk.ntnu.no/bronner/temp/ion3/ion3-prelicense-change.tgz
(size due to inclusion of darcs repo)