[Tinyos-devel] TEP 4 Shepherding

[Omprakash Gnawali]

Quick status update: The current contrib manager thinks it would
require a lot of resource to enforce proper AM ID use for contrib
because once the contributors have access to the CVS they are free to
change their software as they wish.

I just toggled the "final" bit on the TEP.

Thanks everyone for your feedback and Ben for shepherding.

- om_p

On Thu, Oct 23, 2008 at 5:30 PM, Omprakash Gnawali <gnawali at usc.edu> wrote:
> Thanks for your comments, Ben. I am addressing two points you raised.
>
>> lines 58-59: "The AM ID may conflict with the protocols and
>> applications in the contrib tree." I'd say iff the contrib protool is
>> intended to replace the TinyOS protocol. I think the language is weird
>> in that an arbitrary contrib protocol can conflict with a blessed
>> TinyOS protocol.
>
> The concern is admission control on the contrib tree might become
> resource intensive. My understanding is we want it to be as easy as
> possible to put code on contrib. If contrib manager and the community
> is interested in making sure these conflicts do not happen, I would be
> happy to update the TEP before finalizing.
>
>> lines 91-92: "The chair of the Network Protocol Working Group will
>> document the deallocation." I'd also say the chair has the right to do
>> the equivalent of requiring lease renewals, if the ID space gets
>> tight.
>
> If this happens, I think someone needs to do something to reclaim some
> IDs. Yours would be one approach. We don't anticipate this to be a
> problem in the next 1-2 yrs so it is probably better to defer this
> discussion.
>
> - om_p
>