@JustinCappos et al.: Would you be open to a (slight) reorg of this repo's content so that it could automatically processed and published via Hugo and the revamped website repo? For context, read on.
As part of the reworked in-toto website (https://github.com/in-toto/in-toto.io/issues/76), the adopters and integrations are now accessible from the site via the Ecosystem section, which you can preview here:
The initial work was done by an LFX mentee last term. She achieved this by simply copying some of the content from this repo. Copying, of course, not ideal since it puts the burden on website maintainers to keep two sets of info in sync. There should be a single canonical source of info for the friends of in-toto. Hence the proposal to reorganize the content a bit in support of auto inclusion on the (revamped) website.
Another alternative would be to simply merge the content of this repo into the website repo. Let me know what you all think.
@JustinCappos et al.: Would you be open to a (slight) reorg of this repo's content so that it could automatically processed and published via Hugo and the revamped website repo? For context, read on.
As part of the reworked in-toto website (https://github.com/in-toto/in-toto.io/issues/76), the adopters and integrations are now accessible from the site via the Ecosystem section, which you can preview here:
The initial work was done by an LFX mentee last term. She achieved this by simply copying some of the content from this repo. Copying, of course, not ideal since it puts the burden on website maintainers to keep two sets of info in sync. There should be a single canonical source of info for the friends of in-toto. Hence the proposal to reorganize the content a bit in support of auto inclusion on the (revamped) website.
Another alternative would be to simply merge the content of this repo into the website repo. Let me know what you all think.
Related: