Hello OSWG, IoTivity-dev and OSWG Security TG,

As many of you know, being a volunteer project, we've been short-handed on 
developers, and struggling to find resources for several Security features.   
I've been asking for months for additional help with a few features, but being 
unable to find volunteers, I have picked up implementation of these myself.

However just after returning from the Amsterdam F2F, I learned that one of our 
key development resources was moving on to another job.  I'm not able to pick 
up this slack, since I'm already overloaded.   And because of the 
inter-dependent nature of these features, although myself and others have 
tried, it has been infeasible to cut out any additional CRs from the Security 
Spec... to do so would be more work than just implementing what we have (not to 
mention significant normative CRs).

The good news is that just today I've gotten some temporary resource commitment 
from inside Intel, to pick up these newly-ownerless tasks.  However I think 
because of the time lost over the past few weeks, and spin-up required, it 
would greatly increase our odds of success to have another week of development 
time before creating the 1.3-rel branch.  Moreover, at the last OSWG Security 
TG meeting, I believe Dongik Lee mentioned that their team would like a little 
more time (if possible) to implement a couple additional items they're working 
on.

TLDR; if there is not a hard-stop reason why we need to branch next Friday 
April 7th, I propose we take an additional work-week (plus the weekend for 
those of us who need to work through it) and create the 1.3-rel branch on 
Monday April 17th.

Uze, I think the decision is yours ultimately, but I'm sending to the entire 
list to gather feedback in case there are folks counting on this April 7th date 
for a reason we're not aware of.

Thanks,
Nathan Heldt-Sheller
OSWG Security TG Chair

-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170330/79b49034/attachment.html>

Reply via email to