[Tinyos-alliance] TinyOS WG 8/1 notes

David E. Culler culler at eecs.berkeley.edu
Tue Aug 1 11:55:11 PDT 2006


Alliance Working

David Culler
Ramesh Govindan
Phil Levis
Jack Stankovic

TEP dicussion
  - review of TEP Finalization box and WIKI on www.tinyos.net
  - Model of the TEP
      - (A) introduction with technical detail provided elsewhere
      - (B) self-contained document (more like Posix std)

Ramesh: looking for making it more self contained
  - web pages are ephemeral

Why is it the way it is currently:

source code needs to have extensive documentation (nesDOC)
should this be replicated in the TEP?
  - repetition (e.g., requires STD_CONTROL)
  - consistency (TEPs vs Source code?)
     - MUSTs better the same, but MAYs may differ
  - Time to delivery

Ramesh
  - only need to include interfaces that are introduced by the TEP

DEC
  - utilize CVS to make references persistent

PAL
  - may require our own CVS server

Audience Participation?
  - Ramesh: active small group

Get email out to TinyOS Devel on 101.

How have working groups dealt with TEP finalization
  - 102/103 have tended toward convergence
  - 101 has led to opening of new discussion

PAL: email on 101.

----------------------------------

Chartering working groups
  - Documentation (Informational, Tutorial)
      - lots of effort throughout the community.  Available and 
naturally grass roots
      - outputs: actual documentation
      - does it need a more specific term

  - Storage
      - provide forum for currently active efforts (Blockbooks, etc.)
         - files, blocks, indexes, ...

Should there be a call for participation?
Stakeholders => telecon => formation

-----------------------------------

Another substantial reference point for the Alliance: eclipse.org
  - IETF (networking) and OSDL (enterprise linux) provide fairly extreme 
starting points
  - eclipse offers an example that is software focused and has fairly 
broad contribution
  - introduces a family of membership classes that are associated with 
the software process as opposed to the protocol process
  - also presents another candidate source license (EPL)
  - working group page has a resources section is bylaws for these 
organizations


-----------------------------------
Actions:
   Push visibitliy of TEP 101 review process
   Finalize SC owner for TEP 102
   TinyOS Alliance BOF at Sensys
   Homework on Eclipse vs IETF models

   No meeting next week


More information about the Tinyos-alliance mailing list