+1.
There's also confusion about who is in charge of these decisions. EPP has been set up as a project, which generally means the committers decide. But I think the EPP has grown beyond solving simple download size and content requirements to become the face of
the Eclipse IDE. Having clear product management is critical. And of course, by tradition, us engineers will fuss and figure we know better :), but these are important things to decide.
Doug.
From: epp-dev-bounces@xxxxxxxxxxx [epp-dev-bounces@xxxxxxxxxxx] on behalf of Mike Milinkovich [mike.milinkovich@xxxxxxxxxxx]
Sent: Monday, May 05, 2014 2:15 PM
To: Eclipse Packaging Project
Subject: Re: [epp-dev] Java package
We need one of our community's governing bodies to decide on a strategy here. Perhaps the Architecture Council is the right place? Or maybe Markus gets to pick as the EPP leader. (e.g. the guy who's been doing all this work for the past N years.)
But we are not going to change the download page to "Doug's Installer", or "Eike's Installer", or any other installer just because it gets built first.
I don't see a consensus on the problem statement or the requirements. We might want to start there.
On 05/05/2014 2:03 PM, Doug Schaefer wrote:
That's a good point. I did get a good demo from Ekke on Oomph. It's pretty powerful, but might over solve the problem. There's also the Mentor Graphics p2-base IDE that they demoed
for us during the CDT Summit and posted to github (EPL-licensed). And I've been building p2-based installers for years.
The focus has to be on the newbie and providing a good out of box experience. Once set up, as the user gets more experience with Eclipse, doing a check for updates and using MPC to get new stuff will be their way forward.
Doug.
On 05/05/2014 1:53 PM, Doug Schaefer wrote:
That's all from me until I have an installer for you to try,
Talk to the folks behind Oomph.
|