Escamillo wrote:
Can someone enlighten me as to why one would need the code?
The code isn't being made available for people who want to implement solutions on top of these protocols, but rather for people who want to write alternative implementations in place of Microsoft's implementations so they can make use of them, say, for alternative platforms. The hope is that by making the source code available, Microsoft will satisfy the EU's objections with the quality of the documentation they've been preparing. If someone wanted to write an SMB implementation compatible with Windows, they can consult the source to understand exactly how the protocol works, without having any worries of discrepancies.
Interestingly enough, though, this still doesn't solve the strongest issue of contention, which is that EU wants the licensing terms to be friendly towards open source implementations. I'm at a bit of a loss as to what exactly they expect Microsoft to come up with. Open source licenses, specifically the GPL and GPL-compatible licenses, where designed to be as unaccomadating to proprietary licensing as possible. The fact that the GPL stipulates that licensees have the right and obligation to redistribute the source in its entirety means Microsoft really can't license the protocols to GPL projects per se. Essentially, they'd have to give the protocols away, which is what the FSF is fishing for without explicitly asking for it. I have to wonder if the EU commitee has the slightest idea what they're talking about.
I'm not a lawyer, so maybe I'm missing something. I can see licensees incorporating implementations into LGPL and BSD projects, but not GPL ones. Could anyone illuminate further?
EDIT: I want to be clear I'm not implying the GPL is "anti-capitalist" or "communism"; I simply don't think the GPL plays well with other licensing schemes.