> Sure, mixture of licenses makes life more difficult. Not an excuse for > ignoring non-BSD innovations and embracing Linux OSV/OEM community with > their preferred license. GPL'ed LibreOffice bugfixes can't go upstream > to BSD-like, ASF2 license of Apache OpenOffice, but that's life.
I spent the night trying to figure out how I probably misunderstand Andrew's BSD/GPL comments yesterday. :-( When I think of GPL additions to Tiano, I am thinking new modules, ProtoeonOSPkg, NanoBsdPkg, RefindPkg, new file systms, new smartcard drivers, etc. I'm thinklng less of GPL forks of existing Tiano BSD modules. Unlike the Apache OpenOffice/LibreOffice situation, any GPL variant would have some control over the shared Tiano code and could encourage BSD contributions to the shared code. Some forks may be necessary, but unlike AOO/AOO it is a single community and the common upstream code would be in interest of both communities. Back to the AOO/LO example, it is not just two separate communities. Some developers contribute patches to both codebases, which helps unify the two. There are problems when mixing code of two licenses. But ignoring GPL is MUCH harder for Linux OSVs than it is for closed-source ISVs. Long-term, I don't see how Linux OSVs can properly use UEFI without a Linux-aware IBV. Thanks, Lee _______________________________________________ edk2-devel mailing list [email protected] https://lists.01.org/mailman/listinfo/edk2-devel
