Hi There is also a copy on Github: https://github.com/iotivity/iotivity/ The last update there was also 3 weeks ago.
*Actually, what is the overhead of maintaining the Github copy up-to-date state?* Github copy may not be very useful for the code maintainers. However, I do think it adds values for the* developers using **IoTivity SDKs* who build and use the library. >From my experience, it's much easier to grasp "what's going on" - branches, tags, what was fixed when etc. - from Github, comparing to the Gerrit repository. Gerrit is a code review system. It adds complexity not really relevant for developers who just want to learn and use the SDK. Regards Max. On Thu, Jul 13, 2017 at 1:19 AM, Morrow, Joseph L <[email protected] > wrote: > +IoTivity Infrastructure mailing list. > > From: <[email protected]> on behalf of Joseph L > Morrow <[email protected]> > Date: Wednesday, July 12, 2017 at 3:17 PM > To: "[email protected]" <[email protected]>, " > [email protected]" <iotivity-infrastructure@ > lists.iotivity.org> > Subject: [dev] git.iotivity.org???? > > Hi All, > > There appears to be a stale version of the IoTivity repo hosted at > git.iotivity.org/iotivity. Not to be confused with the real version > gerrit.iotivity.org/gerrit/iotivity. > > Can we either get this stale version to not be stale or get rid of this > duplicate and stale repo? > > Notice: It’s 3 weeks stale. (At least on the 1.3-rel branch.) > > Thanks, > > Joey Morrow > > _______________________________________________ > iotivity-dev mailing list > [email protected] > https://lists.iotivity.org/mailman/listinfo/iotivity-dev > >
_______________________________________________ iotivity-dev mailing list [email protected] https://lists.iotivity.org/mailman/listinfo/iotivity-dev
