[Tinyos-devel] Retiring tinyos-2_0_devel-BRANCH

[Philip Levis]

On Dec 15, 2006, at 12:50 AM, Joe Polastre wrote:

> Phil,
>
>  You said that no one (except you and Vlado) have permission to
> modify the HEAD.  Will this continue to be true?
>

No. All of the people who had access to -devel now have access to HEAD.


>  I personally think that an approach like SVN where you can have a
> devel branch that is easily merged with the HEAD is the optimum
> solution given the current tools.  Access control is a red herring,
> and contribution should be key.

Contribution is easy; maintenance is hard. The main purpose of access  
controls it to prevent inadvertent checkins. The most common place  
you see this, in fact, is on branches. The core group had a lot of  
headaches generating the 2.0 RPM because fixes were spread  
(inadvertently) through HEAD, -devel, and -release. Given that TinyOS  
is a component system, people often tweak components for debugging or  
testing.

>
>  Given such considerations, I noticed that contrib does not require a
> specific license for the contrib/ contributions.  I assume this is on
> purpose to allow contributions under any license to be submitted to
> the TinyOS contrib source tree to foster greater collaboration and
> contributions.

Good point. I think we missed that one. I believe the current status  
is that the two current alliance-supported licenses are the BSD  
license[1] and the academic license[2]. 120 states the policy for  
adding new licenses to the pool. I'll check with the alliance WG.

Phil

[1] Starts with "Redistribution and use in source and binary forms,  
with or without", e.g. tos/interfaces/Pool.nc

[2] Starts with "Permission to use, copy, modify, and distribute this  
software..", e.g., tos/interfaces/Leds.nc