I’m doing some follow up on the discussion draft of GPLv3 today, and it’s not going well for the folks at the Free Software Foundation. The positive press that surrounded the draft on day one has melted away to reveal what resembles widespread criticism of not only the draft, but of the FSF itself. As people read over section 11, and noted the bracketed “needs work” text, they started asking: Is Novell’s partnership grandfathered in to the GPLv3?
In an interview with Boston-based IP attorney Jeff Seul today, he and I discussed the GPL and its “ambiguity problem.” It was Seul’s opinion that the draft has become such an ambiguous mess he could no longer provide legal advice for clients coming to his office with the intent of starting a new business of project based on GPLv3′d software. In Seul’s words, “the FSF model is collapsing in on itself.”
While that interview percolates in the editing chamber, you can chew on this email I received from one of my user contacts regarding the GPL. In it, founder of the Washington, D.C., Linux Users Group and a researcher at the University of Maryland Przemek Klosowski tells a tale of two generals, and delves into the DRM aspects of the draft.
I am bemused. As the old military saying goes, the one thing worse than a bad general is two good generals. I see problems with GPL2 but the problem of dealing with differences and choices between GPL v.2 and v.3 just seem like a headache. The big difference is in DRM approach, and I would prefer that people had an option: either not care and use GPL2 or add an anti-DRM clause. Stallman wanted the anti-DRM to be the default so that why it is not an extra clause but the whole new version.
In the end it is just a lot of lawyerspeak barking, while the FOSS caravan goes on.
FOSS carries on, for sure, but will the FSF?