On Thu, May 24, 2012 at 3:01 AM, Ross Gardler <[email protected]> wrote: > Thanks for the pointer Shane. Its a shame people can't see this for what it > is. The LO team are taking a step that makes collaboration easier from a > technical point of view. This is a good thing. > > Yes, the sharing of code is still one way, unless individual contributors > decide to submit patches to both projects. However, the work involved in > doing this will be reduced by this action. This is a good thing. >
Well, yes and no. TDF always had the ability to accept ALv2 code via its compatibility with LGPL. So merely converting to MPLv2 does not enable anything that was not possible before. What does help is that they are now giving explicit thought to how this might work in their processes, and how they will note such combinations in their files. That, more than the license change, will make it easier for them to consume AOO code, and for contributors to contribute to both projects. > Well done TDF. > > Ross > > Sent from my mobile device, please forgive errors and brevity. > On May 23, 2012 2:44 PM, "Shane Curcuru" <[email protected]> wrote: > >> In case folks haven't seen this: >> >> http://legal-discuss.markmail.**org/thread/mleqsm636zf5fqia<http://legal-discuss.markmail.org/thread/mleqsm636zf5fqia> >> >> Which points to: >> >> http://wiki.**documentfoundation.org/**Development/Relicensing<http://wiki.documentfoundation.org/Development/Relicensing> >> >> So it looks like there will be plenty of code sharing! 8-> >> >> - Shane >>
