[Tinyos-host-mote-wg] [Tinyos-2.0wg] 10/12/2005 Telecon Notes

[Kristin Wright]

-------------- next part --------------

Notes from 10/12/2005 TinyOS 2.0 Working Group 

Phil Buonnadonna (Arched Rock), 
Prabal Dutta (UCB), 
David Gay (Intel Research, Berkeley), 
Ben Greenstein (UCLA),
Vlado Handziski (TU-Berlin), 
Jan Hauer (TU-Berlin), 
Jonathan Hui (Arched Rock), 
Kevin Klues (WUStL),
Phil Levis (Stanford),
Kristin Wright (UCB)

10/12/2005 Agenda
-------------------
- who is going to work on what, when?
- managing tinyos 2 development, i.e., how do we deal with
collaborative development and the occasional need to change code/apis
written by others

10/12/2005 Discussion Notes
------------------------------------------------------------------------
NSDI 
------
Vlado: sending out line-count "instructions" so everyone
on the same page
 
2.0 Task Division
------------------
Platforms:
- eyes: 
  - Vlado: need to update to marshall new message_t; need
    SPI cleanup and resolution to smallish issues (which arbiter)
    for msp
  - 2 weeks for radio; only thing not working is AM
- mica2: 
  - david gay, crossbow
- micaz:
  - crossbow, phil levis, arched rock
- telos a
- telos b, micaz
  - arched rock  
- eyes
  - tu berlin
- imote2 
  - arched rock, intel

Subsystems:
 - buses (SPI, I2C, UART, etc)
   -tu berlin/arched rock will work together on msp SPI
   - phil b: will eventually need an implementation for populated telos; 
     they'll do it if not done previously
 - radio (single hop) 
   - cc1000 david
   - cc2420 phil levis
 - storage 
   - mica: david gay
   - sp microchip: arched rock
   - imote2: arched rock
 - hardware id
   - belongs to each platform
 - power management
   - phil: 
     - "power mgt" too broad; should constrain 
       -lower level things and then higher-level policies
       - sleep function based on status, combined w/peripherals' 
         proper support
   - dgay: needs someone to lead design 
     - phil, vlado, kevin 
- security
  - radio stack level
  - phil: not a high priority item for the cc2420; once stack exists and
    is stable, figured he'd add in the security
    - will talk to naveen sastry
 - serial packet-level communication
   - ben: after nsdi deadline will continue work
- sensor boards
   - dgay: propose that they be grouped w/respective platforms
- tossim
  - phil 

Deadlines:
- ben: appropriate deadlines?
- dgay: end of october through end of the year (couple months)
- phil: suggest before end of november; if something bigger, can understand
  if something bigger
- dgay: storage for imote2? 
  - phil: not sure when they'll be made public but there will be 
    internal deadlines


Managing Development 
---------------------------
- dgay: proposal:

Part 1:
- subsystems should have (1) owners and (2) a completion target date
- if subsystem not complete by some approximation of the date, 
  that subsystem can be taken over by someone else preferably 
  after discussion on mailing list 
  - phil b: timeout on mailing list discussion?
  - dgay: let's say a week

Part 2:
- other part: in many cases you want to modify someone else's subsystem;
  there are varying extents of modification
  - bugs -> bigger bugs -> trivial API changes -> rewrite of TEP 
  - handling should scale to degree of modificaiton
    (1) trivial bug: just do them
        (example: if something doesn't compile, just do them)
    (2) substantial, tricky change: maybe send message to
        mailing list and give 48 hours to respond (can check in sooner if
        response is forthcoming)
    (3) TEP changes: discuss on list and get some level of consensus

- Phil: 48 hours is a good idea generally  
- dgay: everyone all right?
  - archedrock: ok, but have some reservation on waiting 48 hours
    in the case of a commit that is important to the community; we
    can work on our own code base here, but the community may suffer
  - tu berlin: ok
- dgay: will write something up next week and folks can okay that

next week
-----------
 - power management
  - please read vlado's email; consider questions
 - figure out next milestones

-------------- next part --------------
_______________________________________________
Tinyos-2.0wg mailing list
Tinyos-2.0wg at Mail.Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-2.0wg