Best practice of posting a board integration with a vendor fork

General Discussions
1

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?

2

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. :slight_smile:

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