Stuff Michael Meeks is doing

Up early, to work - plugged away at mail, then various mono pieces; collected H. from creche. Set off a build of the 2.1 branch to find the bug Pavel reported.
Team meeting, spammed people with action items. Poked at mkbundle, with lots of patient help from Paolo & Miguel discovered that setting MONO_PATH is the cause of all my problems, unsetting that, using mkbundle2, using --deps (and amusingly re-setting MONO_PATH for that command) yield a beautiful standalone elf binary (well it (sadly) requires one extra libzlibwapi.so) that converts OOX to ODF and back.
Kay - revisiting the OO.o Java policy looks sensible to me - and not to look a gift horse in the mouth, but I'm confused: Java is GPL not LGPL - and there is a world of difference and pain here. Of course there is the ClassPath Exception, but what does that mean for OO.o ? is this essentially a 'Lesser' (LGPL like license ?) if so, why not just use the LGPL ? does it mean 3rd parties will no longer be able to write plugins ? is there a good explanation of the ramifications of the ClassPath exception ? will Sun be distributing it's own Java under the terms of the GPL ? the ClassPath licensing exception page is really rather vague. On the other hand, if this gets unwound, it's great news that perhaps we can make OO.o more buildable and usable, and not be so concerned about Java code drifting into OO.o.