Priority of cleaning up unclear legal status

Well, I know there were fantasies expressed in some quarters, that Apache would just take the OpenOffice.org code from Oracle, slap an Apache license on it, and hand it over, along with trademarks, website, etc., to LibreOffice. Those fantasies have gone unfulfilled.

It would probably be very unsatisfying to develop new fantasies that Apache will do this for the Symphony contribution. The plan of record, as decided by the community, is to merge enhancements from Symphony into OpenOffice and release this code as part of Apache OpenOffice 4.0.

Remember, Symphony is not an entirely different code base. It is a fork of OpenOffice.org. We're just rejoining the codebases and ending the fork.

If LibreOffice is truly interested in having "juicy tidbits" from it, then it is in their best interest for us to merge the code into Apache OpenOffice, where they can cherry pick from it, just like their ongoing harvesting of features from OpenOffice 3.4.1. It will be much easier for them to have one code base to sync from, then deal with two.