Jinguk,
I agree with Pat that Sachin will be a good fit as a security sub-maintainer.
Thanks,
-Jaideep


From: iotivity-dev-bounces at lists.iotivity.org 
[mailto:[email protected]] On Behalf Of Lankswert, Patrick
Sent: Tuesday, April 14, 2015 8:42 PM
To: jinguk.jeong at samsung.com; iotivity-dev at lists.iotivity.org
Subject: 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

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++



[cid:image001.gif at 01D0774D.BDCDE980]

[http://ext.samsung.net/mailcheck/SeenTimeChecker?do=d083a0c0528fae5215f55cccbd4dfa28e149768ea3853ad0c02ed1e8db42db2188d6974bd2f79a3cb3b9c254041823979dd130b31b023ef15296970253332b3707805447a154a46fcf878f9a26ce15a0]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150415/c0a50e86/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.gif
Type: image/gif
Size: 13168 bytes
Desc: image001.gif
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150415/c0a50e86/attachment.gif>

Reply via email to