My real point on that is that projects don't look out for the common good, they look out for their own good. My concern is with consistency between the projects. I have projects in my workspace that use Java, _javascript_, HTML, CSS, and C++ in them (client/server
mobile and web apps). My dream is that you seamlessly go from one language to another without having a huge paradigm shift (like a every language having it's own perspective). Until I see WTP and CDT projects (for example) working together to achieve consistency,
we need something to help guide them in that direction.
But that is independent of the WG proposal.
Doug.
Summing
up, the existing team of committers and the project leads (for a project contributed to) would (IMHO) still be the authority that decides what goes in or doesn't.
Yes, exactly. That's an important point. The IDEWG has to reach out to projects in order to align the "wishlist" with their plans and to discuss/clear any road blocks for upcoming contributions. Thus, the IDEWG also need to do some proper planning.
-Gunnar
