Agreed, but the WG only owns the items it works on and not the overall roadmap for the Eclipse IDE, which clearly doesn't have an owner at the moment, let alone a roadmap.
Anyway, let's focus on the WG itself and worry about such roadmap once we see what the WG turns into.
I thought that's part of the scope of the IDEWG, no? The IDEWG has a "wishlist" of items. Some items might span across multiple projects. Those need to be broken down to allow projects to understand the work/contribution that is coming to them and also to define
some of the acceptance criteria for that. Once this mediation has been done, work can be started by the IDEWG.
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.
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.
ide-dev mailing list