GPL v3 Coming Out in 2007? 233
gentoo1337 writes "Eben Moglen of the FSF speaks out in this ZDNet article, noting that GPL v3 may be publicly drafted in early 2006, and in force one year later. The process is very sensitive (noting concerns of forking in the Linux world), but Eben Moglen is optimistic: 'When it's all over, people are going to say, "All that talking for just that much change?" [...] We will do no harm. If we think (some change) may have any unintended consequences, we will not recommend making it.' Controversies aside, there is some good news -- Richard Stallman aims to 'lower barriers that today prevent the mixing of software covered by the GPL and other licenses.' The earlier Slashdot discussion contains complementary info about the intentions of FSF."
Version conflicts? (Score:4, Interesting)
P.S. This is a real question, not a flamebait or troll...
Re:What's missing from GPL2? (Score:4, Interesting)
That's the argument. Personally, I don't know how I feel about it one way or the other.
This is old news (Score:4, Interesting)
Re:What's missing from GPL2? (Score:0, Interesting)
Re:Analysis Paralysis? (Score:5, Interesting)
I've said it before... (Score:5, Interesting)
licence free software (Score:2, Interesting)
Fonts (Score:4, Interesting)
It's unfortunate that such vagueness persists with the GPL, but it seems to be a trend with copyright issues in general (fair use being the most visible).
Re:Version conflicts? (Score:3, Interesting)
This is necessary because the period of copyright keeps increasing and more than 90 years is far too long to wait to change a license in the world of software.
Re:What's missing from GPL2? (Score:3, Interesting)
To state the concern more clearly say EvilCompany takes gcc, does some crazy optimizations, and starts running it on their server never releasing the code, call it pgcc (propietary gcc). Then they sell a small app ttpgcc (talking to propietary gcc) which communicates over the internet to pgcc. ttpgcc sends the code and whatever args to pgcc, which then compiles it and sends back the binary (assuming mad bandwidth and stuff). The user never recieves a copy of pgcc, thus they have no rights to the code under the gpl, however through ttpgcc EvilCompany is now selling an app which is effect a forked version of gcc.
I don't know how to disallow this scenario yet allow a webserver in a license but this certainly presents a problem.