Open jacobdjwilson opened 1 year ago
Important code is:
sequenceDiagram
Incoming Open Source->>+ Outgoing Open Source and Mods: Identification
Incoming Open Source->>+ Outgoing Open Source and Mods: Audit
Incoming Open Source->>+ Outgoing Open Source and Mods: Resolve Issues
Incoming Open Source->>+ Outgoing Open Source and Mods: Reviews
Incoming Open Source->>+ Outgoing Open Source and Mods: Approvals
Incoming Open Source->>+ Outgoing Open Source and Mods: Registration
Incoming Open Source->>+ Outgoing Open Source and Mods: Notices
Incoming Open Source->>+ Outgoing Open Source and Mods: Verifications
Incoming Open Source->>+ Outgoing Open Source and Mods: Distribution
Incoming Open Source->>+ Outgoing Open Source and Mods: Verifications
Closing this pull request and committing the code via GitHub Desktop to get around the conflict. Elegant? No. Work? Yes.
INSANELY COOL DIAGRAM! @jacobdjwilson can you brief the list on how to do this amazing stuff?
Yep, I briefly discussed this on the mailing list with Alberto in the thread "OpenChain Reference Training Slides now in MarkDown (Draft, needs work)"
This diagram was created using Mermaid and the source code can be found here in the live editor tool. This works natively with MarkDown within GitHub and should allow us to convert everything to a editable format such that we can perform PRs on specifics within a graph. For example if someone wants to suggest expanding Audit to include multiple phases such as Security and License they could make a recommendation directly inline with the MarkDown content and it would update the diagram live .The trade off is a lack of rich format ie. colors, complex shapes, etc.
As noted here with your larger contribution on this topic, merging with mainline.
What do you think about the potential to lead a review of the reference training slides to replace all the diagrams with this method?
Slide 54 "Identify and Track Open Source Usage" diagram implemented as Mermaid Chart - Sequence Diagram