Margaret,
Thanks for making this happen.
As the Android/Java maintainer, I think that would be excellent idea where we 
get together and drive issues, discuss features, discuss workload, releases, 
testing and etc.
I had always thought this was part OSWG instead of separate TSC.

Thanks,
-Rick

From: iotivity-dev@lists.iotivity.org [mailto:iotivity-dev@lists.iotivity.org] 
On Behalf Of Margaret LaBrecque
Sent: Monday, June 11, 2018 1:43 PM
To: Nash, George <george.n...@intel.com>; iotivity-dev@lists.iotivity.org; Aja 
Murray <amur...@vtmgroup.com>
Cc: seokhee....@lge.com; jihyeok13....@samsung.com; Ondrej Tomcik 
<ondrej.tom...@kistler.com>; Heldt-Sheller, Nathan 
<nathan.heldt-shel...@intel.com>; Macieira, Thiago <thiago.macie...@intel.com>
Subject: Re: [dev] What is the process for appointing new project 
maintainers/sub-maintainers

Hi George,

Thanks for detailing the current situation so thoroughly.  I believe the 
IoTivity Steering Group (ISG - 
i...@lists.iotivity.org<mailto:i...@lists.iotivity.org>) currently approves new 
maintainers and indeed, has already approved Seokhee Lee from LG.

hi Aja - would you sync offline w George to make sure the above change is made 
in the places it needs to be made?

I can send an email to the ISG regarding Ondrej Tomcik as the new maintainer of 
IoTivity Cloud and also suggest two new sub-maintainers Peter Rafaj and Jozef 
Kralik (not sure sub-maintainers need to be approved per se.)

It has been Thiago's (Community Manager) desire that maintainers form a TSC 
along with any functional leads (e.g., QA lead) and that the TSC be empowered 
to make these types of decisions moving forward ... thus rendering the ISG's 
role to be more focused on project administration.  Perhaps we can pursue that 
path once Ondrej is approved,

Margaret

From: iotivity-dev@lists.iotivity.org<mailto:iotivity-dev@lists.iotivity.org> 
<iotivity-dev@lists.iotivity.org<mailto:iotivity-dev@lists.iotivity.org>> On 
Behalf Of George Nash
Sent: Monday, June 11, 2018 1:32 PM
To: iotivity-dev@lists.iotivity.org<mailto:iotivity-dev@lists.iotivity.org>
Cc: seokhee....@lge.com<mailto:seokhee....@lge.com>; 
jihyeok13....@samsung.com<mailto:jihyeok13....@samsung.com>; Ondrej Tomcik 
<ondrej.tom...@kistler.com<mailto:ondrej.tom...@kistler.com>>
Subject: [dev] What is the process for appointing new project 
maintainers/sub-maintainers

In the last few weeks we have had multiple requires to update/change a 
maintainers role.

It is unclear to me what is the process for updating or changing a maintainers 
role.

There does not seem to be a process in place. I could not find one listed here: 
https://wiki.iotivity.org/doku.php?id=projects_and_functions

We have had a request to update the roles for two projects: Platform Support 
and IoTivity Cloud.

The wiki lists the following for each role.

Platform Support

Architect: Dan Mihai
Maintainer: Dan Mihai
Sub-Maintainers: Dan Mihai (Windows), Rick 
Bell<mailto:richard.s.b...@intel.com> (Android), Phil Coval (Tizen, Ubuntu)
Gerrit Code Review Group: 'Platform Maintainers'

The Platform Support<https://wiki.iotivity.org/platform_support> Project is 
responsible for all platform-specific support including Windows/Android/iOS and 
so on. The maintainer sets guidelines and organizes the framework, and each 
specific platform can have a sub-maintainer to handle details specific to that 
platform.

IoTivity Cloud

Architect: (vacant)
Maintainer: JeeHyeok Kim
Sub-Maintainer: Ziran Sun, Habib Virji

The IoTivity Cloud<https://wiki.iotivity.org/iotivity_cloud> Project is 
responsible for extending accessibility of IoTivity devices and scenarios using 
some techniques like Http to CoAP proxy, OAuth 2 over CoAP and so on. Users can 
access their devices under their prefer accounts through cloud. Also when user 
share credential to other services, they can access to user devices for 
automated control.

We already know that Dan Mihai has left the IoTivity project. We have the email 
from him saying that he is unable to fulfill that role so the wiki really 
should be updated to read that Architect: (vacant), Maintainer: (vacant) also 
the sub-maintainer for windows should also be (vacant).

We really do need a new maintainer for Platform Support. The WebOS commit has 
been stuck in review for weeks due to not having a maintainer. LG has nominated 
Seokhee Lee to the position of Platform maintainer and I believe he has agreed 
to accept the position.

The IoTivity Cloud project is a little different there does not appear to be 
any feedback from any of the current maintainers or sub-maintainers. I did a 
search through several projects and I have not seen any feedback from any of 
the current listed maintainers for at least the last 3 months. Including a long 
discussion on this email list about the Cloud.

There has been some discussion whether "Cloud" is the correct phrase for the 
project function.  Regardless of the name of the project it is clear we need a 
solution that will enable IoTivity/OCF to reach beyond the local subnet. From 
what I have gathered the current maintainers have not been able to reach the 
needs of developers using IoTivity Cloud and for that reason Ondrej Tomcik has 
requested to be a new maintainer and he has suggested two new sub-maintainers 
Peter Rafaj and Jozef Kralik.

I don't want to lose potential community members just because we have done a 
poor job maintaining clear leadership for IoTivity.

Does anyone know the process for appointing/changing new project 
maintainers/sub-maintainers?

George Nash


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#9696): 
https://lists.iotivity.org/g/iotivity-dev/message/9696
Mute This Topic: https://lists.iotivity.org/mt/21995760/21656
Group Owner: iotivity-dev+ow...@lists.iotivity.org
Unsubscribe: https://lists.iotivity.org/g/iotivity-dev/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to