Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "DSDP/RTSC/BoardReport2008"

< DSDP‎ | RTSC
m (End user community and adoption.)
m (Diversity)
Line 28: Line 28:
  
 
==== Diversity ====
 
==== Diversity ====
 +
The initial team of committers is made up entirely of TI engineers.  This is something we hope to change next year as we transition the XDCtools development to the Eclipse infrastructure.
  
 
==== Compliance with the Purposes  ====
 
==== Compliance with the Purposes  ====

Revision as of 18:34, 20 August 2008

This is the proposed Report for the RTSC project, to be presented to the Eclipse Board on September 17, 2008.


Review of project scope and charter

A high-level review of technical progress, strategy and release plans.

The RTSC project, formally proposed in Feburary 2008, has successfully passed two early milestone reviews and is now a fully provisioned incubation sub-project of DSDP. The RTSC team presented a short and long talk at EclipseCon 2008 describing the technical contributions of the RTSC project.

As a first step to moving XDCtools to open source, the previously TI internal RTSC documentation wiki (RTSC-Pedia) is now open to the community at http://rtsc.eclipse.org/docs. Next steps include

  • transition of an internal technical support and discussion mailing list to the RTSC newsgroup
  • submission of the XDCtools source code base for parallel IP review
  • migration & integration of existing TI internal ClearQuest RTSC bug database to Bugzilla
  • migration from Antlr 2.x to Antlr 3.x (to eliminate current IP dependencies) and refactoring of XDCtools to eliminate internal tool usage

Self-assessment of the performance of the project

Performance as an Eclipse open source project

Openness

As a first step toward transitioning TI internal RTSC development to Eclipse, we've moved our documentation wiki to [1]. This allows the RTSC team to quickly respond to community questions.

Transparency

Although we've held open technical calls about RTSC, there is little external visibility of the day-to-day technical discussions and roadmap plans. The RTSC team has been using an TI internal mailing list for support and technical discussions. We plan to transition this traffic to the eclipse news group in the hope that this will encourage users outside TI to chime in.

Meritocracy

Diversity

The initial team of committers is made up entirely of TI engineers. This is something we hope to change next year as we transition the XDCtools development to the Eclipse infrastructure.

Compliance with the Purposes

RTSC is extensible and allows the user to integrate a wide range of SDKs and 3rd party tools. The XDCtools product itself consists of over 125 RTSC packages. Many of these packages provide a "bridge" to commonly used embedded tools (e.g., MinGW and gcc compiler tool chains) and serve as exemplars for extensions to other tools chains.

Greenhills, for example, has created RTSC packages that enable the use of the Greenhills toolchain within the RTSC environment. This allows anyone in the community to easily deploy and manage target content pre-built with the Greenhills tools.

End user community and adoption.

Even though the RTSC project is still in incubation, the starting code base for the RTSC project is is code the TI's XDCtools product. This product has been in continuous development/refinement and use since 2001. The XDCtools are the foundation tools used to create and use several of TI's most popular embedded target content products, including DSP/BIOS and Codec Engine.

Although we have had several very positive deep technical reviews by external companies (Nokia, Ericsson, and Huawei), external adoption has yet to occur. Ericcson, in particular, was very positive and requested that these tools be made open source. The risk of being tied to TI proprietary technology as well as the risk that TI might stop support of these tools, made it impossible for Ericcson to adopt and depend on these tools.

Our hope is that by making these tools available to the community and integrating them into the Eclipse environment, we can attract contributors from other companies. This will greatly facilitate community adoption.

Commercial community and adoption

TI currently ships several products based on the XDCtools (the product associated with the RTSC project)

Compliance with the Roadmap

Board Assistance

The board has already been very helpful in clearing sticky licensing issues that had the potential to significantly hamper commercial adoption of the runtime elements provided by RTSC. At this time, the ball's entirely in our court.

Noteworthy

Back to the top