-
Notifications
You must be signed in to change notification settings - Fork 36
Tooling Landscape Weekly Meeting Notes
Lars Geyer-Blaumeiser edited this page Sep 13, 2018
·
4 revisions
Sandro, Michael P., Michael J., Lars
- Presentation about compliance envelope: https://events.static.linuxfound.org/sites/events/files/slides/%28FINAL%29Mr.%20Mark%20Gisi.pdf
- FOSS bundle generator: Think about a more appropriate name and document it in the Pull Request. Compliance Envelop?
- Change Example for internal Artifact Repository to https://archiva.apache.org/index.cgi
- Add open/non commercial examples where possible
- Remove ECCN classifications form glossary
- Rename Component Clearing to Component Analysis Service
- Add License Scanner as component used by Component Analysis Service
- No interfaces in the component diagram
- Make a picture of the company own infrastructure
Lars, Sandro, Michael P, Hanna
- @Lars: Update glossary as discussed in meeting (based on Michael J's review)
- @Michael P: Update diagram
- @everyone: Prepare next meeting by locating tools in the diagram
We (Michael J and Hanna) looked at Lars' PR and requested some changes.
- @Hanna: incorporate pull request review of Lars' changes
- @Michael J: change titles in diagram to reflect glossary
- Meeting notes in public space (Wiki in Github)
- Sequence diagrams can be for concrete tools and also be generic (needs to be discussed) ** Always needed: Disclosure Document (OS Legal Notice, OSS Readme)
- In copy of component diagram tools will be marked via coloured labels at the components
- @Hanna: Move meeting notes to wiki
- @Hanna: Create pull request for Lars' changes
- @Michael P: Reviews Lars' changes
- @Michael J: Adds changes to diagram (titles)
- We use PlantUML. Useful web editor: https://www.planttext.com/
- Commits always as Pull Request
- We need management suitable diagrams as well -> Overview Model
- Component labels need to be clearer (Tool, Datastore, Data, Service, etc.)
- Component diagram as general view of the components. Can be refined to the individual tools (also with additional diagrams like sequence diagrams)
- @Lars: Sharpen terms in glossary
- @Hanna: Schedule meeting 1x week for updates (Thu 14:30)
- @Michael J: Component Diagram in PlantUML