There is no "IDE working group". Although I do hope that someone will step up to drive the process of writing a charter and getting it created.
Regarding why Workspace Mechanic is the first, I'm not sure if I understand the question. Something has to be the first one we try. It seems to me that no matter which one we pick to be the guinea pig, we will learn a lot about what's possible.
Rather than the current ad-hoc approach, maybe the IDE working group could come up with a prioritized list of potential features to add to the packages? We could solicit suggestions and create a list that could include such things as who is going to maintain the feature, the impact it's likely to have on the packages, and who is going to test the feature for each package. Based on this, the list could identify in which release the feature will be included. Perhaps features could be sponsored by companies willing to fund their maintenance in return for a modest amount of advertising (something on the welcome page and a logo, for example)?
I agree with Doug – why the Mechanic and not any other.
The Workspace Mechanic is especially good at supporting team rollout of an Eclipse-based installation. But that’s not exactly what we want to accomplish with the packages, do we ?
Just looking at the download statistics on Marketplace – why not this one, for instance, which is rated 3rd of all solutions:
I surely don’t want to start a war here around what plugins to pick ; please take this just an example to illustrate the concept.
Martin Oberhuber, SMTS / Product Architect – Development Tools, Wind River direct +43.662.457915.85 fax +43.662.457915.6
This seems like it might be a good discussion topic for an IDE working group.
On 11/20/2013 06:01 PM, Doug Schaefer wrote:
I guess my main question is why this plug-in and not the other 20 or so that would make Eclipse Packages better. How did these guys jump to the head of the line? We should take a broader look at the kind of features we'd like the packages to exhibit and solve this in the large. Sent from my BlackBerry Z30 smartphone.
There is a proposal in play to add Workspace Mechanic to the packages. Current discussion suggests that we should add it to all packages, including yours.
I need all package maintainers to weigh in. A "+1 on behalf of..." will do. If you have reservations, please make them known. I assume that "I have no idea what Workspace Mechanic does" is on at least some of your minds. It would be good if somebody steps up to test that this inclusion will work before we go to the effort of pushing it through the IP process.
epp-dev mailing list
epp-dev mailing listepp-dev@xxxxxxxxxxxhttps://dev.eclipse.org/mailman/listinfo/epp-dev