People have been using ORT for doing curations for a long time, and in the process have gathered valuable information and licensing details for packages. This information is usually stored locally and/or in repos, as package configuration directories with source_artifact.yml / vsc.yml files in them, specifying the license conclusions and path exclusions made.
This RFC is for discussing the need for building a tool with which the said curation information could be imported to DOS, using the DOS API / or the curation UI.
Questions to be answered:
- Do you see if there would be a need for such a tool?
- How would the tool be built? As an ORT plugin (without a UI), or a simple "directory importer" at curation UI? Both are possible, and both have their benefits and drawbacks I think
- Would the existence of such a tool tempt new users to start using DOS?
From SyncLinear.com | DO-274
People have been using ORT for doing curations for a long time, and in the process have gathered valuable information and licensing details for packages. This information is usually stored locally and/or in repos, as package configuration directories with source_artifact.yml / vsc.yml files in them, specifying the license conclusions and path exclusions made.
This RFC is for discussing the need for building a tool with which the said curation information could be imported to DOS, using the DOS API / or the curation UI.
Questions to be answered:
From SyncLinear.com | DO-274