| Re: [epp-dev] Java package |
|
+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:
|
