[Tinyos-devel] Problems with tinyos-1.x vs. 2.x

[John Griessen]

Kevin Klues wrote:

> I think one problem with all of these issues that seem to come up in
> tinyos-1.x is that no one is really maintaining that tree much anymore.

I'm sure there have been lots of
> commits to the (T1) contrib tree, but this code tends to be even less documented
, and some users don't even know that it exists.

> My solution to all this would be to try and convince everyone to switch over
> to tinyos-2.x,

[jg]When I first saw tinyos, There were 3 obvious paths: Go with Boomerang,
T1 or T2.  T2 had the active group of free open coded developers, so I chose that.
There was the implication that T1 code would get ported to T2.

   So whats the right answer here?

[jg]I for one can't see hiring out to port code until it is a match with
customer wants or a product I see making.  I think having two code trees that are
different conceptually is no help to any system customers of mine or future ones.
I'll only promote to find people to use T2.  So I vote promote T2 to new users,
and keep in mind ways to fund porting.

I have not read through a catalog of T1 code even.  Does one exist with app titles and purpose listed?
If so, it would be a good wiki page to do list we could point to and check things off of.
Also we could rate codes that seem valuable, and that would help get coders to
consider porting them.

What position does Crossbow take on T2?  T1 contrib commits by them seem to average 3 yaears old.
I didn't see any mention of it T2 xbow.com.
Moteworks is not free as in open...so not what my researcher customers want.
"MoteWorks is available for free use and distribution for academic, research,
personnel, evaluation, or non-profit use."

We should steer new users to T2.

John Griessen
-- 
Ecosensory   Austin TX
tinyOS devel on:  ubuntu Linux;   tinyOS v2.0.2;   telosb ecosens1