Dan I will add this to the agenda for next week's WG call. From: Daniel Mihai [mailto:[email protected]] Sent: Thursday, February 11, 2016 12:17 PM To: Lioy, Marcello; [email protected]; Dominique Chanet (QEO LLC); Josh Spain; [email protected]; [email protected] Cc: Arvind Padole Subject: proposal to move the core/securitymgr source code into core/alljoyn
Hi Core WG folks, I propose moving the core/securitymgr source code into the core/alljoyn project - becoming Core sample source code. Main reasons: 1. App developers using the SCL need a Security Manager to test the Security 2.0 behavior of their app. So, *everyone* who's a user of core/alljoyn should always be a user of securitymgr too - at least until commercial Security Managers will become available. 2. It is not uncommon to break the securitymgr behavior when we change the core/alljoyn behavior. We should run the securitymgr tests when we change the SCL, and make sure these tests are still passing. 3. Theoretically, at some point the Alliance might decide to make (some of) the securitymgr code part of the SCL. (I am not aware of such a need at this point) Please speak up with any thoughts or questions related to this proposal. Thanks, Dan
_______________________________________________ Allseen-core mailing list [email protected] https://lists.allseenalliance.org/mailman/listinfo/allseen-core
