# Splitting the Autoware.AI repository and changing the organisation

**URL:** <https://discourse.openrobotics.org/t/splitting-the-autoware-ai-repository-and-changing-the-organisation/8139>\
**Category:** Autoware\
**Created:** [March 5, 2019, 7:59am UTC](https://discourse.openrobotics.org/t/splitting-the-autoware-ai-repository-and-changing-the-organisation/8139 "2019-03-05T07:59:36Z")\
**Posts on this page:** 1\
**Showing post:** 19

<div class="post-metadata">

**Author:** ![esteve](https://sea2.discourse-cdn.com/flex022/user_avatar/discourse.openrobotics.org/esteve/32/12_2.png) [@esteve](https://discourse.openrobotics.org/u/esteve)\
**Post date:** [March 8, 2019, 12:32pm UTC](https://discourse.openrobotics.org/t/splitting-the-autoware-ai-repository-and-changing-the-organisation/8139/19 "2019-03-08T12:32:50Z")

</div>

> [@gbiggs](#):
>
> I personally am leaning in the direction of having a separate repository for messages, but I can see the argument against adding another repository.

I think having a separate repository for messages would definitely help here. Having the interface (messages) separate from the behavior (nodes) tends to be a good pattern for loosely coupled architectures.

---

_[View the full topic](https://discourse.openrobotics.org/t/splitting-the-autoware-ai-repository-and-changing-the-organisation/8139)._