Friends of Eclipse,
Eclipse is an open source community that benefits millions of developers around the world each and every day! During the month of September, we are asking you to give back to our wonderful open source community. All donations will be used to improve Eclipse technology. Your contribution counts!
We thank you for this gesture, and for giving back to our community.
Tollfree in the US: 877-421-0030
Access code: 173098#
Full list of phone numbers
Call Time: 8:00 AM Pacific; 11:00 AM Eastern; 1500 UTC
We discussed pros and cons. Actually had a hard time thinking of any "cons". Only ones mentioned that came close was that the move could result in less then ideal integration with xml/sse fromwork. It might lesson the need or viability of an "xml project" thats been discussed at times ... by setting an example of xml going where its used, instead of a central technology point. Might inhibit Vex from expanding out into new areas where a visual xml editor would be useful (and instead focus on only the documentation use cases). But none of those seemed very large or likely, at least not to out weigh the advantages that were anticipated: closer to like-minded developers and end-users. Especially since there were no other dependencies on it within WTP or (as far as we know) adopters of WTP [after all, it has been incubating] so any new uses/dependencies, etc., could be worked out as well in one project vs. the other. In other words, move request approved. Compliments to Dave and others for thinking of it and taking a constructive, proactive, positive approach to improving Eclipse.
Neil mentioned an unanswered newsgroup/forum/mailing list post. We agreed it was fine for a PMC member to send email to project leads, pointing out an item of interest that they might be interested in responding to. [DONE]
Back to meeting list.
Please send any additions or corrections to David Williams.
Back to the top