[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[FuSa SIG] Call for Agenda items for next week's meeting (Nov 19)


  • To: "fusa-sig@xxxxxxxxxxxxxxxxxxxx" <fusa-sig@xxxxxxxxxxxxxxxxxxxx>
  • From: Lars Kurth <lars.kurth@xxxxxxxxxx>
  • Date: Thu, 14 Nov 2019 12:53:33 +0000
  • Accept-language: en-GB, en-US
  • Authentication-results: esa4.hc3370-68.iphmx.com; dkim=none (message not signed) header.i=none; spf=None smtp.pra=lars.kurth@xxxxxxxxxx; spf=Pass smtp.mailfrom=lars.kurth@xxxxxxxxxx; spf=None smtp.helo=postmaster@xxxxxxxxxxxxxxx
  • Delivery-date: Thu, 14 Nov 2019 12:53:41 +0000
  • Ironport-sdr: mey2cmGLRPVsqK9+7Gt0nPlJZD1hlANx9pUD/zzXAzIzOWbWOq3TILCm4+XPpGpu1gLwEUv6Iq CP2Yul/DLE8fwHPoudIZkzlZILT1xfRe4wqmk+NNgKNO3nRV1MpAtVYP5LJIAITOXFxwVMqcGk R9reeyyrGWpdJfQQFj6bBr8heTldg8zUozdF8dW6TBS1hd2L4d2Akmk1BOWE30XRaFCdowKlAK PtQUSGkBAUBDM4o1Dv8RV1xJixU3m9EhFIaYnMzl2FgHEHcYVDTzw597WEKpibBOSuGGv2yj08 4GQ=
  • List-id: This is a discussion list for members of the Xen Project FuSa SIG <fusa-sig.lists.xenproject.org>
  • Thread-index: AQHVmuqFF0iZZsEKaUmxRupAuvYPKQ==
  • Thread-topic: Call for Agenda items for next week's meeting (Nov 19)

Hi all,

it’s been 4 weeks since we met. Please put forward any agenda items

Best Regards

Lars

P.S.: Note that I am on PTO next week. I will chair the call, but I will wing the preparation somewhat

C.1) Actions ongoing or recently closed

High: Lars to kick off a thread on xen-devel@ and come to a conclusion (done, but no conclusion as yet)
See https://markmail.org/message/za465lrrb7waman4
After getting legal advice, the advice is to keep the license of any docs identical to that of the source files
There is NO issue with using a source code license for docs
In practical terms this means we should choose BSD-2-Clause for ABI docs
Personally, I think the best way forward is to maybe do this for ALL safety docs

Medium-High: Antonio to provide a sanitized example of safety docs (including requirements) for system software that we can use as an example
Has been started within Arm
Reviewed some of the example in the last meeting

C.2) Actions not yet resolved

High: Francesco to publish sanitized version of ISO2626 sheets

High: Artem will send part 2 of ISO2626 customization example to the group

High: Artem, Francesco, Lars and Artem to discuss what skills we need in a sub-group to drive progress on ISO2626 customization and see how we can make this happen

My proposal would be:

  • Process stake-holders: Francesco, Antonio, Lars, Artem and maybe Stefano for anything related to process. George is a little overloaded ATM
  • Technical stake-holders: Francesco, Lars, Artem and either Julien (if he has time) & Stefano as technology consultants. If neither can do this, we will have to find someone else, which may be challenging - ACTION: Francesco to check who from Arm could pick this up

High: Francesco’s team to double check MISRA results and later share with group

Low-Medium: Julien to talk to Lava owner on state and usability

Julien: I spoke with one of the Lava owner last Friday. It looks like they have done some works to use QEMU and KVM in Lava 2 a couple of years ago. We could possibly re-use what has been done for Xen. I haven't had yet the chance to speak with Wookey who did the work.
Note: Julien is on PTO and is also now working for AWS, but remains primary Arm maintainer. Need to verify whether he still intends to be part of this group

 

_______________________________________________
Fusa-sig mailing list
Fusa-sig@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/fusa-sig

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.