[Tinyos-2.0wg] Proposal for TinyOS 2.x carveup

[David Gay]

I propose that we divide the work on 2.x into five separate areas:
- core: core services, and basic pc-side support code
- nesC: nesC language, compiler and support tools
- tools: all the tools you need to develop or run tinyos code
- network services: higher-level network services built on the core
- user friendly: tutorial and documentation

These don't all need to be working groups, as some of them are mostly
done (e.g., tools).

There's a more detailed description of what goes in core, tools and
network services at the end of this mail.

I haven't put OSKI in any of these groups yet, I'm not sure we want to
make it part of the core, but I'm not sure if we want a separate group
just for that... Phil? This also poses the question of what API the
network services build on: OSKI, or just stuff offered from the core?
And the same question for apps.

Let me know what I've forgotten, seems unecessary, or in the wrong
place. If we agree on this breakdown, we can figure out what still
needs doing, and who can commit to doing it when...

David


Core:
- platform-dependent core services, with corresponding teps
  * for each platform, as appropriate: mica2, micaz, telos a/b, eyes, imote2
  - basic services (booting, nesC support, scheduler support, I/O pins,
    interrupts)
  - leds
  - timers
  - adc
  - buses (SPI, I2C, UART, etc)
  - radio (single hop)
  - storage
  - hardware id
  - power management
  - security
- platform-independent core services, with corresponding teps
  - random numbers
  - resource arbitration
  - scheduler
  - serial packet-level communication
- sensor boards
  - sensor board tep
  - mica family: micasb, ucla (probably basicsb too)
  - telos a/b: built-in
  - all: DemoSensorC
- tossim
- automatic test suite
- apps
  - BaseStation
  - demos: Null, Blink, RadioCountToLeds, RadioSenseToLeds
- pc-side
  - serial forwarders: Java (net.tinyos.sf), C
  - SDK
    - Java:
      - serial port (net.tinyos.comm)
      - packet-level communication (net.tinyos.packet)
        (serial protocol, serial forwarder protocol, tossim)
      - mig (net.tinyps.message)
      - simple apps (net.tinyos.tools)
    - C:
      - serial protocol, serial forwarder protocol
      - mig
    - other language??

Network services:
- tree-collection routing
- dissemination
- network management (nucleus)
- network services demo app (aka Surge)
  includes PC side (aka net.tinyos.surge)
- network reprogramming (deluge)
  - needs per-platform low-level reprogramming/etc support

Tools (tinyos-2.x/tools + external packages):
- provide compilers, programmers, debuggers for each platform
- our cygwin distribution
- misc tinyos tools
- misc platform tools
- our Java JNI code (serial, env, for now)
- ncc&co