-
Notifications
You must be signed in to change notification settings - Fork 8
Minutes 18 Jan 2024
Paul Albertella edited this page Feb 15, 2024
·
1 revision
Host: Paul Albertella
Participants: Igor Stoppa, Florian Wuhr, Pete Brink, Luigi Pellecchia
- Igor’s documents
- Basil
-
Igor is going to upload a Markdown version of the content as well
-
Criteria for acceptance of documents?
- Licence is compatible
- Contribution rules for Linux Foundation (link)
- Provenance and attribution of content
-
Basil
- Specification management tool
- Linking a document (that provides some kind of specification) to one or more requirements / assertions / justifications regarding it and associated tests that verify these
- Web application, designed to facilitate collaboration between contributors
- If the linked document is e.g. a source code file, then a change in that file can be detected and trigger review
- Planning to extend to support linking to general documents
-
Pete: Can it define a hierarchy of these e.g. Arch -> Design
- Also tracks versions of work items that are created and managed in Basil (requirements, justifications, tests, etc)
- Can provide it with the URL of the set of source documents and get it to check the spec against it
- Could use Basil to start constructing a set of requirements for the kernel
- And possibly use this to analyse test coverage?
- Nested test cases are not possible, but can have multiple test specifications
Paul: How are changes to the data created by Basil managed?
- e.g. How do you control who can change requirements, tests etc?
- Suggestion: Could OSEP start using Basil as a tool in which to start defining requirements for the kernel?
Next week:
- Discuss review criteria for future revisions to content, and criteria for acceptance of a given version / maturity