[Notion-general] Notion LGPL branch

[Arnout E. <no...@bz...>]

Hello,

As you're all probably aware, Notion is currently licensed under the Ion 
license, which is an unfortunate state of affairs. 

When we forked Ion3, we had to decide whether to ignore the work done in the
2007-2010 timeframe and continue LGPL, or take the latest version and be stuck
with an inconvenient license. We chose the second approach, but expressed the
intention that when Notion turned out to be a viable project, we'd like to 
move back to clean LGPL eventually. Preparing for this, we've asked all 
contributions to be dual-licensed LGPL and Ion-license.

This is paying off. Last week and this weekend I've been performing some git
trickery and having manual merge fun. The result is an 'lgpl' branch in git,
which does not contain any code from the LGPL era, but does contain all Notion
contributions from the last 2 years. When we make improvements to either 
branch, these can be easily merged from the one to the other. 

For the nitty-gritty about the git trickery going on here, see my blogpost at
http://arnout.engelen.eu/gikilog/commit/fc50db7d80e25b7ca707147670510d8a3c55450e/
and of course the sf.net git repo's :).

Now that we have the Notion LGPL branch in place, it's time to have it catch 
up on what happened in the 2007-2010 non-LGPL era. 

I would like your help in:

* Test the LGPL branch. If you find any regressions, mention them in the 
  sf.net tracker I created for this purpose at
  https://sourceforge.net/tracker/?group_id=314802&atid=3208161
* Help double-check none of the Ion-licensed code slipped through into the 
  LGPL branch. I'm fairly confident my approach was solid, but the more 
  eyeballs we have here the better
* Perhaps going through the patches at 
  https://sourceforge.net/apps/mediawiki/notion/index.php?title=Licensing_FAQ#List_of_patches_since_license_change
  and help mark trivial/uninteresting/outdated or 'already covered by an issue
  in the lgpl regressions tracker'

I would *not* like your help in:

* taking information from the non-LGPL patch sets, and directly submitting this
  information to the bugtracker. 

The latter could be considered 'copying' non-LGPL information into the LGPL 
branch, which we don't want. Communication between the two worlds should 
always be in functional, abstract terms, nothing even remotely 'close to the 
code'.


Kind regards,

Arnout