MOOCs are the hype these days. Everybody talks about them, many universities (among them, the most notorious ones) are pushing to have their own initiatives and courses and they have even made it to the most prestitgious newspapers.
However, MOOCs are still in their very early phases. They are a recent movement with not more than a couple of years and certainly we still are in a situation where we need to discover and test how to diploy them in the best possible way.
MOOCs share with the FLOSS (which is an acronym that unifies free software, open source and libre software) movement many characteristics: they pretend to be open, they are mainly Internet-mediated and they are on-line. It is true that MOOCs are courses where the main goal should be to learn and that free software projects have as main goal to build a (software) product. But if anyone who has had any software programming experience knows that building a product is to a major part a learning experience as well: the programming language and technicalities have to be learned, interacting with the infrastructure has to be mastered, and finally there is always many interactions with the rest of the team which fosters knowledge exchange. And, not to forget, free software projects have been around for quite long, with many of them being a success (probably there is much free software running so that you can read this blog post).