| RE: [eclipse.org-requirements-council] RoadMap v2 proposed changes |
|
I’m OK with taking the following off
the requirements doc. Thanks Anurag There was a request to draw more attention to headless
support as a theme. There is a mention in the enterprise ready section:
"Provide a batch mode mechanism that makes it easier for
'headless' Eclipse tools to execute. For example, a batch mode for
building and creating Eclipse itself." The request was to add
"development" support to this theme. For example, "Enhance
tooling for headless development and provide a batch mode mechanism that makes
it easier for 'headless' Eclipse tools to execute. For example, a batch mode
for building and creating Eclipse itself. I am on the fence with this change as it appears to be
something that might be up for debate. Comments? From: Hi, I plan to make the following changes on Friday March 17th AM
unless I hear objections or suggestions beforehand. ========================== There is feedback that the "Strategic Goals"
should include mention of RCP because of it's strategic importance in 2006. Therefore, I propose to change the wording in 1 from "...a
development platform which is..." to be "...a development platform and rich client
platform (RCP) which is..." ========================== In the "Extend the Rich Client Platform RCP" theme
about 2/3 way down, RCP is referred to as a "Development Platform",
which is potentially confusing because technically the "runtime
platform" aspect is very important too. Therfore, I propose to
change the wording from "development platform" to "runtime
platform". Note that one of the sub bullets that says "Examine
alternatives for providing a more complete development for creating RCP
applications." There was a request to elaborate on this - can anyone
provide me context? Otherwise, I propose to strike this bullet since the
next bullet is more affirmitive in suggesting improvements. ========================== ================== Fundamental Principals has the following text: "Eclipse projects provide exemplary (show
by example) implementations and extensible frameworks. Examples target open
source implementations such as CVS, Ant, JBoss, JOnAS, Mono, and Tomcat." In what way are these related to these other projects? I propose that we do not call out specific technologies in this
bullet. Instead, I propose we say: "Eclipse projects provide exemplary
(meaning "show by example") implementations and extensible
frameworks. Where projects require use of other technolgies (such as source
control, application servers, build engines), they will target
exemplary free open source implementations of those technologies." =================== Under "Rich Client Platform", the bullet "More
complete control over the branding of RCP applications, including the changing
of all filenames from ’eclipse’." has been addressed in
3.1. I propose to remove it from the Themes and priorities and move it to
"Progress" in the main roadmap. =================== There was a request to draw more attention to headless
support as a theme. There is a mention in the enterprise ready section:
"Provide a batch mode mechanism that makes it easier for
'headless' Eclipse tools to execute. For example, a batch mode for
building and creating Eclipse itself." The request was to add
"development" support to this theme. For example, "Enhance
tooling for headless development and provide a batch mode mechanism that makes
it easier for 'headless' Eclipse tools to execute. For example, a batch mode
for building and creating Eclipse itself. I am on the fence with this change as it appears to be
something that might be up for debate. Comments? ================ Cheers, - Don -- Donald Smith donald.smith@xxxxxxxxxxx
Director of Ecosystem Development Office: (613) 224-9461 x231 Cell: (613) 292-5160 Fax: (613) 224-5172 Blog: http://eclipse-ecosystem.blogspot.com
|