Re: [ide-dev] Getting feedback on IDE

[Mickael Istria <mistria@xxxxxxxxxx>]

On 11/19/2013 03:40 PM, Mike Milinkovich wrote:

I would happily  use this exact issue as a reason against changing things in the platform. Changing things which impact our adopters (e.g. organizations which embed Eclipse software in their products) is much more likely to cause unintended consequences than changing things which impact our users (e.g. people who download and use Eclipse IDEs directly from our website).

So either we put changes in projects and we force adopters who don't want them [group A] to override them in there product,
or we don't put changes in projects and we force adopters who want them [group B] to copy them into there product.

In any case, either group A or group B will need to change stuff.

What are the criteria that tend you to prefer group A over group B?

--
Mickael Istria
Eclipse developer at JBoss, by Red Hat
My blog - My Tweets