-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
operations.md added #959
base: profile-operations
Are you sure you want to change the base?
operations.md added #959
Conversation
Signed-off-by: Ummo Schwarting <[email protected]>
Signed-off-by: Ummo Schwarting <[email protected]>
Profile operations, merge current discussion state as of 24-09-27 Merged after Operations profile meeting
as base for discussion Signed-off-by: Marcel Kurzmann <[email protected]>
Signed-off-by: Marcel Kurzmann <[email protected]>
|
||
## Summary | ||
|
||
The Operations Profile defines fields for describing the business context of the software that cannot (or not yet) directly extracted from the source repository. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The Operations Profile defines fields for describing the business context of the software that cannot (or not yet) directly extracted from the source repository. | |
The Operations Profile defines fields for describing the business context of the software that cannot (or not yet) be directly extracted from the source repository. |
|
||
The intention of the Operations Profile is to provide a common base rather for alignment of tool and infrastructure interfaces and development than for exchanging the data between organizations along the software supply chain. The managed information is expected to be mainly kept within the organizations but in some cases might also be necessary input for processing and determining relevant parameters for the later exchange in the supply chain (e.g. Export Control Classification Number). | ||
|
||
The information about Applications shall describe facts about the distribution and business context of a product brought into the market, that could consist of several deliverables. There relation between Application and Deliverable can be 1:n. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The information about Applications shall describe facts about the distribution and business context of a product brought into the market, that could consist of several deliverables. There relation between Application and Deliverable can be 1:n. | |
The information about Element shall describe facts about the distribution and business context of a product brought into the market, that could consist of several deliverables. The relation between Element and Deliverable targets can be one to many. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Applications could be Products, Projects, Packages, etc. so probably best to stick with Element term which could be any of these.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good starting point. Couple of comments.
2a71c84
to
5640f99
Compare
A bunch of type mismatch errors:
|
Signed-off-by: Marcel Kurzmann <[email protected]>
Signed-off-by: Marcel Kurzmann <[email protected]>
Signed-off-by: Marcel Kurzmann <[email protected]>
Signed-off-by: Marcel Kurzmann <[email protected]>
Signed-off-by: Marcel Kurzmann <[email protected]>
…cription Signed-off-by: Marcel Kurzmann <[email protected]>
as discussed in #897