Closed mnm678 closed 1 month ago
Is there an advantage over maintaining this in https://theupdateframework.io/adoptions/?
IMO this repo here should primarily serve as umbrella for the TUF core- and subprojects under github.com/theupdateframework
. See e.g. PROJECTS.md
plus proposed classification from our original community repo draft.
Is there an advantage over maintaining this in https://theupdateframework.io/adoptions/?
Hm. It probably does lower the barrier for outside collaborators to add a new adoption via PR.
Either way maybe we could add a CONTRIBUTING.md
file[^1], which explains how to inform the community about a new adoption.
[^1]: See existing ideas for CONTRIBUTING.md
in our original community repo draft. :P
Hi @lukpueh what are your suggestions, should we add CONTRIBUTING.md
in Community
repo? And this content as you suggested looks good to add. If you like, I want to work on this.
Hi @lukpueh @mnm678 @joshuagl any thoughts on adding contributing.md?
Feel free to open a pr. You can start with the content from the draft repo, and possibly add a description of how adoptions can add themselves to https://theupdateframework.io/adoptions/
Sure, I will raise PR, asap! /assign
@mnm678 @JustinCappos can we close this now.
Fixed in https://github.com/theupdateframework/community/pull/18/files, which adds instructions to this repo, about how to document a new adoption on theupdateframework.io
We can have a list of companies/organizations that have adopted TUF to allow interested parties to see who else has adopted the project.