Hi IoTivity Dev Community,

 

Few initial thoughts "We need a 3rd party library acceptance criteria" -

 

-          Well documented in English. ?

-          Maximum permissive license. ? Needs level or specific options
that community prefer.

-          Security consideration? Needs more specific information.

 

Additions / Modifications are most welcome.

 

Since IoTivity is growing, this checklist getting ready earlier will help
contributors to decide right direction and avoiding any inconvenience.

 

Regards

Dwarka

----------------------------------------------------------------------------
------

Software R&D Center | Software Strategy Team | Open Source Group

Open Connectivity Foundation (OCF) | Iotivity | Javascript Foundation (JSF)

 

From: iotivity-dev-boun...@lists.iotivity.org
[mailto:iotivity-dev-boun...@lists.iotivity.org] On Behalf Of Macieira,
Thiago
Sent: Saturday, August 19, 2017 12:48 AM
To: iotivity-dev@lists.iotivity.org
Subject: [dev] Notes from the ISG meeting 2017-08-17

 

*         Approved buildsystem maintainer - Mats Wichmann

*         Approved API function leader - Dave Thaler

*         Approved Platform Support maintainer - Dan Mihai

*         Governance proposal seems stuck - we should consider simplifying
instead

*       Reviewed contracted QA proposals 

*       Recommendation to keep at current levels to avoid further delays

 

Other reminders:

*         We need a 3rd party library acceptance criteria

*         Need a procedure to handle security notifications 

_______________________________________________
iotivity-dev mailing list
iotivity-dev@lists.iotivity.org
https://lists.iotivity.org/mailman/listinfo/iotivity-dev

Reply via email to