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: iotivity-dev@lists.iotivity.org <iotivity-dev@lists.iotivity.org> On Behalf Of Rami Alshafi Sent: Donnerstag, 30. August 2018 02:48 To: iotivity-dev@lists.iotivity.org 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 (#9903): https://lists.iotivity.org/g/iotivity-dev/message/9903 Mute This Topic: https://lists.iotivity.org/mt/25089084/21656 Group Owner: iotivity-dev+ow...@lists.iotivity.org Unsubscribe: https://lists.iotivity.org/g/iotivity-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
