# Best practice of posting a board integration with a vendor fork

**URL:** <https://hub.mender.io/t/best-practice-of-posting-a-board-integration-with-a-vendor-fork/7729>\
**Category:** General Discussions\
**Created:** [April 16, 2025, 12:38pm UTC](https://hub.mender.io/t/best-practice-of-posting-a-board-integration-with-a-vendor-fork/7729 "2025-04-16T12:38:17Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mabembedded](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/mabembedded/32/2379_2.png) [@mabembedded](https://hub.mender.io/u/mabembedded)\
**Post date:** [April 16, 2025, 12:38pm UTC](https://hub.mender.io/t/best-practice-of-posting-a-board-integration-with-a-vendor-fork/7729/1 "2025-04-16T12:38:17Z")

</div>

Hi,

I’d like to post a board integration guide for a Digi Connect Core 6N module. However, I needed to make changes to Digi’s `meta-digi` layer and created a fork to maintain these changes. Should I reference my own repo manifest, which contains my fork of the layer, in the board integration guide?

---

<div class="post-metadata">

**Author:** ![TheYoctoJester](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/theyoctojester/32/1444_2.png) [@TheYoctoJester](https://hub.mender.io/u/TheYoctoJester)\
**Post date:** [April 16, 2025, 1:29pm UTC](https://hub.mender.io/t/best-practice-of-posting-a-board-integration-with-a-vendor-fork/7729/2 "2025-04-16T13:29:53Z")

</div>

Hi @mabembedded,

Thanks for sharing! There’s no die-hard rules here, the core requirement is that it should be reproducible for future users. So in a nutshell, use good judgment. 🙂

Generally I would say it depends on the kind and scope of modifications to `meta-digi` which are required. Can it be done through appends? Then the most straightforward way is to create something like `meta-mender-digi` in `meta-mender-community` which just holds that.

If the current state of things is already visible somewhere, I can also take a look.

Greetz,  
Josef