[Tinyos Core WG] Re: non-TEP code

[Kevin Klues]

When we were setting up the guidelines for tinyos 2.0 contrib I sent out an
email to tinyos-devel requesting everyone's feedback on the process.  Much
of the way it has now been set up is based on the feedback that you
provided.  What limitations do you still see that hinder you from being able
to contribute code and how do you think they might be resolved?  The process
is never completely set in stone and can be constantly updated based on any
feedback that is given.

Kevin

On 1/30/07, Joe Polastre <joe at polastre.com> 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?
>
> 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)...
>
> -Joe
> _______________________________________________
> 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
>



-- 
~Kevin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.millennium.berkeley.edu/pipermail/tinyos-2.0wg/attachments/20070130/2a8858ef/attachment.html