[Tinyos-alliance] TEP 120

[Philip Levis]

On Feb 10, 2007, at 8:16 AM, stankovic at cs.virginia.edu wrote:

>
> Sect 4.1   "regular Allinace meetings."  should we say something  
> about the
>                   expected frequency  - once per year?
>
>      do we want to say what a small versus large company is?
>
>     the steering committe will be engaged in ratification   
> standards...how?
>                should we say something about this here?
>
> sect 7
>
>      there will be a mechanism for contributing IP .... what is that
>            mechanism; is it described sect 8?  or elsewhere
>
>   the Alliance will have a preferred source license ... where? when?

These are the questions Jack raised when reviewing TEP 120. I think  
they are all good questions. Among other things, they deal with  
questions which were less clear when we started writing the document  
but which have solidified a bit since.

That being said, some of them will by necessity evolve, and so we  
probably don't want to spell out the answers in TEP 120. Rather, we  
can provide references to the tinyos.net website. In particular:

> Sect 4.1   "regular Allinace meetings."  should we say something  
> about the
>                   expected frequency  - once per year?

I think we should state this part clearly in 120. Right now the  
expected frequency is at least once a year (TTX), with other meetings  
as needed (e.g., the net2 workshops). Saying that it's at least once  
a year and may become more often gives us the space to grow.

>
>      do we want to say what a small versus large company is?
>

Saying this clearly in 120 would be good, with the caveat that it may  
change.


>     the steering committe will be engaged in ratification   
> standards...how?
>                should we say something about this here?
>

This is a tough one -- TEP 123 is our first "standard" and net2 is  
still talking with Sun about it. I suggest that we leave this one  
vague and let it evolve.

> sect 7
>
>      there will be a mechanism for contributing IP .... what is that
>            mechanism; is it described sect 8?  or elsewhere

I think that we need to spell this one out more clearly. A company or  
research group reading the document should have a clear sense of what  
this is.


>
>   the Alliance will have a preferred source license ... where? when?

I think that we should leave this as a reference to tinyos.net.  
Currently, it's BSD/Academic for the core, and a subset of the OSI  
licenses for contrib. The contrib caretakers should maintain a list  
of the approved OSI licenses.

Phil