The serious flaw that I see with LSB is twofold - its closed nature, to be sure, and its assumption of leadership. Leadership of an OSS project is a matter of respect AND competence. Each OSS project has its Benevolent Dictator. The position is assumed by the individual BD and accepted by the tribe. Why and how the BD assumes the leadership role is not the issue. How he maintains the position is. The BD is respected by the tribe both for his competence and his willingness to hear the voices of the tribe, both of praise and of criticism. He is willing to hear the suggestions for what they are - a good faith effort to contribute. While maintaining ultimate power over the project, he hears the soundness of the ideas and chooses directions based on the value of the ideas, not his own unilateral concepts.
The *ONLY* way that these OSS projects succeed and continue to improve is by using the open communication channels available to both the BD and the tribe members. Without that bi-directional communication, the project flounders and dies. That, unfortunately, will be the result of the LSB project if those involved in it think that they know better than the rest of the community and think that they can impose their will on the tribe. They may succeed in standardizing and marketing whatever they standardize, but where will they go then? Do they seriously think that the OSS community will simply follow like lemmings? They will succeed in causing the very same thing that the *NIX community has seen - fragmentation, animosity, and dissent.
The OSS Business Model?
I fully agree that 90% of the users use 20% of the features of a software product. Indeed, that 20% of the features is the core of the project. Now, IF I could code, I would surely make my software freely available - containing that 20% of the functionality. Why? To give back to the tribe that has given me the freedom of choice. But I am also aware that there are users who need that last 10% of the functionality that I choose not to incorporate in the free software. I certainly would implement those functions and make them available at a price. Everyone wins. Most of the users have a tool to help accomplish only what they need to do. The minority of the users get the functionality they need. I get the satisfaction of giving back to the tribe AND making a profit!