Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipse-ide-wg] Eclipse IDE Working Group proposed changes to Current Mission & Strategic Objectives

Hi Manual and Mickael,

I agree with Mickael that the impression of:

"Provide governance, resources, and funding for the development of the Eclipse IDE packages and the Eclipse platform"

makes it look like the WG has something to do with governance of the  Eclipse Project (aka Eclipse Platform). It doesn't - the EDP covers project governance and there has been no discussion of changing that in any way.

That said - I hope the WG can influence and partner with the Eclipse Project - but that influence and partnership are within the EDP.

The IDE WG should be providing the governance (some of it delegated to the Planning Council) of the Eclipse IDE packages (and SimRel). And the WG should be providing resources and funding to any area of the ecosystem in order to achieve the mission of the IDE WG. 

As we refine our message we should be mindful of the distinction of the Eclipse IDE vs. Eclipse Project. I also think that we should not use the term "Eclipse IDE platform" anywhere as that muddles the two closely related items.


Jonah Graham
Kichwa Coders

On Sun, 6 Jun 2021 at 13:54, Mickael Istria <mistria@xxxxxxxxxx> wrote:

There are a few things I'd like to discuss, mainly things that are giving the impression that the WG has some extra power over the Eclipse Platform or other Eclipse projects, which are already governed by the EDP independently of the working group. The WG goals are IMO to be focused on the ecosystem and the "product" (ie pages and other content that is not part of an Eclipse project) and its marketing, not on the projects. Specifically:
* "Provide governance [...] for the development of [...]": I think the EDP does cover governance of development and WG has to clearly not be involved in that part. The WG can govern some other aspects (some funding and so on), but it's as far as I understand not intended to nor capable of governance of project development.
* "Increase the number and/or frequency of commits by engaging and incentivizing committers and community members working on the Eclipse IDE platform": this seems a bit too fine grained and only focusing on numbers (which are not a quality metric). For a strategic objective, I believe something more vague like "Stiumulate and grow the ecosystem of contributors to the Eclipse IDE and Platform". Things like number of commits and diversity of contributors can be KPIs for that objective.,..
* "Improve the user-friendliness and UX of the Eclipse platform for a better end-user experience." : I also think this is a bit too specific. Something like "Identify work items that seems most profitable to end-users and influence Eclipse IDE projects to prioritize them". Note than maybe "end-users" need to be clarified here, to ensure people think about the same targets. Maybe it would be nice to identify some personas to define the end-users and more easily communicate about them with the projects.

eclipse-ide-wg mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

Back to the top