In order to install the files onto a customer's machine, I have to copy the files onto their machine, and so yes, I am distributing it. If I install both Moodle, and Microsoft's plugin, then I am distributing them as a combined work.
If you want to assume that Microsoft won't sue you, then that's up to you. Companies usually do not have the luxury of saying "oh, let's just cross our fingers and hope they don't sue". Companies have to play it safe. Besides, it's not just Microsoft who can sue, but also any of the many copyright holders of Moodle, plus any of the authors of the additional plugins that I happen to also install on the customer's machine.
Thanks for the clarification, Martin. I'm glad to hear that they're working on resolving the issue. (Of course, if they're afraid of the patent clauses in GPLv3, then they could always just release their code under some other GPLv3-compatible license.)
No, because if you are installing on a customer's computer, you are distributing, and so you would be breaking the license.
No, they didn't, which causes a problem since Moodle is being relicensed to GPLv3.
In fact, it would be stupid on their part to release source code to work with programs under incompatible license terms which would disallow anyone from legitimately being able to distribute it.
And yet, that's exactly what Microsoft did. Moodle is switching to GPLv3, and Microsoft's plugin is GPLv2 only.
Actually, the original software (Moodle) is moving to GPLv3, while Microsoft has released their plugin under GPLv2 only which makes it impossible for anyone to legally distribute Moodle with Microsoft's plugin. Not only that, but Moodle had previously be licensed under GPLv2 or later, so using a GPLv3 plugin was always fine. So it would have been better if Microsoft had used GPLv3 instead.
Hmpf. 128MB? My first USB drive was a whopping 8MB! And I still haven't figured out what to do with all that space. I usually transfer files over the network, so what would I need a USB drive for?
No, rev was in previous versions of HTML, but was apparently dropped in HTML 5, probably because people didn't understand the different between rev and rel.
rel="canonical" and rev="canonical" are different things
Good point, but the other side to it is that if we go back to the idea that if you don't like it you can fix it. Whereas the coding can be a heavy time investment, hiring developers can be a heavy financial investment, perhaps costing even more than buying a proprietary program to do the same thing.
Agreed, as long as there is a proprietary program that does what you want it to (or close enough to what you want).
With the industry that I work in, the proprietary solution is very expensive, and the FOSS solution does 90% of what people want, and custom development is fairly easy.
Modifying OpenOffice.org or Cinelerra is probably a much harder task.
It's a naive, domestic operating system without any breeding, but I think you'll be amused by its presumption.