[Tinyos-devel] Re: [Tinyos Core WG] Re: non-TEP code
Kevin Klues
klueska at gmail.com
Tue Jan 30 00:18:17 PST 2007
One way to resolve the licensing issue might be to allow outside projects to
be included in the contrib index even if their code is not officially
considered part of tinyos contrib and is not being hosted on sourceforge.
These projects could be hosted by whoever, wherever they wanted (and under
whatever license they wanted), but their existence would be made easily
known by keeping a reference to them in the index among all of the other
projects. Is this something that would sound reasonable to the alliance?
Kevin
On 1/30/07, Philip Levis <pal at cs.stanford.edu> wrote:
>
> 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
> _______________________________________________
> 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-devel/attachments/20070130/e8994afa/attachment.html
More information about the Tinyos-devel
mailing list