Considering the fact that the only closed components (rather than applications) are a video driver that Nokia doesn't control the license of (it belongs to SGX) and the BME daemon, I don't know where all this confusion comes from. Every other N900 driver MeeGo uses is not just open source in the sense of having the source available, the kernel drivers are also either committed or being committed to the linux kernel upstream. For one thing, this means that all future releases would support the same hardware devices, for no extra effort, and so would any Linux distribution that uses a kernel after those drivers were committed to the source. As for different MeeGo images (SUSE MeeGo would be a MeeGo image), for those who don't catch slaapliedje's tone, the MeeGo approach means that any program written for MeeGo would work on any instance of MeeGo. As MeeGo is a fully functional system by itself, there isn't a necessity to add more stack elements and APIs, but it is open to any such additions. If a program uses one of these additional API's, obviously you would need to have that API as well. Often this would involve other open source technologies, but a good example of how proprietary code can play nice with MeeGo would be something like the OVI API, that Nokia would add in its MeeGo releases, for OVI Store maybe Music store of some kind, etc.