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

[Vlado Handziski]

On 1/30/07, Joe Polastre <joe at polastre.com> wrote:
>
> On November 27 2006, two months ago, I wrote an email asking how to
> get a button driver committed to T2.
>
> Since this time, there has been a flurry of emails that have discussed
> philosophy, but not real action.
>
> At this time, I am forced to conclude that there will be no resolution
> on this issue.  Therefore, it is up to third party vendors (such as
> Moteiv and Crossbow) to provide drivers for our systems since the
> TinyOS community is incapable of accepting outside contributions for
> necessary functionality.
>
> It is unfortunate that the TinyOS distribution is not able to meet the
> needs of developers, especially with simple functionality like user
> buttons, the sensornet protocol, and low power radio stacks.  If, in
> the future, the TinyOS czar(s) are interested in including
> functionality like this, we'd be willing to share these libraries with
> the community under an open license.



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

Vlado
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.millennium.berkeley.edu/pipermail/tinyos-devel/attachments/20070130/fa18c433/attachment.htm