"Examples maintainer" is very generic in my opinion. Examples should be
developed for each component by component developers. It's not separable.
I think your code belongs to the IoTivity Security maintainers group, where
active maintainers are (based on wiki)
Aleksey Volkov, Nathan Heldt-Sheller, Kevin Kane, Greg Zaverucha
Best Regards
Ondrej Tomcik :: KISTLER :: measure, analyze, inovate
From: rami alshafi <[email protected]>
Sent: Donnerstag, 30. August 2018 21:42
To: Tomcik Ondrej <[email protected]>; [email protected]
Subject: Re: Inefficient code reviews
Ondrej,
Thank you for the advice and the assurance I am not alone. I am the original
author of the sample application that I am trying to maintain which is found in
this source path (examples/OCFSecure).
According to this page<https://wiki.iotivity.org/projects_and_functions> there
is no maintainer for the examples. This explains the delay as other maintainers
would need to take on this additional responsibility.
If possible, I would love to be the maintainer for the examples/OCFSecure
sample application so I can maintain it more frequently and efficiently. I read
the project governance and I will need to propose my maintainer candidacy to
the IoTivity Steering Group. There is not a mention of how to contact the ISG.
Will you please advice me on how to contact the ISG?
Thanks,
-Rami
________________________________
From: Ondrej Tomcik <[email protected]>
Sent: Thursday, August 30, 2018 1:16:57 AM
To: Rami Alshafi; [email protected]
Subject: RE: Inefficient code reviews
Hello Rami,
You're not the only one. We had the same issue with the Cloud component.
Solution was to take over the responsibility for component - architect and
maintainer role.
Who is responsible for a component you upstreamed modifications into? I would
write directly them.
Ondrej Tomcik :: KISTLER :: measure, analyze, inovate
From: [email protected] <[email protected]> On
Behalf Of Rami Alshafi
Sent: Donnerstag, 30. August 2018 02:48
To: [email protected]
Subject: [dev] Inefficient code reviews
Devs,
I have extremely simple code review that I submitted 3 weeks ago. It mainly
includes changes in README file, white space modifications (based on previous
code reviews) and fixing a minor issue with the sample app SVR database.
Mats has already reviewed it and we went back and forth over 3 separate
patches. I have e-mailed the IoTivity maintainers list and got no response.
We really need to improve the efficiency of code reviews and merging code in
order to grow the IoTivity developer community.
My last patch took more than 7 months to be reviewed and finally merged!!
Am I alone in this struggle or is this a common problem among developers?
this is the link to the patch https://gerrit.iotivity.org/gerrit/#/c/26733/
Thanks,
-Rami
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#9905):
https://lists.iotivity.org/g/iotivity-dev/message/9905
Mute This Topic: https://lists.iotivity.org/mt/25089084/21656
Group Owner: [email protected]
Unsubscribe: https://lists.iotivity.org/g/iotivity-dev/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
