The Transterpreter Project

Concurrency, everywhere.


Coming reorganization

Software projects aren't. The Transterpreter is a small and portable runtime for the occam programming language. However, there is more to the Transterpreter than just the TVM (the core interpreter). There are wrappers for each platform we target, the SWIG FFI generator, the toolchain (currently the slinker, and soon 42, our new compiler), as well as documentation, educational material (for use in the classroom), and applications. In our case, we have two primary areas of application---wireless sensor networks and robotics, both embedded contexts.

However, there's a hidden aspect to the project that we have had our eyes on for some time, but really never kept up on---the WWW. The Transterpreter.org site was largely static when we first built it, and I believe that is inappropriate for reporting on the work we're doing as a team. The goal is to have an easy way for us to publish updates and information pertaining to our work in a flexible form that can easily be subscribed to in several different ways.

Structure

Currently, our site is a collection of static pages, and one weblog where we post updates. I recently promoted that to the top-level of the site, as it was the most interesting/dynamic part of the site. However, I think I can take this much further. In the coming Transterpreter.org site reorganization, I'll treat every aspect of the project as a flowing source of information and updates, easily aggregated and redistributed. Practically, this means that the Transterpreter.org website will become a collection of weblogs; it will be easy to add new weblogs, and they'll all be aggregated through the main part of the site.

It is possible that we should just announce and discuss more about the Transterpreter on the mailing lists---in fact, I might encourage the group to begin doing so. However, people go to Google to find information when they're stuck, and therefore exposing as much information as possible to search engines in a structured format that can be repackaged and repurposed (a DB-backed weblog exporting an RSS feed) seems to make a great deal of sense.



Metadata

  • Posted: February 19, 2006
  • Author: Matthew Jadud
  • Comments: None
  • Tags: None