[Tinyos-devel] Re: [Tinyos Core WG] Re: non-TEP code

[Philip Levis]

On Jan 29, 2007, at 11:42 PM, Joe Polastre wrote:

>> You are right that non-TEP code currently can not be directly  
>> accepted into
>> the core. But TinyOS 2.0 contrib has been open for some time, and  
>> it seems
>> to be the best option for hosting code until the TEP  
>> standardisation for the
>> button interfaces is finished. The process of contributing code is  
>> described
>> at www.tinyos.net/Developers/Contributing Code. The direct
>> link is:
>> http://tinyos.cvs.sourceforge.net/*checkout*/tinyos/tinyos-2.x- 
>> contrib/contrib.html
>
> A button is one of the simplest interfaces available.  If it takes
> over 2 months to get a button interface through the bureaucratic
> system, how long does it take for an interface with complexity?
>

I think it depends how many people work on it. After the initial  
flurry of emails, no-one (including you) followed up on the issue, so  
it moved to the back burner.

> TinyOS 2.0 contrib, on a separate note, has license restrictions and
> process controls that make it unappealing to corporate users (and was
> designed without input from corporate users)...

IIRC, the last discussion on contrib licenses was "mostly OSI  
licenses." That is, you can pick from almost any of the standard OSI  
licenses. The "almost any" is mostly because of GPL. Due to the fact  
that TinyOS doesn't have linking, the GPL makes things tricky and so  
is out. The consensus came to this due to the problems of trying to  
agree on what "open source" is. Rather than have the contrib  
caretakers go down that rathole (and find they didn't read a piece of  
legal fine print), the conclusion was to just take the OSI's word for  
it.

Phil