JinGuk, Thanks.
Pat From: ??? [mailto:[email protected]] Sent: Wednesday, April 15, 2015 12:08 AM To: Lankswert, Patrick; iotivity-dev at lists.iotivity.org Subject: Re: RE: RE: [dev] Maintainer (Security Project) Pat OK, I see. Sachin can continue his work as a sub-maintainer until new security maintainer is selected if jaideep don't have any concern. BR Jinguk Jeong ---?? ???--- ??? : Lankswert, Patrick/patrick.lankswert at intel.com <mailto:Patrick/patrick.lankswert at intel.com> ???? : 2015/04/15 12:41 (GMT+09:00) ?? : RE: RE: [dev] Maintainer (Security Project) JinGuk, I know that I am not the security chair, but I think that Jaideep was intending to name Sachin Agrawal as a security sub-maintainer. Sachin has been working on the security area and the Iotivity implementation for some time. Pat From: JinGuk Jeong [mailto:[email protected]] Sent: Monday, April 13, 2015 9:47 PM To: Lankswert, Patrick; iotivity-dev at lists.iotivity.org <mailto:iotivity-dev at lists.iotivity.org> Subject: Re: RE: [dev] Maintainer (Security Project) Pat, Below process is just for selecting maintainer, not TG chair. As you know, IoTivity is separated with OIC. I think that sub-maintainers continue until the new maintainer is selected. However, as I remember, security sub-maintainers weren't announced yet, even though other project sub-maintainers were announced. So, IoTivity developers don't know who are sub-maintainers of security project. Although we need to discuss with new security maintainer about sub-maintainers, current sub-maintainer can do their job until new maintainer is selected. Jaideep, Could you announce sub-maintainers before stopping your maintainer works? Based on IoTivity governance, the ownership of the sub-maintainer list belongs with the maintainer. BR Jinguk Jeong ------- Original Message ------- Sender : Lankswert, Patrick<patrick.lankswert at intel.com <mailto:patrick.lankswert at intel.com> > Date : 2015-04-13 23:39 (GMT+09:00) Title : RE: [dev] Maintainer (Security Project) <!--[if mso 9]--> Jinguk, Will you also be acting as the Task Group Chair or just the maintainer? Does the governance allow a separation? Why would you not let the sub-maintainers continue as the maintainers until the new Task Group Chair is selected? They are doing the job now and have the history of the work in progess. Pat From: iotivity-dev-bounces at lists.iotivity.org <mailto:iotivity-dev-bounces at lists.iotivity.org> [mailto:[email protected]] On Behalf Of ??? Sent: Sunday, April 12, 2015 8:32 PM To: iotivity-dev at lists.iotivity.org <mailto:iotivity-dev at lists.iotivity.org> Subject: [dev] Maintainer (Security Project) Dear developers, As you may know, Jaideep will no longer be able to serve as a Security Maintainer. So, we should try to search for good candidates in the community. Firstly, If you are willing to be the maintainer of security project, plz let me know. I will discuss with ISG members after searching for candidates. I ask as the lead architect; Are there any candidates? Plz let me know including simple reason. BR Jinguk Jeong ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Jinguk Jeong, Software R&D Center, SAMSUNG ELECTRONICS CO., LTD Email : jinguk.jeong at samsung.com <mailto:jinguk.jeong at samsung.com> 010-3244-4110 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Jinguk Jeong, Software R&D Center, SAMSUNG ELECTRONICS CO., LTD Email : jinguk.jeong at samsung.com <mailto:jinguk.jeong at samsung.com> 010-3244-4110 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ <http://www.samsung.net/pt_images/C10/securityimage/MSI_20140516060336843.gif> <http://ext.samsung.net/mailcheck/SeenTimeChecker?do=d083a0c0528fae5215f55cccbd4dfa28e149768ea3853ad0c02ed1e8db42db2188d6974bd2f79a3cb3b9c254041823979dd130b31b023ef15296970253332b3707805447a154a46fcf878f9a26ce15a0> <http://ext.samsung.net/mailcheck/SeenTimeChecker?do=d083a0c0528fae525bc8e28272fa9f18cd77e75492ab13c0294a76bc6a3cc8413488ff5bbdf1525fd3d52e3ddee9306ded04226648eb720dce7100ee954f3d131b20909a04efd4d2748cfe1d4e847419cf878f9a26ce15a0> -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150415/529e57a3/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 7198 bytes Desc: not available URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150415/529e57a3/attachment.p7s>
