[Tinyos Core WG] Re: non-TEP code

[Joe Polastre]

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.

Best,
-Joe

On 11/27/06, Joe Polastre <joe at polastre.com> wrote:
> The question arose "where is the user button interface in T2?".  For
> code that could be committed but has no TEP, what is the policy?
> Similarly, do we need to work on a "button" TEP (sounds like
> overkill)?
>
> -Joe
>