| [dsdp-pmc] FW: Questions for tomorrow's call |
|
Hi folks, I put all of you responses into one email and sent it to Eddie.
Mika, I couldn’t answer all of the questions for your project. Can you
fill out additional answers? It probably won’t make this article, but
these questions are useful for future press interviews. Everyone: Eddie said we have until Monday to get head shots.
Please take a picture of yourself over the weekend. You can email me directly. Doug From: Gaff, Doug Hi Eddie, I was out of the office yesterday because my wife was having
some minor surgery. Sorry for the delay. I have gathered
information from the project leads in preparation for this call. Unfortunately,
it will be difficult to provide headshots of all of the project leads. I
can supply photos for a couple of us now. I can probably produce the rest
by Monday. Let’s discuss on the phone, though. Doug eRCP
I
also would like a photo of each lead, if available. http://wiki.eclipse.org/index.php/User:Martin.oberhuber.windriver.com 1-
What is the planned date for the next major release of your project? Version
number? The upcoming release for the Target Management Project is the
Remote System Explorer (RSE) 1.0, to be released on October 20, 2006.
See the Project Plan on http://www.eclipse.org/dsdp/tm/development/plan.php
for details. 2-
What are the most important features to be added in this release? This is the first release of the Target Management Project. The
most important features are listed in the Release Review slides,
available from http://www.eclipse.org/projects/slides/TM_1.0_Release_Review_v3.pdf,
slide #4: * A single consistent UI for accessing remote resources - Tree View (pluggable system types, subsystems, filters), Table
View, Remote Monitor - Remote Drag&Drop, Copy&Paste, Edit&Compare,
Properties, Search - Standard widgets and dialogs for remote open-file,
enter-password, move … * Provided standard subsystems / services - Remote file system access through ssh, ftp or dstore protocols - Remote shell (command) access through ssh or dstore protocols - Remote process access through dstore protocol on Linux - dstore protocol implementation and agent for remote search,
remote archive exploring, remote process and other pluggable miners * CDT Remote Launch Integration using gdbserver * Team sharing of connection and filter definitions 3-
What are the major benefits of those features? Users can get access to remote computers through a
comprehensive, consistent UI. They can operate on remote computers as if they
were local. ISVs can use the existing framework to plug in new
connection types for their types of connections or computers eaily. So they
gain a rich UI for accessing their systems through their unique
connection schemes easily. 4-
Will anything be left out of this release, and if so, what? "User actions" and "Import/Export" were
originally planned to be included in this release, but had to be deferred due to slow
legal and copyright review process and lack of resources. "User Actions" allow users to define their own
shortcuts for actions to be executed on the remote system, store them and share them in a
team for easy re-use. "Import/Export" allows to synchronize local file
systems with remote file systems easily. 5-
When will those left-out features be added? We are planning a Service Release of RSE 1.0 in December, which
will add those features. This plan is tentative right now and has not yet
been signed off by all stakeholders. 6-
The tool will run on which major operating systems? (Linux, Windows, MacOS) We are testing the RSE client UI on Windows 2000 and XP, Linux
(Redhat WS4 and Suse SLES9) as well as MacOS X with the IBM and Sun
JVMs. It should, however run on any supported Eclipse platform since it
is plain java. The Datastore server, which is needed to use all functionality
of the remote connections that come out of the box, is being tested on
Windows, Linux, MacOS, AIX and Solaris. In addition to that, secure shell (ssh) and ftp connections can
be made to any server that supports these protocols, including VMS,
embedded operating systems like VxWorks and QNX Neutrino, and Mainframes. 7-
The tool requires which version of Eclipse? RSE 1.0 requires Eclipse 3.2. The CDT Remote Launch Integration
requires CDT 3.1. 8-
The tool plugs into an existing Eclipse install does it install a new
distribution? RSE plugs into an existing Eclipse install. We also offer an
Update Site for easy access to our tool. For the upcoming release cycle (RSE
2.0, to be released in June 2007), we are going to join the Europa
Release Train such that our features will be integrated with the main Eclipse
Update Sites. 9-
Would you consider the project “mostly framework” or “mostly
tool” and why? RSE is about 50% of both. People can use it out of the box for a
variety of nice things to do, including ssh and ftp file transfers and
remote shell access. For ISVs, the framework is equally useful. 10-
What are the purpose and intended user group(s) for your project? Anybody who needs to access remote compute resources can use
RSE, although the features perhaps apply a bit more to programmers
than other types of users. We expect RSE to be used for accessing small
embedded device just like accessing remote mainframe computers, and in
fact we do currently have users and contributors in both areas. Looking at
the trend to use Eclipse more and more for embedded software
development, I'd expect also embedded software development use of RSE to
increase in the future. 11-
What other Eclipse projects does Target Management / RSE have dependencies on? The core RSE framework just depends on Eclipse Platform. The CDT
Remote Launch integration depends on CDT. In addition to those, we also
have an experimental "Discovery" feature for finding remote
systems through the DNS-SD protocol. This component depends on EMF 2.2.0. 12-
Please provide your full name, title, project and your role in it. Martin Oberhuber, Member of Technical Staff at Wind River Systems, Inc. Lead of the Target Management Project. Thanks
in advance. You are welcome. Feel free to browse our website, http://www.eclipse.org/dsdp/tm for
more information. Especially the upcoming Release Review Slides at http://www.eclipse.org/projects/slides/TM_1.0_Release_Review_v3.pdf
are a good read since they cover the current state of the project
quite accurately. For instance, you can read there that the current
size of the TM source code is 230161 lines of code. The slide also lists
the affiliated companies on slide #17. Another interesting fact is that we are conducting a planned and
coordinated testing effort with many of our users, which is
supported through the Eclipse Wiki - See http://wiki.eclipse.org/index.php/RSE_1.0_Testing for details. MTJ 1- What is the planned date for the next
major release of your project? Version number? MTJ will release version 0.7 in October of this year. MTJ will have the following features: ·
To create Eclipse Mobile Java Tools platform
that vendors can extend to support their devices. Extensibility in the first
phase includes o
Runtime management framework § adding
device adapter to manage emulators + real devices o
Build framework, customized and extensible build
process § Packaging
(CDC, CLDC, Java in Palm devices, Java in Nokia devices,…) § Signing
(differences between devices) o
Deployment framework ·
Provide default tools to develop mobile Java
applications. o
Create a project o
Create a code o
Compile o
Package o
Run in emulator o
Signing o
Transfer to real Device ·
Provide User and developer documentation
The current focus is on Windows
development. Eclipse 3.2 The tool can plug into an existing
Eclipse install. Both. There are equal parts
framework and tools. Mobile Java developments using
MIDP J2ME profiles. The Eclipse Platform. Mika Hoikkala Nokia MTJ project lead DD 1- What is the planned date for the next major release of your
project? Version number? Device Debugging will release Version 0.9 in June 2007 along
with the Europa Eclipse train release. We will release milestones with
Europa starting with milestone 3. 2- What are the most important features to be added in this
release? This release with contain a near-production quality Debugger
Services Framework (DSF) with will take advanced of recent enhancements in the
Eclipse Platform Debug Interfaces. This framework will allow commercial
device software tooling vendors to better implement their commercial debug
engines in Eclipse. The framework will contain an MI implementation
design to be the next generation CDT debugger implementation for GDB. The
release will also contain enhanced debug view support, including multi-core
capabilities. Finally, the release will contain initial tooling for the
IP-XACT Debug specification currently in design in the SPIRIT consortium. 3- What are the major benefits of those features? Device Software Tooling vendors typically have proprietary debug
engines geared towards embedded-specific debugging capabilities. These
engines often provide greater visibility into and control over target
hardware. The DSF technology will provide a modular, extensible, and
performant framework for implementing embedded debuggers in Eclipse. Multi-core support will allow debugger views to associate
themselves with one or more debug contexts, e.g. processors, cores, processes,
threads. Multiple debug views of the same type will exist and will
display information specific to their context. For example, imagine
having two register views showing the hardware registers of two different cores
on an embedded processor. The SPIRIT consortium originally formed to provide EDA vendors
with common data file formats for describing system-on-chip hardware. The
consortium recently created a new working group around specifications for
debugger tooling. The IP-XACT debugger specification is designed to
provide silicon vendors with a standard data file format for describing their
hardware so that tools vendors can better display information from and provide
control over the hardware. 4- Will anything be left out of this release, and if so, what? API’s will be provisional in the 0.9 timeframe. We
are currently planning additional functionality (mostly features) beyond the
June 07 Europa release. 5- When will those left-out features be added? A maintenance release later in 07 will contain additional
functionality. 6- The tool will run on which major operating systems? (Linux, Windows,
MacOS) All, but the testing focus will be Linux and Windows. 7- The tool requires which version of Eclipse? The Europa release, likely versions Eclipse 3.3. 8- The tool plugs into an existing Eclipse install does it install
a new distribution? It plugs into an existing install. It is designed to be
used in conjunction with CDT, although CDT will be optional. 9- Would you consider the project “mostly framework”
or “mostly tool” and why? Mostly framework. The CDT project already provides tooling
for C/C++ development. The DD project exists to provide additional
frameworks for more customized embedded debugger implementations that one can
get from CDT or the Eclipse Platform.
In open source, the intended user group will be users of the GDB
debug engine. Commercially, we are targeting all companies that build
embedded debuggers on top of Eclipse. We intend to provide the
next-generation CDT debugger implementation while at the same time enabling
companies that do debugging outside of CDT. 11- What other Eclipse projects does DD have
dependencies on? Eclipse Platform CDT 12- Please provide your full name, title, project and your role in
it. Doug Gaff Engineering Manager, Wind River Systems DSDP PMC Lead, DD Project Lead NAB 1-
What is the planned date for the next major release of your project? Version
number? 2-
What are the most important features to be added in this release? 3-
What are the major benefits of those features? 4- Will anything be left out of this release, and if so, what? 5- When will those left-out features be added? NAB is still in 0.x releases. We are completing the
project plan now for potential alignment with Europa. 6-
The tool will run on which major operating systems? (Linux, Windows, MacOS) NAB supports Windows and Linux. 7-
The tool requires which version of Eclipse? NAB works with 3.2 currently and will adopt 3.3 as we get on the
Europa train. 8-
The tool plugs into an existing Eclipse install does it install a new
distribution? NAB can install into an existing Eclipse. 9-
Would you consider the project "mostly framework" or "mostly
tool" and why? NAB's look is mostly tool because it aims GUI builder like as
Visual Studio. However, the run-time libraries that implement the GUI widgets
can be extended for any operating system. These libraries represent the
framework. 10-
What are the purpose and intended user group(s) for your project? Our purpose is building a GUI IDE frameworks for CPU native code
widget libraries, with a specific focus on the embedded space. We are
targeting mobile GUI developers. 11-
What other Eclipse projects does EMF have dependencies on? NAB is not dependent on any other project, but we are compatible
with CDT. Developers can use CDT as a prototyping platform for testing
mobile GUI’s on a Windows or Linux desktop. 12-
Please provide your full name, title, project and your role in it. Shigeki Moride Fujitsu NAB Project Lead TmL Project is still in the proposal phase. |