Skip to content

Minutes 30 Nov 2023

Jump to bottom
Paul Albertella edited this page Nov 30, 2023 · 2 revisions
  • Host: Paul Albertella
  • Participants: Igor Stoppa, Gab Paoloni, Daniel Krippner

Agenda:

  • 'Checklist of known issues' initiative
    • Update from Igor on status of his document
  • 'Next Steps' from Munich Workshop [1]
    • Agree actions for OSEP & add issues in GitHub [2] regarding
        1. Establish document review & publication workflow
        1. Build index of past ELISA results
        1. Basil requirements tool
  • Vice-chair for OSEP?
    • Suggested new role for all ELISA WGs
    • Act as proxy for WG chair when unavailable (e.g. run meeting)
  • 'Proven in use' PR from Sebastian [3]
    • Review status

Igor’s document

  • Hoping to have complete and approved for publication by end of year
  • Question: where could we place it?
    • Hope to publish it as NVIDIA doc, but under a Creative Commons or equivalent licence
    • Who might contribute to it / maintain it as a living document?
    • Make an ELISA fork of it and carry it forward?
  • Not guaranteed to be published in a form we can fork / extend

Document review and ‘publication’

  • Some issues cannot necessarily be resolved, because they concern subjective points
    • Reflect this by documenting differences of opinion or record objections
    • Remove need to resolve all differences
    • Record assertion and what would be needed to support it
  • May be some aspects that need further investigation
    • Record as TODOs
  • What are the possible next steps for ‘publishing’?
    • Review at ELISA level?
      • Hosting an opinion or endorsing an opinion?
    • Suggestion: focus on making the content available, with a statement about its level of maturity, rather than ‘endorsement’
  • Next steps: PiU document is a good test case for this

Index of previously create ELISA content

  • Index results without ‘endorsing’ them
  • Publish index with disclaimer
    • Or two indexes - one that is ‘endorsed’ and one that isn’t?
    • Define some criteria for what is ‘endorsed’?
  • Next steps: Pick some examples and try to define some criteria, or decide what is useful / complete enough to bring to a wider audience
  • Index that identifies level of maturity?

Basil requirements tool

  • Technical issues will be discussed in Tools WG
  • Discuss the process aspects of Basil in OSEP?
    • FuSa qualification of Basil?
    • How it might contribute to a FuSa workflow
  • OSEP could host these two discussions and write up the results
  • Define a use case for Basil - e.g. look at a given Linux subsystem
    • Examine both the approach and how the tool supports it
    • Gab: Pick a man page and use Basil to structure requirements around it
      • Identify e.g. POSIX compliance
      • Link to existing tests
    • Igor: Pick a more discrete kernel feature?
      • e.g. kernel after init phase marks certain pages as read only, those that host variables tagged as __ro_after_init
    • Action: Gab to talk to Luigi and come up with an example
      • Consider a different use case after working through this
  • Existing alternatives to Basil
Clone this wiki locally