# Bi-Weekly dev call

**URL:** <https://forum.opencyphal.org/t/bi-weekly-dev-call/173>\
**Category:** Development & Maintenance\
**Created:** [October 5, 2018, 9:48pm UTC](https://forum.opencyphal.org/t/bi-weekly-dev-call/173 "2018-10-05T21:48:10Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![pavel.kirienko](https://forum.opencyphal.org/user_avatar/forum.opencyphal.org/pavel.kirienko/32/9_2.png) [@pavel.kirienko](https://forum.opencyphal.org/u/pavel.kirienko)\
**Post date:** [November 5, 2018, 7:53pm UTC](https://forum.opencyphal.org/t/bi-weekly-dev-call/173/7 "2018-11-05T19:53:17Z")

</div>

> where are we with the si namespace? How do we close on this?

See my latest comment in the thread: [SI namespace design - #5 by pavel.kirienko](https://forum.opencyphal.org/t/si-namespace-design/207/5). We could use a competing namespace design proposition to compare against my original one.

> The previous si proposal lacked torque. Can we add torque in nm?

By all means.

> Code-compatibility - it’s time to close on this. If my latest proposal isn’t palatable then I’ll go with the BDFL

Will reply in the same thread once more tomorrow: [The case for code compatibility - #4 by pavel.kirienko](https://forum.opencyphal.org/t/the-case-for-code-compatibility/194/4)

> What can I do to close on the v1 standard? I’d really like to get back to work on libuavcan.

I think we agree on all things except the versioning issue. The SI namespace does not seem to affect implementations. I think it should be safe for you to start working on the new implementation already, meanwhile I and Kjetil will finish up the spec – Kjetil will take care of the DSDL chapter, whereas I will update the transport layer and the high-level overview sections in the beginning of the document.

* * *

Kjetil proposed to move the call to 18:30 UTC. It works well for me during the winter, so I am okay with the change for now; when the DST is active it will get difficult though (18:30 UTC is 21:30 EEST, which is rather late). Perhaps we could pick an earlier time instead, or maybe a different day, to avoid rescheduling the call once again in a few months when the DST is active again. Otherwise, 18:30 UTC works as a tentative solution.

---

_[View the full topic](https://forum.opencyphal.org/t/bi-weekly-dev-call/173)._
