Yesterday I was on a panel at the Open Source Business Conference with Eben Moglen, Diane Peters and Jim Harvie. The title of the session was “GPL 3.0: Directions, Implications, Casualties“, but what it was really about was providing a venue for the Free Software Foundation to talk publicly for the first time about the process that will be followed in creating the next versions of both the GPL and LGPL.
You can read a description of the process that Eben outlined in several articles, such as this one. Unfortunately, I was misquoted as saying that Eclipse would consider moving to GPL 3.0. At this point, I cannot imagine that happening. What I said in response to a question from the audience was that we would consider revisions to the EPL if that meant that we could combine our code with GPL and/or LGPL more easily. But for us to do anything along those lines would require some truly compelling benefits to justify the community work involved.
An obvious question is why was I there? Eclipse doesn’t use the GPL, so how does this impact our community? The fact is that this GPLv3 process is going to be a massive effort with potentially sweeping implications for both the free and open source communities. The FSF has said that as part of their process they want input from other communities, so we plan to be involved. How involved is still TBD.
This effort, along with the work going on at the OSI on license proliferation is going to mean that free and open source licensing issues are going to be a hotly debated topic for the next twelve to eighteen months. As one of the leading open source communities, Eclipse is going to be actively engaged in these conversations. It is going to be interesting to see how all this plays out.